OPOWER · Authentication Profile

Opower Authentication

Authentication

OPOWER secures its APIs with oauth2 across 1 declared security scheme, as derived from its OpenAPI definitions. OAuth 2.0 is offered via the clientCredentials flow(s).

CompanyEnergyUtilitiesEnergy EfficiencyCustomer EngagementSmart MeterUsage DataOracle

Methods: oauth2 Schemes: 1 OAuth flows: clientCredentials API key in:

Security Schemes

OAuth2ClientCredentials oauth2

· flows: clientCredentials

Source

Authentication Profile

generated: '2026-07-20'
method: searched
source: https://docs.oracle.com/en/industries/energy-water/digital-self-service/restapi/UseOAuth.html
docs: https://docs.oracle.com/en/industries/energy-water/digital-self-service/restapi/UseOAuth.html
summary:
  types: [oauth2]
  oauth2_flows: [clientCredentials]
  model: two-legged (trusted developer / utility) client-credentials
schemes:
- name: OAuth2ClientCredentials
  type: oauth2
  description: >-
    Oracle Utilities Opower REST APIs use the OAuth 2.0 standard with two-legged
    authorization: a trusted developer (the utility) obtains an access token using the
    client_credentials grant and their client_id / client_secret, then passes it as a
    Bearer token on every request. Tokens are short-lived (expires_in ~3599 seconds).
  flows:
  - flow: clientCredentials
    tokenUrl: https://cxapi.opower.com/apis/authorization-v1/oauth2/token
    scopes: {}
  token_request: >-
    POST /apis/authorization-v1/oauth2/token with body grant_type=client_credentials,
    HTTP Basic auth of client_id:client_secret, Content-Type application/x-www-form-urlencoded.
  token_response_fields: [client_id, access_token, token_type, expires_in]
  usage: 'Authorization: Bearer {access_token}'
  guidance: >-
    Oracle documents that keys/tokens must not be used directly in a browser or mobile
    app; utilities must front the Opower APIs with a server-side API gateway that exchanges
    an end-customer session token for a utility OAuth token.
scopes: none-documented
notes: >-
  The GraphQL Integration Hub API is likewise OAuth 2.0 secured. No OAuth scopes are
  documented; access is governed by the utility's provisioned products and roles.

Work with this as data

Every security artifact 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 security posture

4 MCP tools reach this

find_securityBrowse and filter every security artifact 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 security artifact

curl "https://apis.io/api/v1/security/opower-authentication"

All security posture

curl "https://apis.io/api/v1/security?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.