generated: '2026-09-13' method: searched source: https://docs.here.com/policies/docs/limits-and-quotas, https://docs.here.com/geocoding-and-search/docs/limits-and-performance, https://docs.here.com/identity-and-access-management/docs/how-to-find-rate-limit-rules, https://docs.here.com/policies/docs/rps-capacity-planning, and 429 response definitions across the 48 documents in openapi/ supersedes: The 2026-05-04 bulk-sweep scaffold that invented free/professional/enterprise tiers with 10/100/1000 rpm and X-RateLimit-* headers. None of those numbers came from HERE. limit_count: 6 headers: retry_after: Retry-After limit: X-RateLimit-Limit reset: X-RateLimit-Reset usage: RateLimit-Usage remaining: null note: Retry-After is declared on 18 responses across the portfolio. X-RateLimit-Limit and X-RateLimit-Reset are declared on Tour Planning v3 only; most HERE services return a bare 429 with Retry-After. There is no portfolio-wide RateLimit-* header policy. response_codes: throttled: 429 surge_shedding: 503 payload_too_large: 413 runtime_introspection: supported: true api: HERE IAM Rate Limit Rules API v1 spec: openapi/here-rate-limit-rules-v1-openapi.yml docs: https://docs.here.com/identity-and-access-management/docs/how-to-find-rate-limit-rules detail: 'HERE publishes the enforced limits as a callable API rather than only as a documentation table. A caller can read the rules actually in force for its own identity (`me`), for a generic identity in its organization (`default`), or for a named identityHrn, and can look up rules per endpointId, pathPrefix or URL. This is the strongest rate-limit signal in the profile and is unusual: limits are machine-readable at runtime, per caller.' operations: - getRateLimitRulesMe - getRateLimitRulesDefault - getRateLimitRulesIdentity - getRateLimitRuleCaller - getRateLimitRuleDefault - getRateLimitRuleIdentity - getEndpoints - getEndpoint limits: - name: Per-endpoint rate limits scope: per-identity (app, user or organization) per endpoint window: not disclosed limit: null burst: null status_on_exhaustion: 429 detail: All API endpoints are subject to rate limits. HERE states these limits "are subject to adjustments and are not disclosed in detail"; the enforced value is readable per identity through the Rate Limit Rules API. source: https://docs.here.com/geocoding-and-search/docs/limits-and-performance - name: Surge shedding scope: global window: up to ~10 minutes limit: null status_on_exhaustion: 429 detail: On a sudden demand surge (for example a doubling of traffic in a short period) HERE may return 429/503 and throttle callers for up to about 10 minutes even when their quota was not reached, to protect SLA commitments. source: https://docs.here.com/policies/docs/limits-and-quotas - name: RPS capacity planning threshold scope: per contract window: 5-minute average limit: null detail: Maximum RPS is measured as a 5-minute average. Customers must notify HERE 60 days before a >25% increase over the previous 60-day maximum; exceeding by 40% voids availability penalties. source: https://docs.here.com/policies/docs/rps-capacity-planning - name: Batch API v7 — records per job scope: per job limit: 1000000 unit: records status_on_exhaustion: 413 source: https://docs.here.com/geocoding-and-search/docs/limits-and-performance - name: Batch API v7 — input size scope: per job limit: 500 unit: MB uncompressed status_on_exhaustion: 413 source: https://docs.here.com/geocoding-and-search/docs/limits-and-performance - name: Batch API v7 — startable job queue scope: per user limit: 500 unit: jobs in QUEUED/SUBMITTED/FAILURE status_on_exhaustion: 429 source: https://docs.here.com/geocoding-and-search/docs/limits-and-performance other_limits: - name: Batch API v7 — recId length limit: 512 unit: UTF-8 characters effect: entry in the job error log - name: Batch API v7 — record length limit: 4096 unit: UTF-8 characters effect: entry in the job error log - name: Geocoding and Search v7 — results per request limit: 100 unit: items default: 20 source: openapi/here-geocoding-and-search-v7-openapi.json (`limit` parameter maximum) guidance: backoff: Honour Retry-After; exponential backoff with jitter on 429/503. quota_docs: https://docs.here.com/policies/docs/limits-and-quotas