Rate Limits

The FieldEdge Open API limits each partner to 100 requests per minute and 1,000 requests per hour. These limits keep the platform fast and available for every partner and customer.

Limits apply per partner. Every request your integration makes counts toward one shared allowance, no matter which API key, endpoint or FieldEdge customer it is for.

Limits at a glance

Limit	Allowance	Window	When exceeded
Rate limit (bursts)	100 requests	Rolling 60 seconds	429 Too Many Requests
Hourly quota (sustained use)	1,000 requests	Fixed 1-hour window	403 Forbidden

Both limits apply at the same time. The hourly quota is the tighter one for steady traffic: it averages out to about 16 requests per minute. Sending at the full 100-per-minute rate uses up the hourly quota in roughly 10 minutes.

How requests are counted

• Per partner. All requests from your integration count toward your partner allowance, across all endpoints.
• Shared across customers and keys. If you serve several FieldEdge customers or use more than one API key, they all draw from the same allowance. Heavy traffic for one customer reduces what is left for the others.
• Rate limit window rolls. The 100-per-minute limit looks back over the last 60 seconds at any moment, so capacity frees up gradually as older requests age out.
• Hourly quota resets on the hour. The 1,000-per-hour quota resets at a fixed time each hour (on the hour, UTC), not one hour after your first request.
• Counts are approximate. Our gateway runs on multiple servers, so a request or two may occasionally pass or be rejected near the boundary. Build to the published numbers, not to the exact edge.

Responses when a limit is exceeded

A rejected request is not processed. It returns an error, and you can safely retry it later.

429 Too Many Requests — rate limit

Returned when your integration sends more than 100 requests in 60 seconds. The Retry-After header gives the number of seconds to wait.

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

{
  "statusCode": 429,
  "message": "Rate limit is exceeded. Try again in 12 seconds."
}

403 Forbidden — hourly quota

Returned when your integration has used its 1,000 requests for the current hour. The message says how long until the quota resets (hh:mm:ss). This response has no Retry-After header.

HTTP/1.1 403 Forbidden
Content-Type: application/json

{
  "statusCode": 403,
  "message": "Out of call volume quota. Quota will be replenished in 00:21:37."
}

A 403 can also mean an authorization problem. Check the message text: if it mentions the call volume quota, wait for the reset rather than changing credentials.

Handling limits in your integration

1. On 429, wait the number of seconds in Retry-After, then retry. If the header is missing, back off exponentially (1s, 2s, 4s… up to 60s) with random jitter.
2. On 403 with the quota message, pause all API requests until the reset time in the message. Do not retry in a loop: every attempt is rejected until the hour resets.
3. Cap retries (for example, 5 attempts) and surface the failure to your users or logs after that.
4. Route all calls through one shared throttle. Because the allowance covers your whole integration, separate workers or services must coordinate so they don't exceed it together.

Best practices

• Pace requests. Spread work evenly instead of firing large batches at once. A client-side limit of about 15 requests per minute keeps you inside the hourly quota.
• Share the budget fairly across customers. If you serve several FieldEdge customers, schedule their syncs so one large customer can't use up the hour for everyone.
• Cache data that changes rarely. Store reference data (for example, lookup lists and settings) and refresh it on a schedule, not on every request.
• Sync incrementally. Fetch only records changed since your last sync rather than re-reading full datasets.
• Use pagination sensibly. Request the largest page size an endpoint allows to reduce the number of calls.
• Queue background jobs. Run bulk imports and backfills through a throttled queue, ideally outside business hours.
• Log rate-limit responses. Track 429 and 403 counts so you can spot jobs that need tuning.

FAQ

Do rejected requests change any data? No. A 429 or 403 quota response means the request was not processed. Retry it once the limit allows.

Are limits per API key or per customer? Neither. They are per partner: one allowance shared by all your API keys and all the FieldEdge customers you serve.

Do the limits differ between the dev and production environments? The limits in this guide apply to both. Avoid load testing against shared environments; contact us first if you need to.

Can I get a higher limit? Possibly. Email feintegrations@xplortechnologies.com with your integration name, the number of customers you serve, your expected request volume per hour, and the use case. We review requests case by case.