DEVELOPERS · API v1

Idempotency and retries

Public documentation. Partner access through Sales.

Contact Sales

Documentation / Idempotency and retries

Every partner POST requires an Idempotency-Key of 1–120 characters. Keep it stable for retries of the exact same operation.

Required headers

Authorization: Bearer YOUR_ACCESS_TOKEN
Accept: application/json
Content-Type: application/json
Idempotency-Key: your-stable-operation-reference

Request identity

Keys are scoped to your client and bind to the method, path and request body. Changing a request while reusing its key returns 409. JSON object key order does not change identity. Successful retries replay the stored response.

Recovery rules

After a network timeout or server failure, retry the same request with the same key using exponential backoff. On 429, honor Retry-After. On 401, obtain a valid token. Fix validation errors before sending a new operation with a new key. Do not blindly retry 403, 404, 409 or 422.

Upgrade compatibility

Older replay entries without a request fingerprint return 409. Use a new header key while preserving source_ref. Historical ledger source references remain recognized to prevent duplicate stamps or redemptions.

Your privacy

We use necessary storage for sign-in, security and preferences. No analytics or advertising trackers are enabled.

Necessary storage Always active
Keeps your session secure, remembers your language and stores your privacy choice.
Analytics and advertising
Not enabled. We do not use session replay or advertising cookies in this version.

This choice does not accept subscription terms or sign you up for marketing emails.

Legal and privacy centre