Autopass · OAuth Scopes

Autopass OAuth Scopes

OAuth 2.0 searched

Autopass publishes 1 OAuth 2.0 scope via the authorizationCode and clientCredentials flows. Scopes are the fine-grained permissions an application requests at authorization time to act against the Autopass API on a user’s behalf.

Tokens are issued from https://api.autopass.xyz/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.

CompanyMobilityParkingPaymentsAutomotiveFinancial ServicesOAuthTaiwan

Scopes: 1 Flows: authorizationCode, clientCredentials Method: searched

OAuth endpoints

Authorization URL
https://api.autopass.xyz/oauth/authorize

Token URL
https://api.autopass.xyz/oauth/token

Flows
authorizationCodeclientCredentials

Scopes (1)

Scope	Description	Flows
openid	OpenID Connect authentication. Grants identity claims (sub, email, email_verified, phone_number, phone_number_verified) via the userinfo endpoint and ID token.	authorizationCode

📄 Provider scope reference:

Source

OAuth Scopes

generated: '2026-07-18'
method: searched
source: https://api.autopass.xyz/.well-known/openid-configuration
schemes:
  - name: autopassOAuth
    source: https://api.autopass.xyz/.well-known/openid-configuration
    flows:
      - flow: authorizationCode
        authorizationUrl: https://api.autopass.xyz/oauth/authorize
        tokenUrl: https://api.autopass.xyz/oauth/token
      - flow: clientCredentials
        tokenUrl: https://api.autopass.xyz/oauth/token
scopes:
  - scope: openid
    description: >-
      OpenID Connect authentication. Grants identity claims (sub, email, email_verified,
      phone_number, phone_number_verified) via the userinfo endpoint and ID token.
    flows: [authorizationCode]
    sources: [https://api.autopass.xyz/.well-known/openid-configuration]
notes: >-
  scopes_supported in the published OIDC discovery lists only "openid". Autopass does not
  document additional resource scopes; partner authorization to the /pois, /site-sessions
  and /orders resources is governed at the client/partner level rather than by OAuth scopes.