Jawg Maps · Rate Limits

Jawg Maps Rate Limits

Jawg enforces per-account limits along two axes: a monthly included-request quota tied to the subscription plan (shared across tiles, Places, routing, matrix, isochrone, and static maps), and a short-window requests-per-second throttle that scales up with the plan tier. Exceeding the RPS throttle returns HTTP 429; exhausting the monthly quota blocks further requests until the quota resets or an overage / upgrade is in place. Access tokens can be domain-restricted to control where they may be used.

Jawg Maps Rate Limits is the machine-readable rate-limit profile for Jawg Maps on the APIs.io network, conforming to the API Commons Rate Limits specification.

It captures 4 rate-limit definitions, measuring requests.

The profile also includes 3 backoff/retry policies defined and response codes documented for throttled.

Tagged areas include Maps, Geospatial, Tiles, Geocoding, and Routing.

4 Limits Throttle: 429
MapsGeospatialTilesGeocodingRoutingLocationRate LimitingQuotasThrottling

Limits

Requests Per Second (RPS) account
requests
see provider documentation
Short-window throttle that scales with the subscription plan; bursts above it return 429.
Monthly Request Quota account
requests
see provider documentation
Included monthly request allowance shared across all Jawg APIs; varies by plan.
Tile Requests account
requests
counted against the monthly quota
Each raster/vector tile fetch counts as a request against the shared quota.
Places / Routing / Matrix / Isochrone Requests account
requests
counted against the monthly quota
API calls to Places, routing, matrix, and isochrone count against the same shared quota.

Policies

Tiered Limits
RPS throttle and monthly request quota rise as accounts move from Free to Starter, Business, and Enterprise.
Token Domain Restriction
Access tokens can be restricted to allowed domains/referrers to prevent unauthorized use.
Backoff Strategy
Clients should implement exponential backoff with jitter on HTTP 429 responses.

Sources