This article explains the API Daily Rate Allowance, the configurable Overage Buffer (ceiling), regional reset times, how usage is measured, enforcement mechanism (including 429 responses), and notifications.
The API Daily Rate Allowance is only applicable to customers on the Location Intelligence subscription.
The API Daily Rate Allowance is applicable to all APIs except the Coverage API.
Before you proceed, it's recommended that you review the following glossary.
Glossary
Term | Definition |
|---|
API Overage | When you exceed your API Daily Rate Allowance in a 24-hour period. |
API Daily Rate Allowance | The number of Tile requests or Effective Tile requests (AI areas) permitted in a 24-hour period. |
Overage Buffer | A percentage-based threshold of the total daily allowance which can be used before cutoff. |
Daily Rate Reset Time | North America accounts reset at 00:00 CST
ANZ accounts reset at 00:00 AEST |
Effective Tile Request | AI area polygons counted as the number of tiles underneath the AI area request, measured in tiles at zoom level 21. |
Overage Days Remaining | The number of days you can exceed the daily allowance. |
Rate Limit Cutoff | The point at which API access is revoked and a 429 HTTP response code is returned for requests. |
What’s included in your subscription
- Today's Usage - Usage on a particular day expressed as a percentage of your allowance.
- Overage Buffer (not visible in MyAccount) - The threshold of the total daily allowance, in relation to your API Daily Rate Allowance. For more information, read the sections below.
- Overage days remaining
To view this data, select Account, Usage tab and then click API Daily Rate.
How usage is measured
Usage is measured by the number of Tile or Effective Tile requests, with the following tile counting rules applied:
- For Vertical, panorama, and WMS imagery, usage is measured for requests with zoom level >= 14.
- Daily usage is calculated over your regional 24‑hour window.
Regional reset times
Usage counters reset precisely at the configured regional reset time.
- North America (NA/US) accounts reset at 00:00 CST.
- ANZ accounts reset at 00:00 AEST.
Overage Buffer
The Overage Buffer provides a buffer over and above your contracted daily allowance. It is expressed as a percentage of your contracted daily allowance. If your daily usage stays below the defined buffer, requests continue to succeed until that buffer is exceeded.
If you exceed your Overage Buffer, API access is removed for the remainder of the day. Cutoff remains until the regional daily reset time, or until the Overage Buffer is increased by authorized staff.
When access is removed, API calls receive an HTTP 429 Too Many Requests response with Retry-After header indicating reset time. Given below is an example:
You have exceeded your daily rate limit, and you will not be able to access additional tiles today. See your contract administrator to increase daily allowance
You’ll receive an HTTP 429 Too Many Requests response when you exceed the API’s per-second rate limit, that is, the number of requests you can make against an endpoint/second. For example, if you send more than 1,000 requests per second to the Tile API, the request will be rejected with HTTP 429.
Notifications and visibility
The following notifications are sent as specific thresholds are reached.
Threshold | Notifications |
|---|
80% of daily allowance | Account admins notified; includes time remaining until reset. |
Exceeds daily allowance | Notification; indicates whether strict enforcement is in effect. |
80% of daily Overage Buffer | Warning about approaching cutoff. |
Exceeds daily Overage Buffer | A notification is sent to your CSM for further action. |
Reaching Overage Days Permitted in the month | Notification that Strict Enforcement has been enabled |
Shown below is an example of a notification.
Guidance and recommended actions
- Monitor MyAccount daily usage and ensure account admin contact information is accurate in case you need to contact them.
- Subscribe to notifications.
- Other measures:
- Cache tiles and avoid redundant requests.
- Batch or simplify AI-area polygons to reduce Effective Tile consumption (counted at zoom level 21).
- Handle 429 responses gracefully, read the Retry-After header and wait until reset.
- If you need more capacity, contact your contract administrator or CSM to increase the API Daily Rate Allowance or the Overage Buffer. Authorized staff can make changes, which take effect within 60 minutes.