Idempotency
Money-moving endpoints take an idempotency key. Send the same key again and you get the original result back, never a second movement.
Money-moving endpoints accept an idempotency key. Send the same key with the same request and you get the original result back, rather than a second movement.
Idempotency-Key: payroll-march-emeka-001
- Generate the key on your side, before you first try, and reuse it for every retry of that same intent.
- A new intent gets a new key. Reusing a key for a different body is an error.
- Keys are scoped to your tenant, so two businesses can use the same string safely.
Header names by module
The header name is not the same in every module. This table is generated from the API reference, and each endpoint in the reference lists the header it takes.
| Header | Modules |
|---|---|
Idempotency-Key | bills, budget, collections, disbursements, events, gift-cards, rentals, savings, transactions |
X-Idempotency-Key | offline-payments, openbanking |