Versapay · OAuth Scopes

Versapay OAuth Scopes

OAuth 2.0 searched

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

Tokens are issued from https://secure.versapay.com/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.

PaymentsCanadaAccounts ReceivableAR AutomationOrder-to-CashPayment AcceptancePayment ProcessingB2B PaymentsInvoicingE-CommerceCard PresentWebhook

Scopes: 5 Flows: authorizationCode, clientCredentials, password Method: searched

OAuth endpoints

Authorization URL
https://secure.versapay.com/oauth/authorize

Token URL
https://secure.versapay.com/oauth/token

Flows
authorizationCodeclientCredentialspassword

Scopes (5)

Scope	Description	Flows
receivables	Access to the accounts-receivable / Collaborative AR surface (customers, invoices, payments, collaboration, notifications).	authorizationCode, clientCredentials, password
payables	Access to the payables / money-movement surface (funds, transactions, debit agreements, autopay).	authorizationCode, clientCredentials, password
read	Read access to permitted resources.	authorizationCode, clientCredentials, password
write	Create access to permitted resources.	authorizationCode, clientCredentials, password
update	Update access to permitted resources.	authorizationCode, clientCredentials, password

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

Source

OAuth Scopes

generated: '2026-07-24'
method: searched
source: https://secure.versapay.com/.well-known/openid-configuration
docs: https://developers.versapay.com/
notes: >-
  Versapay's primary API auth is HTTPS Basic (API Token & Key) or JWT bearer, but
  secure.versapay.com additionally exposes a Doorkeeper OIDC/OAuth2 authorization
  server (discovery at /.well-known/openid-configuration). The scopes below are
  taken verbatim from scopes_supported in that discovery document. Scope-to-
  operation mapping is not published per-endpoint; descriptions are inferred from
  the platform surface (receivables/payables product lines + CRUD verbs) and
  should be confirmed against an issued client's grant.
schemes:
  - name: OAuth2
    source: https://secure.versapay.com/.well-known/openid-configuration
    flows:
      - flow: authorizationCode
        authorizationUrl: https://secure.versapay.com/oauth/authorize
        tokenUrl: https://secure.versapay.com/oauth/token
        pkce: [plain, S256]
      - flow: clientCredentials
        tokenUrl: https://secure.versapay.com/oauth/token
      - flow: password
        tokenUrl: https://secure.versapay.com/oauth/token
    token_endpoint_auth: [client_secret_basic, client_secret_post]
    revocation_endpoint: https://secure.versapay.com/oauth/revoke
    introspection_endpoint: https://secure.versapay.com/oauth/introspect
    userinfo_endpoint: https://secure.versapay.com/oauth/userinfo
    jwks_uri: https://secure.versapay.com/oauth/discovery/keys
scopes:
  - scope: receivables
    description: Access to the accounts-receivable / Collaborative AR surface (customers, invoices, payments, collaboration, notifications).
    flows: [authorizationCode, clientCredentials, password]
    sources: [https://secure.versapay.com/.well-known/openid-configuration]
  - scope: payables
    description: Access to the payables / money-movement surface (funds, transactions, debit agreements, autopay).
    flows: [authorizationCode, clientCredentials, password]
    sources: [https://secure.versapay.com/.well-known/openid-configuration]
  - scope: read
    description: Read access to permitted resources.
    flows: [authorizationCode, clientCredentials, password]
    sources: [https://secure.versapay.com/.well-known/openid-configuration]
  - scope: write
    description: Create access to permitted resources.
    flows: [authorizationCode, clientCredentials, password]
    sources: [https://secure.versapay.com/.well-known/openid-configuration]
  - scope: update
    description: Update access to permitted resources.
    flows: [authorizationCode, clientCredentials, password]
    sources: [https://secure.versapay.com/.well-known/openid-configuration]

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/versapay-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 form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

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