Skip to main content
The Glider Platform API uses two rate-limit layers. These limits protect service availability.

Rate-limit layers

Layer 1: Global limit for each IP address

Each request from an IP address counts toward one global limit. The route does not change this count. This limit prevents one client from overloading the service.

Layer 2: Tier limit for each IP address

Each route belongs to a tier based on cost and sensitivity. All routes in one tier share a counter for each IP address. A request must pass both layers. If it exceeds one limit, the API returns 429.

Response headers

Each rate-limited route returns these standard headers: When both layers apply, the headers show the limit with fewer remaining requests. Use these values to control the request rate.

429 response format

When a request exceeds a limit, the API returns:
Include correlationId and requestId when you contact Glider support.

Retry a request

  1. Read the Retry-After header (or retryAfter field) from the 429 response.
  2. Wait at least that many seconds before retrying.
  3. For repeated 429 responses, use exponential backoff with jitter.
  4. Use different retry times for different clients.