Enode · Rate Limits

Enode Rate Limits

The Enode API enforces per-client rate limits to protect both the platform and upstream device-vendor integrations. Limits are applied per OAuth client and vary by endpoint class, with control actions and refresh-hints subject to tighter limits than reads because they reach through to vendor cloud APIs. Enode recommends webhooks over polling and respects per-vendor refresh intervals. Specific numeric limits are not published and are not reconciled in this artifact.

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

It captures 3 rate-limit definitions, measuring requests and actions.

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

Tagged areas include Energy, Electric Vehicles, EV Charging, Smart Charging, and Energy Transition.

3 Limits Throttle: 429
EnergyElectric VehiclesEV ChargingSmart ChargingEnergy TransitionRate LimitingQuotasThrottling

Limits

Requests Per Client client
requests
see provider documentation
Per OAuth client request rate; varies by endpoint class.
Control Actions client
actions
see provider documentation
Charge/control actions reach through to vendor clouds and are limited more tightly than reads.
Refresh Hints device
requests
see provider documentation
refresh-hint calls are bounded by per-vendor refresh intervals.

Policies

Prefer Webhooks
Subscribe to webhooks for device and user updates instead of polling read endpoints.
Backoff Strategy
Clients should implement exponential backoff with jitter and honor Retry-After on 429 responses.
Respect Vendor Intervals
Telemetry freshness and refresh frequency are constrained by each upstream device vendor.

Sources