specification: API Commons Rate Limits
specificationVersion: '0.1'
schema: https://raw.githubusercontent.com/api-evangelist/interface-research/main/schema/api-commons.yml#/$defs/RateLimits
provider: Xcel Energy
providerId: xcel-energy
created: '2026-05-04'
# Provenance stamped 2026-08-11: this artifact was written by the API Evangelist
# bulk sweep dated 2026-05-04, not harvested from the provider. See roadmap#35.
method: generated
modified: '2026-05-05'
reconciled: false
tags:
  - Rate Limiting
  - Energy Data
  - Green Button
  - Utility
description: Xcel Energy does not publish numeric rate limits for its Green Button Connect My
  Data (ESPI) or IEEE 2030.5 endpoints on the public-facing developer portal. The portal at
  developer-apim.aws.xcelenergy.com requires registration; rate-limit policy is gated behind that
  onboarding. ESPI is designed for batched daily data pulls rather than high-frequency reads.
sources:
  - https://developer-apim.aws.xcelenergy.com/
limits:
  - name: ESPI / Green Button Connect data feed (numbers not publicly documented)
    scope: third-party-provider
    metric: varies
    limit: see Xcel Energy developer portal after onboarding
    notes: Green Button Connect data is published as periodic ESPI-formatted feeds rather than
      per-call resource fetches; throughput is governed by the customer-authorized data window
      and Xcel's batch-publishing schedule.
  - name: IEEE 2030.5 local smart-meter endpoint
    scope: meter
    metric: requests_per_second
    limit: 'see IEEE 2030.5 specification and Itron Gen 5 Riva meter limits'
    notes: IEEE 2030.5 is a local, customer-network protocol; per-meter request rates are bound
      by the meter hardware (Itron Gen 5 Riva) rather than a centralized Xcel quota.
policies:
  - name: Onboarding required
    description: Public rate-limit numbers are not published; third parties must complete Xcel's
      data-recipient onboarding to receive the limits document.
  - name: ESPI batch model
    description: Green Button Connect uses a publish-and-fetch model rather than transactional
      reads; clients should follow ESPI's NotificationLink / SubscriptionLink polling pattern.
  - name: Backoff
    description: Standard guidance is exponential backoff with jitter on HTTP 429 / 503 responses.
maintainers:
  - FN: Kin Lane
    email: kin@apievangelist.com
    url: https://apievangelist.com