Monta · Rate Limits

Monta Rate Limits

The Monta Public API is secured with OAuth2 client-credentials bearer tokens (access tokens valid roughly one hour, refresh tokens roughly 24 hours) and uses page / perPage pagination on list endpoints, with perPage capped at 100 items. Monta does not publish specific request-rate limit numbers (RPM/RPS) for the Public or Partner API; applications are expected to behave well and rely on webhooks rather than aggressive polling. Specific per-endpoint or per-application rate-limit values are not reconciled in this artifact.

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

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

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

Tagged areas include EV Charging, Electric Vehicles, Charge Points, Energy, and Mobility.

4 Limits Throttle: 429
EV ChargingElectric VehiclesCharge PointsEnergyMobilityRate LimitingQuotasThrottling

Limits

Access Token Lifetime application
seconds
~3600
Bearer access tokens issued by POST /auth/token are short-lived (about one hour).
Refresh Token Lifetime application
seconds
~86400
Refresh tokens are valid for about 24 hours and are exchanged via POST /auth/refresh.
Pagination Page Size request
items
100
perPage query parameter accepts 1-100 items, default 10; page starts at 0.
Request Rate application
requests
see provider documentation
No public RPM/RPS limit is published; use webhooks instead of frequent polling.

Policies

OAuth2 Client Credentials
Exchange clientId and clientSecret for a short-lived bearer token; refresh before expiry.
Prefer Webhooks Over Polling
Subscribe to signed webhook events for real-time updates rather than polling list endpoints.
Backoff Strategy
Clients should implement exponential backoff with jitter and honor 429 responses and any Retry-After header.

Sources