Autopay · OAuth Scopes

Autopay OAuth Scopes

OAuth 2.0 derived

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

Tokens are issued from https://api-auth.autopay.io/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.

ParkingParking PaymentsFleet ManagementPermitsParking OperatorsNorway

Scopes: 3 Flows: clientCredentials Method: derived

OAuth endpoints

Token URL
https://api-auth.autopay.io/oauth/token

Flows
clientCredentials

Scopes (3)

Scope	Description	Flows
customer_club	Required for Customer Club API operations	clientCredentials
permit_booking	Required for Booking API operations	clientCredentials
zone_status	Required for Status API operations	clientCredentials

📄 Provider scope reference:

Source

OAuth Scopes

generated: '2026-07-11'
method: derived
source: openapi/autopay-openapi.yml
schemes:
- name: OAuth2
  source: openapi/autopay-openapi.yml
  flows:
  - flow: clientCredentials
    tokenUrl: https://api-auth.autopay.io/oauth/token
  description: OAuth 2.0 Client Credentials flow. Tokens are minted from the Auth0 token endpoint
    and used as Bearer tokens with `audience` set to `https://api.autopay.io`. Some endpoints
    require specific scopes such as `permit_booking`, `customer_club`, or `zone_status`.
scopes:
- scope: customer_club
  description: Required for Customer Club API operations
  flows:
  - clientCredentials
  sources:
  - openapi/autopay-openapi.yml
- scope: permit_booking
  description: Required for Booking API operations
  flows:
  - clientCredentials
  sources:
  - openapi/autopay-openapi.yml
- scope: zone_status
  description: Required for Status API operations
  flows:
  - clientCredentials
  sources:
  - openapi/autopay-openapi.yml