Eliq · OAuth Scopes
Eliq OAuth Scopes
OAuth 2.0
searched
Eliq 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.
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.
EnergyUtilitiesAnalyticsSustainabilityEnergy DataSmart MeterDisaggregationForecastingSegmentationConsumptionTariffsInsights
Scopes: 0
Flows:
Method: searched
Scopes (0)
Eliq 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.
Eliq does NOT publish a scope reference page. The scopes below are the ones the provider's own documentation and Auth API contract show by name in request examples and token-claim examples — they are transcribed, not enumerated from a catalogue, and the real per-client scope set is only visible inside the Client Admin Portal. `scopes_supported` is absent from the OIDC discovery document too. NO SCOPE HERE WAS INVENTED and this list is not claimed to be complete.
Eliq does NOT publish a scope reference page. The scopes below are the ones the provider's own documentation and Auth API contract show by name in request examples and token-claim examples — they are transcribed, not enumerated from a catalogue, and the real per-client scope set is only visible inside the Client Admin Portal. `scopes_supported` is absent from the OIDC discovery document too. NO SCOPE HERE WAS INVENTED and this list is not claimed to be complete.
📄 Provider scope reference: https://developer.eliq.com/doc/authentication
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.