Scheduled removals and deprecated fields.
Every breaking change is announced here before it takes effect. A deprecated field keeps working until its removal date. Additive changes — new endpoints, new optional fields, new enum values — are not breaking and are not listed, so write clients that ignore fields they do not know.
| Date | Endpoint | Change |
|---|---|---|
| 2026-09-23 | GET /team | balances[].depositInfo is removed. Use the top-level deposits array. |
| Deprecated since | Endpoint | Field | Use instead |
|---|---|---|---|
| 2025-10-27 | GET /payout/{id}, GET /payouts | uuid | id |
| 2025-12-04 | GET /team | teamUuid | id |
| 2026-02-11 | POST /payout, GET /payout/{id}, GET /payouts | handleType | verificationMethod |
| 2026-06-21 | GET /payout/{id}, GET /payouts | url | A fresh claim URL from POST /session/payout |
| 2026-07-28 | POST /session/payout | whitelabel (accepted but ignored) | branding: "team" |
| 2026-07-28 | OAuth | Dynamic client registration (RFC 7591) for platform integrations | An OAuth client created in Settings → OAuth Clients |
Errors and retries
The error format, common error codes, and how to retry safely.
Create POST
Create or update a new payout for team members. For teams with balance enforcement enabled (the default), pre-approved payouts (`preApproved: true`) are rejected with HTTP 422 and error code `INSUFFICIENT_BALANCE` when the total of all open (approved but not yet paid out) payouts would exceed the team wallet balance. The error `data` contains `walletBalance`, `totalOpenAmount`, and `currency`.