Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.getarca.app/llms.txt

Use this file to discover all available pages before exploring further.

The Arca API enforces rate limits to protect the service from abuse and ensure reliable performance for all integrations.

​
Limits

All endpoints share a single limit of 600 requests per minute, tracked per API key. Each integration has its own independent quota.

​
When a limit is exceeded

When a rate limit is exceeded, the API returns 429 Too Many Requests with a JSON body: 
{
  "statusCode": 429,
  "error": "Too Many Requests",
  "retryAfter": 47
}
retryAfter is the number of seconds to wait before retrying. The following headers are included on 429 responses:
HeaderDescription
x-ratelimit-limitMaximum requests allowed in the window
x-ratelimit-remainingRequests remaining before the limit resets
x-ratelimit-resetSeconds until the window resets
retry-afterSame as retryAfter in the response body

​
Best practices

  • Respect retry-after. When you receive a 429, wait the indicated number of seconds before retrying.
  • Avoid polling loops. If you need near-real-time updates, prefer event-driven patterns over polling every few seconds.
  • Use pagination. The task list endpoint returns a maximum of 100 tasks per page. Fetch only the pages you need.
  • Batch writes sequentially. If importing data, send requests sequentially rather than in parallel bursts.