Rate Limits

Our APIs implement rate limiting, which defines the maximum number of calls allowed within a specified time interval. Rate limiting helps ensure optimal performance for the integration between your software and Telgorithm by preventing other clients from negatively affecting your service.

Although no universally accepted standard exists for HTTP rate-limiting headers, we were guided by the IETF draft: RateLimit Fields for HTTP.

We use the following HTTP headers for our API endpoints:

RateLimit-Limit: The total number of requests allowed in the current time window.
RateLimit-Remaining: A non-negative integer representing the number of remaining requests allowed in the current time window.
RateLimit-Reset: The number of seconds until the quota resets and the full quota becomes available.

Default quotas:

When the quota is exceeded, the server does not process the request and instead responds with a 429 HTTP status code.

If you need a higher quota, please contact us.

Authentication Failure Protection

To protect API availability, Telgorithm may temporarily reject requests after repeated authentication failures.

If requests from the same network source repeatedly return 401 Unauthorized, subsequent eligible API requests may be rejected with 429 Too Many Requests for a short period. This can also affect multiple clients that share the same NAT, proxy, or gateway.

When this protection returns 429, the response includes the RateLimit-* headers:

• RateLimit-Limit: the applicable authentication-failure limit.
• RateLimit-Remaining: 0 while requests are temporarily throttled.
• RateLimit-Reset: the number of seconds until the client should retry.

To avoid triggering this protection, do not continuously retry requests that return 401 Unauthorized. Verify the API credentials before sending additional requests.