API rate limits
Understand how rate limiting works and how to handle 429s.
Last updated April 27, 2026
The Maptera API enforces rate limits per API key. Limits are generous for typical use but designed to prevent abuse and runaway scripts.
Default limits
- 100 requests per minute per API key (read endpoints)
- 30 requests per minute per API key (write endpoints — POST/PATCH/DELETE)
- Geocoding endpoints: 60 per minute
Response headers
Every response includes headers showing your current usage:
X-RateLimit-Limit: 100
X-RateLimit-Remaining: 87
X-RateLimit-Reset: 1735689600Handling 429 errors
When you exceed a limit you get a 429 Too Many Requests response. The Retry-After header tells you how many seconds to wait before retrying. A simple exponential backoff handles this gracefully.
If you have a legitimate use case that needs higher limits, contact us — we can raise limits per-account.
Was this article helpful?
Related articles
Did this article miss your question?
Email our team and we will help directly.