Volteras · OAuth Scopes

Volteras OAuth Scopes

OAuth 2.0 searched

Volteras publishes 12 OAuth 2.0 scopes via the clientCredentials flow. Scopes are the fine-grained permissions an application requests at authorization time to act against the Volteras API on a user’s behalf.

Tokens are issued from /v1/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.

CompanyElectric VehiclesConnected VehiclesAutomotiveVehicle TelemetryEV ChargingEnergyMobilityFleet Management

Scopes: 12 Flows: clientCredentials Method: searched

OAuth endpoints

Token URL
/v1/oauth2/token

Flows
clientCredentials

Scopes (12)

Scope	Description	Flows
vehicle:all	Access to everything (all vehicle scopes).
vehicle:information	Access to vehicle specifications, options, vin and registration plate.
vehicle:charging_history	Access to vehicle charging history.
vehicle:telemetry	Access to location and odometer.
vehicle:commands	Access to remote commands.
vehicle:driving_behavior
vehicle:location_history
battery:all
battery:telemetry
geofences:all
geofences:read
geofences:write

📄 Provider scope reference: https://docs.volteras.com/overview/scopes

Source

OAuth Scopes

generated: '2026-07-21'
method: searched
source: openapi/volteras-connect-openapi-original.json
docs: https://docs.volteras.com/overview/scopes
description: >-
  Volteras consent scopes control what data/capabilities an integration gets
  from a connected end-user account; they are passed via the scopes parameter
  when constructing the account connect URL (POST /v1/accounts:connect). The
  API-client credential itself uses OAuth 2.0 client-credentials with no
  client-level scopes. The docs scopes page documents the five vehicle scopes;
  the OpenAPI ScopeEnum additionally declares battery and geofence scopes.
schemes:
  - name: OAuth2ClientCredentialsBearer
    source: openapi/volteras-connect-openapi-original.json
    flows:
      - flow: clientCredentials
        tokenUrl: /v1/oauth2/token
scopes:
  - scope: vehicle:all
    description: Access to everything (all vehicle scopes).
    sources: [openapi/volteras-connect-openapi-original.json#ScopeEnum, docs]
  - scope: vehicle:information
    description: Access to vehicle specifications, options, vin and registration plate.
    sources: [openapi/volteras-connect-openapi-original.json#ScopeEnum, docs]
  - scope: vehicle:charging_history
    description: Access to vehicle charging history.
    sources: [openapi/volteras-connect-openapi-original.json#ScopeEnum, docs]
  - scope: vehicle:telemetry
    description: Access to location and odometer.
    sources: [openapi/volteras-connect-openapi-original.json#ScopeEnum, docs]
  - scope: vehicle:commands
    description: Access to remote commands.
    sources: [openapi/volteras-connect-openapi-original.json#ScopeEnum, docs]
  - scope: vehicle:driving_behavior
    description: null
    sources: [openapi/volteras-connect-openapi-original.json#ScopeEnum]
  - scope: vehicle:location_history
    description: null
    sources: [openapi/volteras-connect-openapi-original.json#ScopeEnum]
  - scope: battery:all
    description: null
    sources: [openapi/volteras-connect-openapi-original.json#ScopeEnum]
  - scope: battery:telemetry
    description: null
    sources: [openapi/volteras-connect-openapi-original.json#ScopeEnum]
  - scope: geofences:all
    description: null
    sources: [openapi/volteras-connect-openapi-original.json#ScopeEnum]
  - scope: geofences:read
    description: null
    sources: [openapi/volteras-connect-openapi-original.json#ScopeEnum]
  - scope: geofences:write
    description: null
    sources: [openapi/volteras-connect-openapi-original.json#ScopeEnum]
scoped_endpoints:
  - {endpoint: '/vehicles/[id]', scopes: [vehicle:information], required: false, effect_without_scope: 'Fields excluded: vin, registrationPlate'}
  - {endpoint: '/vehicles/', scopes: [vehicle:information], required: false, effect_without_scope: 'Fields excluded: vin, registrationPlate'}
  - {endpoint: '/vehicles/[id]/options', scopes: [vehicle:information], required: true, effect_without_scope: 401 Response}
  - {endpoint: '/vehicles/[id]/specifications', scopes: [vehicle:information], required: true, effect_without_scope: 401 Response}
  - {endpoint: '/vehicles/[id]/telemetry', scopes: [vehicle:telemetry], required: true, effect_without_scope: 401 Response}
  - {endpoint: '/vehicles/[id]/charging-history', scopes: [vehicle:charging_history], required: true, effect_without_scope: 401 Response}
  - {endpoint: '/vehicles/[id]/charging-history/[id]', scopes: [vehicle:charging_history], required: true, effect_without_scope: 401 Response}
  - {endpoint: '/vehicles/[id]/command-executions/', scopes: [vehicle:commands], required: true, effect_without_scope: 401 Response}

Work with this as data

Every scope set 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 oauth scopes

4 MCP tools reach this

find_scopesBrowse and filter every scope set 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 scope set

curl "https://apis.io/api/v1/scopes/volteras-scopes"

All oauth scopes

curl "https://apis.io/api/v1/scopes?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no email required.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.