Referral Partners

Embed debt collection into your SaaS platform with the Referral Partner API.

Overview

The Referral Partner API enables platforms to offer debt collection as a native feature. Onboard your clients as Debitura creditors, submit cases on their behalf, and earn revenue on successful collections — all through a white-labeled experience.

Use this track if you are: A SaaS platform (accounting software, invoicing tool, ERP) looking to add debt collection capabilities for your users.

What You Can Build

• Seamless client onboarding — Create Debitura accounts for your users programmatically
• In-app case submission — Let users send invoices to collection without leaving your platform
• White-label experience — Custom branding on all user-facing flows
• Revenue tracking — Monitor earnings and attribution via reporting endpoints
• Real-time events — Webhooks for onboarding completion, case updates, and payments

Your Reading Path

Start here

1. How It Works — The two-API architecture and how the pieces fit together
2. Authentication — API key and bearer token model
3. Environments — Test vs production URLs
4. Quickstart — Onboard a client and submit a case end-to-end

Build the core integration

5. Client Onboarding — Full POST /clients workflow with all response scenarios
6. Case Submission — Mint bearer tokens and submit cases via the Customer API
7. Webhooks — Event subscriptions for onboarding and case events
8. Preview Pricing — Show your users the success fee before they commit

Handle edge cases

9. KYC Verification — Director identity verification for some jurisdictions
10. Revenue Tracking — Build revenue dashboards, understand the fee pipeline
11. Webhook Best Practices — Production-grade event handling

Understand the boundaries

12. Responsibility Matrix — Who does what: Debitura vs your platform

Prepare for production

13. Webhook Testing — Verify your handler with test events
14. Going Live — Step-by-step migration to production and pre-flight checklist
15. Error Reference — Every error across both APIs in one place
16. Troubleshooting — Common issues and how to debug them

Case Management

After onboarding a client, you use the Customer API (with a bearer token) to submit and manage cases. See How It Works for how the two APIs connect.

• Create a Case — Submit cases for collection
• Track Case Status — Monitor progress
• Webhooks (Customer API) — Case-level event notifications

API Reference

• Referral Partner API — Client onboarding, token generation, revenue reporting
• Customer API — Case submission and management (used with bearer tokens)

Business context: See How Referral Partners Work on the support site for the business model, commercial terms, and operational guidance.