REST API errors and rate limits - SaucerSwap

The REST API uses standard HTTP status codes. This page covers the statuses you should handle, the quota headers to monitor, and how to retry safely.

Status codes

Status	Meaning	What to do
`200`	Success	Parse the JSON body.
`400`	Invalid request — a malformed or missing parameter, such as an out-of-range `from`/`to` or an unsupported `interval`	Fix the request; do not retry unchanged.
`401`	Missing or invalid `x-api-key` header	Check that the key is present, unexpired, and sent on every request.
`403`	The key is not authorized for the request	Contact [email protected] about your key’s access.
`404`	Unknown resource, such as a token or pool id that does not exist	Verify the id against the corresponding list endpoint.
`429`	Rate limited — the monthly quota is exhausted or requests are arriving too fast	Back off and retry later; see below.
`5xx`	Server error	Retry with exponential backoff.

The V3 Orderbook API has its own error format — a JSON body of { "error": "message string" } — and its own rate and policy limits. See Orderbook limits and errors.

Rate Limits

100 requests per 10 seconds per IP
590 requests per minute per IP

Next steps

REST API authentication

Request an API key and understand how quotas are provisioned.

REST API conventions

Parse amounts, prices, and timestamps correctly before debugging errors.

Orderbook limits and errors

Policy limits and error handling for the V3 Orderbook API.