Effective: May 5, 2026
Applies to:
- MileMaker 2.0 REST API (Guide20)
Overview
To ensure consistent performance and fair access for all customers, MileMaker now enforces per-customer rate limits on API requests. This update introduces request limits along with response headers that let your application track its current usage in real time.
No action is required for most integrations. Applications that operate well within normal usage levels are unaffected.
Rate Limits
Each customer account has a default limit of 10,000 requests per minute. Requests are measured over a rolling one-minute window across both Guide19 and Guide20, separately for search and routing endpoints.
If your integration requires a higher limit, the limit can be adjusted for your account on request — please contact MileMaker support at support@milemaker.com
Tracking Your Usage
Every API response includes the following headers, reflecting your account's current rate-limit status:
| Header | Description |
|---|---|
X-RateLimit-Minute-Limit |
The maximum number of requests allowed in the current one-minute window. |
X-RateLimit-Minute-Remaining |
The number of requests remaining in the current window. |
X-RateLimit-Minute-Reset |
The time at which the current window resets, as a Unix timestamp (seconds since epoch, UTC). |
We recommend monitoring these headers so your application can pace its requests and avoid interruptions.
When a Limit Is Exceeded
If you exceed your rate limit, the API responds with HTTP status 429 Too Many Requests. The rate-limit headers above are included on this response as well, so your application can use X-RateLimit-Minute-Reset to determine when to resume sending requests.
We recommend implementing a retry strategy (for example, exponential backoff) so that occasional limit responses are handled gracefully.
Comments
0 comments
Please sign in to leave a comment.