Eaton · OAuth Scopes

Eaton OAuth Scopes

OAuth 2.0 derived

Eaton uses OAuth 2.0 but publishes no discrete scopes — access is governed by the grant itself (e.g. client-credentials or role-based authorization) rather than per-scope consent.

Tokens are issued from https://api.em.eaton.com/oauth2/token.

This index is generated from the provider’s OpenAPI security definitions (and, where available, its documented scope reference) and refreshes on every APIs.io network build. Browse every provider’s scopes at scopes.apis.io.

Power ManagementElectricalSmart BreakerEV ChargingDemand ResponseData CenterDCIMPDUUPSUtilityIndustrialBuildingMobilityAI FactoryEnergyIoTSustainability

Scopes: 0 Flows: clientCredentials Method: derived

OAuth endpoints

Token URL
https://api.em.eaton.com/oauth2/token

Flows
clientCredentials

Scopes (0)

Eaton implements OAuth 2.0 but publishes no discrete scopes — access is governed by the grant itself (client-credentials or role-based authorization) rather than per-scope consent.

Eaton's Smart Breaker API OAuth2 uses a scope-less client-credentials flow — tokens are issued from client ID + secret alongside an Em-Api-Subscription-Key header, with authorization governed by application/organization service accounts and user roles rather than documented OAuth scopes (https://api.em.eaton.com/docs).

📄 Provider scope reference: https://api.em.eaton.com/docs

Source

OAuth Scopes

generated: '2026-07-11'
method: derived
source: openapi/smart-breaker-openapi.yml
docs: https://api.em.eaton.com/docs
note: Eaton's Smart Breaker API OAuth2 uses a scope-less client-credentials flow — tokens are issued from client ID + secret alongside an Em-Api-Subscription-Key header, with authorization governed by application/organization service accounts and user roles rather than documented OAuth scopes (https://api.em.eaton.com/docs).
schemes:
- name: OAuth2
  source: openapi/smart-breaker-openapi.yml
  flows:
  - flow: clientCredentials
    tokenUrl: https://api.em.eaton.com/oauth2/token
scopes: []