Skip to content
English - United Kingdom
  • There are no suggestions because the search field is empty.

What does Error Code 429 mean and how do I resolve it?

Error 429 means you have exceeded your API key's request allowance of 50 requests per minute. The limit operates on a rolling window, and the correct fix is to restructure your integration to use a storage layer rather than querying the API directly in real time.

How the throttle limit works

Error 429 occurs when the number of requests made with your API key exceeds the permitted allowance. By default, each API key is limited to 50 requests per minute.

The limit operates on a rolling minute rather than a fixed clock interval. This means that when a request is made, it is removed from your remaining allowance and returns to it exactly 60 seconds later. For example:

  • 0 seconds — a request is submitted — 49 requests remaining
  • 30 seconds — a request is submitted — 48 requests remaining
  • 60 seconds — the first request returns to the allowance — 49 requests remaining
  • 90 seconds — the second request returns to the allowance — 50 requests remaining

How to resolve the issue

1. Use a storage layer (recommended approach)

The API is not designed for live, real-time querying from your integration or website. The correct architectural pattern is:

  • Run a scheduled job (e.g. once per hour or once per day) that fetches data from the API and stores it in your own database or storage layer
  • Your website or application then reads from your storage layer, not from the API directly
  • This approach drastically reduces API calls and eliminates throttling under normal conditions

The only exception to this pattern is when the API is being used to submit data into agentOS — for example, posting a tenancy application from an application form or creating a diary appointment. In these cases, it is acceptable for the API call to be triggered directly by a user action.

2. Review your request frequency

If you are already using a storage layer, review how frequently your scheduled jobs run and whether any processes are making redundant or duplicate requests. Reducing unnecessary calls will help keep you within the limit.

3. Request an increased limit

If your integration has a legitimate requirement for more than 50 requests per minute and restructuring is not feasible, contact api@agentos.com to discuss whether an increased limit can be applied to your key.

Getting help

If you are unable to resolve the issue after reviewing your integration architecture, contact support@agentos.com for assistance.