Mesh Payments · OAuth Scopes

Mesh Payments OAuth Scopes

OAuth 2.0 searched

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

Tokens are issued from https://api.meshpayments.com/as/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.

CompanyPaymentsSpend ManagementExpense ManagementCorporate CardsTravelAccounts PayableFintechCard IssuingAccounting Automation

Scopes: 1 Flows: authorizationCode, clientCredentials, deviceCode Method: searched

OAuth endpoints

Authorization URL
https://api.meshpayments.com/as/authorize

Token URL
https://api.meshpayments.com/as/token

Flows
authorizationCodeclientCredentialsdeviceCode

Scopes (1)

Scope	Description	Flows
openid	OpenID Connect authentication scope; requests an ID token from the Mesh authorization server.	authorizationCode

📄 Provider scope reference: https://developers.meshpayments.com

Source

OAuth Scopes

generated: '2026-08-04'
method: searched
source: https://api.meshpayments.com/.well-known/openid-configuration
docs: https://developers.meshpayments.com
docs_note: the developers portal that would carry the scope/permission reference returns
  401 (HTTP Basic) to the public, so only the scopes the authorization server advertises
  anonymously are recorded.
schemes:
- name: Mesh Payments authorization server
  issuer: https://api.meshpayments.com
  source: https://api.meshpayments.com/.well-known/openid-configuration
  flows:
  - flow: authorizationCode
    authorizationUrl: https://api.meshpayments.com/as/authorize
    tokenUrl: https://api.meshpayments.com/as/token
  - flow: clientCredentials
    tokenUrl: https://api.meshpayments.com/as/token
  - flow: deviceCode
    deviceAuthorizationUrl: https://api.meshpayments.com/oauth2/device_authorization
    tokenUrl: https://api.meshpayments.com/as/token
scopes:
- scope: openid
  description: OpenID Connect authentication scope; requests an ID token from the Mesh
    authorization server.
  flows:
  - authorizationCode
  sources:
  - https://api.meshpayments.com/.well-known/openid-configuration
gaps:
- scopes_supported on the discovery document lists only "openid". Any API or MCP resource
  scopes Mesh issues are not advertised anonymously, and the RFC 9728 protected-resource
  metadata for https://api.meshpayments.com/mcp omits the optional scopes_supported
  member. Publishing scopes_supported on the protected-resource metadata would let an
  agent discover the permission surface without credentials.
x-evidence:
- fetched: '2026-08-04'
  url: https://api.meshpayments.com/.well-known/openid-configuration
  http_status: 200
- fetched: '2026-08-04'
  url: https://api.meshpayments.com/.well-known/oauth-protected-resource/mcp
  http_status: 200