Skip to main content
Rate limiting is used to control the volume of requests processed by the Erysta API. This ensures a stable and reliable environment for all users.

​
Limits per time period

Rate limits are applied globally to all incoming requests. Our system evaluates limits based on the unique origin of the request to prevent abuse.
Time periodMaximum number of API calls allowed
1 minute100 calls

​
Response header information

Each API response includes standard headers to help you monitor your current usage and prevent interruptions: X-RateLimit The maximum capacity for the current window. X-RateLimit-Remaining Remaining requests available until the next reset. X-RateLimit-Reset Unix timestamp indicating when your quota will be fully restored.

​
Handling Limit Exceptions (429)

When a limit is reached, the API will return a 429 Too Many Requests error. To ensure continuous service, your integration must monitor the Retry-After header, which indicates the exact number of seconds to wait before your next successful request.
Rate limit reached – Response example
{
  "status": 429,
  "success": false,
  "error": {
    "message": "Too Many Requests",
    "timestamp": "2026-03-09T15:30:00.000Z"
  }
}

​
Best Practices

  1. Optimize Batching: Avoid high-frequency polling.
  2. Respect Retry-After: Always implement a delay logic based on the Retry-After header.