To ensure fair usage and platform stability, the FieldInsight Public API enforces rate limits on all applications.Understanding how these limits work and how to handle them correctly is essential for building reliable integrations.Overview#
Your application is limited to:60 API requests per minute per business
This limit applies independently to each business your application interacts with.How Rate Limiting Works#
Requests are counted within a fixed one-minute window.Each business has its own window timing, and windows reset at different times.You may make up to 60 requests.
Once the limit is reached, further requests will be rejected until the window resets.
| Header | Description |
|---|
| X-RateLimit-Limit | Maximum number of requests allowed in the current window |
| X-RateLimit-Remaining | Number of requests remaining in the current window |
| X-RateLimit-Reset | Time when the current window resets (UTC epoch seconds) |
These headers allow your application to dynamically adjust its request
behavior.What Happens When You Exceed the Limit#
If you exceed the rate limit, the API will return:HTTP 429 Too Many RequestsNo further requests should be made for that business
You must wait until the time specified in X-RateLimit-Reset before retrying
Client-Side Handling Recommendations#
To build a robust integration, we strongly recommend implementing proper rate limit handling.Every response includes rate limit information. Use it to:Prevent hitting the limit
Determine when it is safe to retry
x-ratelimit-remaining is low, proactively slow down requests rather than waiting for a 429 response.Handle HTTP 429 Correctly#
When a 429 Too Many Requests response is received:1.
Read the X-RateLimit-Reset header
2.
Calculate how long to wait
3.
Pause requests until after the reset time
Modified at 2026-02-18 02:21:38
