Update Claim Amount
Adjust the principal and fees on an active case to reflect the current state of the debt.
When to Use This
The claim amount changes when:
- Additional evidence reveals the debt is higher or lower than originally stated
- Partial payments have already been made and the creditor wants to reflect the reduced principal
- Legal costs or enforcement fees need to be added to the fees
- Errors in the original claim amount need to be corrected
Use PUT /cases/{id}/fees with a grossAmount field to update the principal, fees, or both in a single call.
What Changes
When you update the claim amount:
- Principal and fees are updated — all values you supply replace the current values
- Success fee is re-evaluated — if you changed the principal and a collection partner is assigned, the pre-legal success fee (your commission percentage applied to the new amount) is re-evaluated. If the new principal crosses a fee bracket, the endpoint does not apply the change silently — it returns
409asking you to confirm (see Price-Change Confirmation below). When the fee does not move (or moves by ≤0.1 percentage points) the new value is applied directly and returned asrecalculatedSuccessFee - Remainder is recalculated — the outstanding balance (
grossAmount + interestFees + collectionFees + reminderFees − payments) is updated automatically - Audit event is written — a timeline entry recording the old and new values is created and is visible to the creditor
Price-Change Confirmation
When a principal edit would move the success-fee percentage by more than 0.1 percentage points, the edit is not applied. The endpoint returns 409 Conflict with a confirmation body so you can review the change before committing to it:
{
"caseId": "a1b2c3d4-...",
"confirmationRequired": true,
"currentSuccessFee": 8.00,
"proposedSuccessFee": 9.50,
"isIntentionalRate": false,
"message": "...",
"warning": null
}
Resubmit the same request with one resolution flag to apply it:
| Flag | Effect | When allowed |
|---|---|---|
confirmPriceChange: true | Re-prices to the new standard (bracket) rate and applies the edit | Only on a standard, tier-based rate (isIntentionalRate: false) |
keepIntentionalRate: true | Applies the amount edit but keeps the existing rate | Only on a special agreement (isIntentionalRate: true) |
Special Agreements Are Preserve-Only
If the case carries a deliberately-set rate — an accepted quote or a manual override (isIntentionalRate: true) — the rate is preserve-only on this API. You can apply the amount edit and keep the rate with keepIntentionalRate: true, but you can never re-price it. Sending confirmPriceChange: true on such a case is rejected with 400 directing you to keepIntentionalRate: true — nothing is applied.
:::note Business context The special rate was negotiated for this case and cannot be overridden from a partner integration — only a Debitura administrator can change it to the standard rate. See Success Fees for how pricing is determined. :::
Status Gate
| Case Status | Principal (grossAmount) | Fees only |
|---|---|---|
| Active | Allowed | Allowed |
| PendingVerification | Allowed | Allowed |
| Paused | Allowed | Allowed |
| NeedsAdditionalDetails | Allowed | Allowed |
| Closed | Rejected (400) | Rejected (400) |
| Merged | Rejected (400) | Rejected (400) |
:::note Asymmetry with file upload File uploads are allowed on Closed cases. Principal and fee edits are not — they are rejected on both Closed and Merged cases. This matches the partner portal behavior. :::
Backward Compatibility
The grossAmount field is optional. Omitting it leaves the principal unchanged — the endpoint behaves exactly as before (fees-only update). Existing integrations that call PUT /cases/{id}/fees without grossAmount are unaffected.
Decrease Is Allowed
Both increases and decreases to the principal are accepted. There is no minimum. The UI shows an informational warning when payments exist — the API does not enforce this either.
Zero (0.00) is accepted as a valid principal.
Request Example
PUT /cases/{id}/fees
Content-Type: application/json
{
"grossAmount": 850.00,
"interestFees": 35.00,
"reminderFees": 0.00,
"collectionFees": 120.00
}
Response Example
{
"caseId": "a1b2c3d4-...",
"grossAmount": 850.00,
"interestFees": 35.00,
"reminderFees": 0.00,
"collectionFees": 120.00,
"totalAddedFees": 155.00,
"recalculatedSuccessFee": 170.00,
"remainder": 1005.00
}
recalculatedSuccessFee is null when the principal was not changed, or when no collection partner is assigned.
Fees-Only Update (Backward-Compatible)
To update fees without touching the principal, omit grossAmount:
PUT /cases/{id}/fees
Content-Type: application/json
{
"interestFees": 35.00,
"reminderFees": 0.00,
"collectionFees": 120.00
}
For full endpoint details, see Update Case Fees.