Skip to main content

Rate limits

To protect platform stability, the Merchant API may rate-limit requests. When you exceed a limit, expect an HTTP 429 Too Many Requests response; back off and retry after a short delay.

Specific limits to be confirmed

Concrete per-endpoint rate limits and any Retry-After / rate-limit response headers for this platform are not yet finalised in this documentation. Build defensively using the guidance below; this page will be updated with exact figures.

Building for rate limits​

  • Retry 429 and 5xx with exponential backoff and jitter. Do not retry tight loops.
  • Honour Retry-After if present on a 429 response.
  • Keep retries idempotent. Reuse the same merchant_reference so a retried creation does not create a duplicate (see Conventions).
  • Prefer webhooks over polling. Use webhooks to learn about outcomes instead of polling search endpoints in a loop.
  • Batch with search. Use the …/search endpoints with pagination rather than many single-record lookups.