Otonomo · OAuth Scopes

Otonomo OAuth Scopes

OAuth 2.0 derived

Otonomo 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.otonomo.io/v1/oauth/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.

CompanyConnected VehiclesAutomotiveFleet ManagementTelematicsVehicle DataMobilityIoTLocationConnected Car
Scopes: 0 Flows: clientCredentials Method: derived

OAuth endpoints

Token URL
https://api.otonomo.io/v1/oauth/token/
Flows
clientCredentials

Scopes (0)

Otonomo 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.

📄 Provider scope reference:

Source

OAuth Scopes

Raw ↑ 
generated: '2026-07-20'
method: derived
source: openapi/otonomo-fleet-openapi.yml
schemes:
- name: oauth2
  source: openapi/otonomo-fleet-openapi.yml
  flows:
  - flow: clientCredentials
    tokenUrl: https://api.otonomo.io/v1/oauth/token/
  description: 'OAuth2 client-credentials. Obtain a Bearer token from POST /v1/oauth/token/
    then send it as Authorization: Bearer <token>.'
scopes: []