Managed Cases

Submit and monitor cases on behalf of your own clients.

When to Use Managed Cases

Some collection partners have their own client relationships—businesses that come to you directly rather than through Debitura. With managed cases, you can submit these cases to Debitura's network while maintaining your client relationship.

Use managed cases when:

• Your client doesn't have a Debitura account
• You want to leverage Debitura's partner network for jurisdictions you don't cover
• You need to track cases you've referred out

How It Works

Your Client → You (Managing Partner) → Debitura → Collection Partner
                                                        ↓
                                               Works the case
                                                        ↓
You monitor progress ←──────────────────────── Updates & payments

1. You create a managed case via POST /managed-cases with your client's details
2. Debitura assigns the case to an appropriate collection partner
3. The assigned partner works the collection
4. You monitor progress via GET /managed-cases endpoints
5. When payment is collected, you're notified

Managing Partner vs Collection Partner

Role	What You Do	Endpoints
Collection Partner	Work cases assigned to you	GET /cases, POST /cases/{id}/payments
Managing Partner	Submit cases, monitor progress	GET /managed-cases, POST /managed-cases

You can be both simultaneously—working some cases directly while referring others out.

Limitations

As a managing partner, you cannot:

• Close cases
• Edit case details
• Record payments on production cases (only the assigned collection partner can)

You can:

• View case details and timeline
• Read chat communications
• Monitor payment status
• Access case files
• Upload files using POST /managed-cases/{id}/files
• Record payments on test cases (see below)

Use the managed-cases endpoint when you submitted the case on behalf of your client. If you are also the assigned collection partner on a different case, use POST /cases/{id}/files for that case instead. See Upload Files for file requirements and examples.

Recording Payments on Test Cases

You can record payments on test cases (created with isTest: true in the POST /managed-cases request body) via POST /managed-cases/{id}/payments. This enables full end-to-end integration testing — verifying webhook delivery, lifecycle transitions, and remainder updates — without involving the assigned collection partner.

This endpoint is not available for production cases. On production cases, only the assigned collection partner can record payments via POST /cases/{id}/payments.

POST /managed-cases/{id}/payments
Content-Type: application/json

{
  "date": "2025-11-19",
  "paymentAmount": 5000.00,
  "closeCase": false
}

A payout record is created automatically with the full amount allocated to the creditor. Webhooks fire normally, making this useful for verifying your webhook handling end-to-end.

Testing your integration

Set isTest: true in the request body when creating cases during development. Cases marked as test data return with isTestCase: true on the response DTO, are excluded from production metrics, and let you freely record payments to verify your webhook handling and reconciliation logic.

API Endpoints

Endpoint	Purpose
POST /managed-cases	Create a case for your client
GET /managed-cases	List cases you've submitted
GET /managed-cases/{id}	View case details
GET /managed-cases/{id}/timeline	View case history
GET /managed-cases/{id}/payments	View payments collected
POST /managed-cases/{id}/payments	Record a payment (test cases only)
GET /managed-cases/{id}/files	View files attached to the case
POST /managed-cases/{id}/files	Upload a file to the case

Choose between a total amount, age buckets, and invoice lines in Claim Amount and Age, then follow Create a Managed Case for request examples. For the complete schema, see the API Reference.