Equinor · OAuth Scopes
Equinor OAuth Scopes
OAuth 2.0
searched
Equinor publishes 3 OAuth 2.0 scopes. Scopes are the fine-grained permissions an application requests at authorization time to act against the Equinor API on a user’s behalf.
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.
CompanyEnergyOil and GasRenewablesNorwayOpen DataOpen Source
Scopes: 3
Flows:
Method: searched
Scopes (3)
| Scope | Description | Flows |
|---|---|---|
| Timeseries.Read | API permission required to read timeseries; also needed to create streaming subscriptions. | |
| AE.Read | API permission needed to access the Alarm & Events API. | |
| user_impersonation | Delegated permission a client needs to call the Timeseries API on behalf of a signed-in user (public clients plant-timeseries-api-public-plant-production / -non-production are provided). |
📄 Provider scope reference: https://github.com/equinor/OmniaPlant/wiki/Authentication-&-Authorization
Source
OAuth Scopes
Work with this as data
Every scope set here is available over the APIs.io API and to AI agents over MCP.