Radar · Rate Limits

Radar Io Rate Limits

Radar enforces per-organization rate limits on the api.radar.io/v1 REST API, expressed primarily as requests per second, and separately meters monthly API-call and tracked-user quotas by plan. Server (secret key) endpoints such as track, geofence management, and users have their own limits distinct from client (publishable key) endpoints such as geocoding, search, and routing. Specific per-endpoint values are set per organization and plan and are not reconciled in this artifact.

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

It captures 4 rate-limit definitions, measuring requests and users.

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

Tagged areas include Location, Geocoding, Geofencing, Maps, and Routing.

4 Limits Throttle: 429
LocationGeocodingGeofencingMapsRoutingRate LimitingQuotasThrottling

Limits

Requests Per Second (Client Key) organization
requests
see provider documentation
Applies to publishable-key surfaces (geocoding, search, routing, tiles); varies by plan.
Requests Per Second (Server Key) organization
requests
see provider documentation
Applies to secret-key surfaces (track, geofence CRUD, users, trips); varies by plan.
Monthly API Calls organization
requests
see plan allotment
Free tier includes a monthly call allotment; overages are pay-as-you-go.
Monthly Tracked Users organization
users
see plan allotment
Applies to Track / SDK usage; varies by plan.

Policies

Tiered Limits
Limits and quotas raise as organizations move from Free to Enterprise plans.
Backoff Strategy
Clients should implement exponential backoff with jitter and honor 429 responses.

Sources