⚠️Errors, retries, and rate limits

Validation errors

Invalid request data normally returns 400 with field-specific details. Treat IDs as environment-specific and refresh discovery data when a combination becomes unavailable.

{
  "network": [
    "network not available for selected cryptocurrency"
  ]
}

Authentication errors

An invalid or missing Partner-Api-Key is rejected. Verify the key prefix, environment, and widget status before retrying.

Quote search errors

• A missing or expired search_id can return 404.

• A specified provider can return 400 with Quote not found.

• No result for one provider does not imply that all providers are unavailable.

Create a new search rather than polling an invalid search ID indefinitely.

Retry guidance

Retry only transient failures such as network timeouts and 5xx responses. Use exponential backoff with jitter and a bounded attempt count. Do not automatically retry transaction creation unless the application can determine whether a transaction_id was already created.

Rate limits

The current API does not publish a fixed partner request quota. Clients must nevertheless:

• avoid tight quote-polling loops;

• cache relatively stable discovery data;

• stop polling on completed or terminal failure;

• handle 429 Too Many Requests and Retry-After defensively if throttling is introduced;

• coordinate expected high-volume traffic with partner support.

Start quote polling after a short delay and increase the interval instead of polling continuously.