Skip to main content
Network failures can leave you unsure whether a request succeeded. ProxyJam supports idempotency on create operations so you can retry safely.

​
How it works

Include a unique idempotency_key (UUID) in your request body. If you send the same key again, the API returns the original response instead of creating a new resource.

​
Endpoints that support idempotency keys

​
Header-based idempotency

Some endpoints take the idempotency key as the HTTP Idempotency-Key header rather than a body field:
The Idempotency-Key header is required for POST /payments/payment-intents and for mobile-rotating calls to POST /orders/{order_id}/extend. Requests will be rejected without it.
A replay with the same key returns the cached response. A different request body sent with the same key returns 409 ConflictError.

​
Best practices

  • Generate a new UUID for each unique operation. Never reuse a key for a different operation.
  • Store the key before making the request so you can resend it on retry.
  • Keys are scoped per user — the same key used by two different users creates two separate resources.