Reditus API
The Reditus API lets you send data to Reditus and pull your data out of it. API and webhook access is included on every plan, and your API key is already available during the 14-day free trial.
What customers use the API for
- Payments from any processor except Stripe (most common). If you bill with Paddle, Chargebee, Lemon Squeezy, PayPal or any other processor, you send your payments through the Payments API and Reditus matches them to referrals. On Stripe, connect Stripe natively instead; you don't need the Payments API. Full guide: run your affiliate program with any payment processor.
- All of your tracking. You can track server-side through the API instead of through the tracking script's cookie. Some larger enterprise customers run all of their tracking through the API; it is a more custom setup and takes more work.
- Your data in your own tools or an LLM. Pull your affiliate data into your own systems, or connect the API to an AI assistant such as Claude through MCP, retrieve all your Reditus data and run your own analysis, without the Reditus interface.
How the Payments API works
- Referrals come first. Your referrals reach Reditus through the tracking script and the signup snippet, or through the API. A payment only creates a commission for a referral that exists in Reditus.
- Pick a mode. Forward all payments with the customer's email or a unique ID, and Reditus ignores the payments that don't belong to a referral. Or use minimal-data mode: first ask the API which referrals exist, then send payment data for those customers only.
- Send amounts in cents. The Payments API takes amounts in cents: a payment of €99.00 is sent as 9900.
- Send an idempotency key with every payment. It is required and tied to one transaction, so a commission is never calculated twice.
- Send refunds to the refund endpoint. Any refund rejects the full commission automatically. Partial refunds are not possible.
Coupon-code tracking isn't available on the API path: affiliates promote with their tracked links. Forwarding all payments takes about four hours of developer time, depending on your processor. The endpoints and fields are in the developer documentation.
Unique IDs instead of emails
Working purely with unique IDs is fully supported. UID tracking (no emails needed): send your own account or organization IDs instead of email addresses. Combined with server-side tracking, no customer emails or visitor profiles reach Reditus. That holds when payment data goes through the Payments API and the Stripe, HubSpot and Calendly integrations are not connected, because each of them brings the email address to Reditus on its own. UID tracking is opt-in: without it, the referred person's email is sent.
Test on staging first
Staging is a separate, self-serve environment at app.getreditus.net.
- Sign up on app.getreditus.net, even if you already have a Reditus account: staging is fully separate from production.
- Get your API key there, and keep all your endpoints on .net while you test.
- Test the full flow, from signup to payment, before you go to production.
- When everything works, switch the endpoints, the API key and the tracking script to .com for production.
Webhooks
Want Reditus to tell your systems when something happens, such as a new partnership or a new lead? Use the webhooks.
FAQ
Where is the API documentation?
Do I need the API if I use Stripe?
Not for your payments: connect Stripe natively. Some Stripe customers still choose the Payments API, so they don't have to give Reditus read-only access to their whole Stripe account.
How do I test the API?
Sign up on the staging environment at app.getreditus.net, get your API key there, point your API calls to the .net endpoints and test the full flow. When it works, switch the endpoints, the API key and the tracking script to .com.
Can I use the API during the free trial?
Yes. Your API key is already available during the 14-day free trial.
Does the Payments API take amounts in cents?
Yes. Send every amount in cents: a payment of €99.00 is sent as 9900, and $1,250.00 as 125000.