Upcoming System Update: Enrol and RPL

On Thursday. 12th March 2026, we’ll be rolling out a series of improvements to Enrol and RPL.

Full details of the changes can be found in the release notes below:

Downtime: There will be no product downtime.

Submit a ticket Log in

API Rate Limit

Overview

The Onefile API enforces a rate limit to ensure stable and reliable performance for all customers. If your integration exceeds this limit, requests will temporarily be blocked.

API Rate Limit

  • Maximum: 300 API calls per minute
  • If this limit is reached, the API will return a 429 – Too Many Requests error.

How to Avoid Hitting the Limit

If your system is regularly reaching the rate limit, consider the following:

  • Use paged searches to retrieve larger batches of data in a single request.
    This is more efficient than making multiple small calls.
  • Cache data when appropriate instead of re‑requesting unchanged values.
  • Stagger bulk processing jobs to avoid rapid bursts of requests.

Tips & Notes

  • A 429 error indicates you must wait before retrying your request.
  • If you frequently reach the limit, review your API logic to reduce unnecessary calls.

Terminology

Terminology used in this article may differ depending on your Centre.

Related Articles

Need Help?

If you need assistance or have questions about API usage, please contact Onefile Support or your internal technical team.

Did you find it helpful? Yes No

Send feedback
Sorry we couldn't be helpful. Help us improve this article with your feedback.