REST API access - SaucerSwap

The REST API needs no API key. Send a plain HTTPS request; there is no signup, header, or token to add.

This page covers the REST data API only. The V3 Orderbook API uses wallet challenge authentication and short-lived JWTs for account endpoints. See Orderbook authentication.

Make a request

curl -i https://api.saucerswap.finance/tokens

A successful response returns 200 with rate-limit state in the response headers (values as of November 7, 2026):

HTTP/2 200
content-type: application/json; charset=utf-8
x-ratelimit-limit: 10000000
x-ratelimit-remaining: 10000000
x-ratelimit-additional-total: 0
x-ratelimit-reset: 1796083199999

Use https://test-api.saucerswap.finance for testnet. An x-api-key header from an older integration is ignored, so existing code keeps working.

Rate-limit headers

Header	Meaning
`x-ratelimit-limit`	Requests allowed in the current period.
`x-ratelimit-remaining`	Requests left in the current period. Use it to alert or self-throttle.
`x-ratelimit-additional-total`	Requests counted over the limit in the current period.
`x-ratelimit-reset`	Time when the counters reset, as a unix timestamp in milliseconds.

Per-IP limits also apply. See REST API errors and rate limits.

Next steps

REST API conventions

Understand tinybar, smallest-unit amounts, timestamps, and interval endpoints.

Errors and rate limits

Handle 400, 404, and 429 responses and build retry logic that respects the limits.

Browse the endpoints

Start with the token list, then explore pools, farms, and stats.

Developer quickstart

Make your first REST call in under five minutes.

​Make a request

​Rate-limit headers

​Next steps

REST API conventions

Errors and rate limits

Browse the endpoints

Developer quickstart

Make a request

Rate-limit headers

Next steps