Rate Limits

Rate limits protect the API from excessive load and ensure fair usage across all users. Limits are applied per API key.

Default Limits

Category	Endpoints	Limit
Trading	buy, sell (instant and delayed)	No limit
Token Creation	create-token	No limit
Token Management	claim-creator-fees, claim-cashback, update-fee-shares, transfer, revoke	60 requests / minute
All other endpoints	wallets, funding, utilities, health	60 requests / minute

Trading and token creation endpoints are not rate limited — you can execute as many transactions as needed.

When you exceed the limit, the API returns a 429 status code:

{
  "success": false,
  "error": {
    "code": "RATE_LIMIT",
    "message": "Rate limit exceeded"
  }
}

Practice	Why
Batch requests	Use arrays (e.g., 100 wallets in one balance call) instead of individual calls
Cache read responses	Avoid polling the same data more than needed
Back off on 429	Wait before retrying — exponential backoff works well
Monitor your usage	Track your request count to stay within limits

A single balance request can query up to 100 wallets at once. Batching is the most effective way to stay within limits.

If the default limits do not fit your use case, reach out to the team. Custom limits are available on a case-by-case basis.

Request custom rate limits or discuss your specific requirements

Full reference of all API error codes

Tips for reliable API integration