Rate Limiting

6 min

The EquiDeFi API enforces

To protect system stability and assure fair usage, the API enforces rate limits from one scope.

Requests that exceed limits receive a 429 Too Many Requests response, and clients are given guidance on when to retry.

All requests to the API are limited to 120 req/min (per API key).

Note: We currently do not allow for custom rate limiting configuration.

Clients are informed about usage status via response headers. Two header styles are supported:

Preferred (IETF-style)

These follow guidelines from the draft standard for rate limiting headers.

When a request is throttled (429), a Retry-After: <seconds> header is included to instruct how long the client should wait before trying again.

When a request is blocked by rate limiting, the response looks as follows:

HTTP/1.1 429 Too Many Requests Retry-After: 12 Content-Type: application/json

{ "error": "Too many requests, please try again later." }

Clients must obey the Retry-After header before retrying.

Successful Read (IETF-style headers)

Request

GET /api/v1/investment/9b32de17-****-****-****-************ HTTP/1.1 Authorization: Bearer sk_live_0c7c195*******************

Response Headers

HTTP/1.1 200 OK RateLimit-Policy: 120;w=60 RateLimit-Limit: 120 RateLimit-Remaining: 119 RateLimit-Reset: 56 Content-Type: application/json

Respect the Retry-After header if present in the response headers. Do not retry if the the RateLimit-Remaining is 0

Use larger page sizes or caching techniques (ETags, conditional GETs) to reduce the total number of API calls.

Segment workloads via separate API keys when possible to prevent one key’s usage from interfering with another.

If your service sits behind proxies or load balancers, the rate limiting will still be limited by the API key, not the IP address requesting the endpoint