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, in the API Commons Rate Limits shape.

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

An exhausted limit returns HTTP 429.

This profile was written by API Evangelist and has not been verified against a page the provider published; treat every limit as unconfirmed until a dated transcription replaces it.

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 Exhausted: HTTP 429
Method: generated, dated 2026-06-21.
Written by API Evangelist on 2026-06-21 and not verified against a page the provider published. Treat every limit as unconfirmed until a dated transcription replaces it.
View Source
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

Work with this as data

Every rate limit here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for rate limits

4 MCP tools reach this
  • find_rate_limitsBrowse and filter every rate limit in the catalog.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This rate limit 
curl "https://apis.io/api/v1/rate-limits/enode-rate-limits"
All rate limits 
curl "https://apis.io/api/v1/rate-limits?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.