Per-entity rate limits and throttling behavior for all StableFX API endpoints.
Rate limits control how many requests you can make per second to each StableFX
endpoint. Limits apply per entity. Your entity ID is the unique identifier
assigned to your organization when you register with Circle.StableFX counts requests with a sliding window algorithm. The window is one
second long. If you send more requests than the limit allows in any rolling
one-second span, the API returns an HTTP 429 Too Many Requests response until
your rate drops below the limit.
If you receive a 429 response, wait briefly and retry. Use exponential delay
between retries. Sending requests at the same rate extends the throttle.
The following table lists the per-entity rate limits for all StableFX API
endpoints. For examples of calling these endpoints, see the
taker quickstart and
maker quickstart. To set up the
notifications endpoint, see
Set up a webhook endpoint.
Method
Endpoint
Maximum requests per second
POST
/v1/exchange/stablefx/quotes
20
POST
/v1/exchange/stablefx/trades
20
GET
/v1/exchange/stablefx/trades
30
GET
/v1/exchange/stablefx/trades/{tradeId}
30
GET
/v1/exchange/stablefx/signatures/*
20
POST
/v1/exchange/stablefx/signatures/*
20
POST
/v1/exchange/stablefx/fund
20
GET
/v1/exchange/stablefx/fees/{tradeId}
30
POST
/v1/exchange/stablefx/notifications
50
Was this page helpful?
Assistant
Responses are generated using AI and may contain mistakes.