GridX · Rate Limits

Gridx Rate Limits

GridX's Calculate and Empower APIs are partner/enterprise APIs provisioned per utility deployment. Authentication uses short-lived JWT bearer tokens (roughly one-hour expiry) for the Customer Information and Usage endpoints, with a separate token flow for OpenADR. GridX does not publish specific request-per- minute, request-per-day, or quota values; any rate limiting, concurrency caps, and batch-processing constraints are governed by the deployment contract and are not reconciled in this artifact.

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

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

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

Tagged areas include Energy, Utilities, Rate Engine, Billing, and Rate Analytics.

3 Limits Throttle: 429
EnergyUtilitiesRate EngineBillingRate AnalyticsRate LimitingQuotasThrottling

Limits

API Request Limits deployment
requests
see provider / contract documentation
Not publicly published; governed by the utility deployment agreement.
Token Expiry account
seconds
~3600
JWT bearer tokens from the /token endpoint expire after approximately one hour and must be refreshed.
Batch Rate Analysis deployment
jobs
see provider / contract documentation
Empower batch rate-analysis throughput is contract-governed; not publicly documented.

Policies

Token-Based Authentication
Customer Information/Usage endpoints require a JWT bearer token; OpenADR uses a separate token flow.
Backoff Strategy
Clients should implement exponential backoff with jitter and honor Retry-After on 429 responses.

Sources