Idempotency & retries

Idempotency is keyed on (partnerId, orderId). Use it to make retries safe.

Same orderId + same body

You get the original result back as 200 DUPLICATE. Network timeout? Just resend the identical request.

Same orderId + different body

409 IDEMPOTENCY_CONFLICT. An orderId is bound to its first payload; use a new orderId for a different award.

503 TX_CONFLICT

Transient contention. Retry the same request with backoff; it’s idempotent, so you’ll get the original award or a fresh one.

Retry policy

Recommended for 502 / 503 / 504 and network errors: exponential backoff (e.g. 1s, 2s, 4s, 8s) with jitter, capped at ~5 attempts, always reusing the same orderId.

Caution

Do not retry 4xx responses (except after fixing the cause). They are deterministic — the same request will fail the same way. Fix the payload, signature, or cap first.