Skip to main content
Every REST API endpoint requires an API key. Keys are provisioned by the SaucerSwap team and carry a monthly request quota.
This page covers the REST data API only. The V3 Orderbook API uses wallet challenge authentication and short-lived JWTs instead — see Orderbook authentication.

Get an API key

Email [email protected] to request a key. The team provisions keys manually — there is no self-serve signup — and your monthly request quota is agreed during that conversation. Provisioned keys are UUID strings. Store your key in server-side secret storage. Do not embed it in frontend code or commit it to a repository: anyone holding the key consumes your quota.

Authenticate requests

Pass your key in the x-api-key header with every request over HTTPS:
A successful response returns 200 with your current quota state in the response headers:

Quota headers

If you expect to occasionally need more requests than your quota, raise it with the team in advance — overage requests are then counted in x-ratelimit-additional-total instead of being rejected.

Next steps

REST API conventions

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

Errors and rate limits

Handle 401, 403, and 429 responses and build quota-aware retry logic.

Browse the endpoints

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

Developer quickstart

Make your first authenticated call in under five minutes.