Rate limits

Each API key can make 600 requests per minute.

How the limit worksCopy Anchor Link

• The limit is counted per key. Two keys have two separate limits.
• The minute is a fixed window: it starts with the key's first request and resets 60 seconds later. Within one window, the 601st request and every request after it are refused.
• Every request made with a valid key counts, whatever the endpoint and whatever its outcome, including requests that the MCP server makes with your key.
• The API does not send the remaining budget in response headers. If you run close to the limit, count your own requests.

When you go overCopy Anchor Link

The API answers 429 Too Many Requests with a Retry-After header: the number of seconds until the window resets.

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

{ "error": "API key rate limit exceeded", "code": "RATE_LIMITED" }

Wait that many seconds, then send the request again. Nothing was done for a refused request, so retrying it is safe.

# -i prints the response headers, including Retry-After
curl -i "https://<your-workspace>.apros.app/api/leads" \
  -H "Authorization: Bearer $APROS_API_KEY"

Stay under the limitCopy Anchor Link

• Read lists with the largest page size the endpoint allows (usually 100) instead of fetching records one by one. See Pagination.
• Spread bulk jobs over time rather than sending everything at once.
• Cache data that changes rarely, such as stages, units or currencies.
• When you retry a create after a timeout, send an Idempotency-Key so the retry cannot create a duplicate. See Retrying safely.

Other limitsCopy Anchor Link

Endpoints that are called without an API key have their own limits: