Veem · OAuth Scopes

Veem OAuth Scopes

OAuth 2.0 searched

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

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

PaymentsB2B PaymentsCross-Border PaymentsInvoicingWalletsFintechGlobal Payments
Scopes: 1 Flows: clientCredentials, authorizationCode Method: searched

OAuth endpoints

Authorization URL
https://api.veem.com/oauth/authorize
Token URL
https://api.veem.com/oauth/token
Flows
clientCredentialsauthorizationCode

Scopes (1)

ScopeDescriptionFlows
all Full access to the Veem Public API on behalf of the authorized account; the only scope Veem documents. clientCredentials, authorizationCode

Source

OAuth Scopes

Raw ↑
generated: '2026-07-21'
method: searched
source: https://developer.veem.com/docs/oauth
docs: https://developer.veem.com/docs/oauth
description: >-
  OAuth scope surface for the Veem Public API. Veem documents a single
  coarse-grained scope, "all", used across both the two-legged
  (client_credentials) and three-legged (authorization_code) flows — there is
  no published per-resource scope or permission catalog. The published OpenAPI
  slices declare no oauth2 securitySchemes, so the mechanical derive pass found
  no in-spec scopes; this file is sourced from the OAuth guide.
schemes:
  - name: OAuth2
    source: https://developer.veem.com/docs/oauth
    flows:
      - flow: clientCredentials
        tokenUrl: https://api.veem.com/oauth/token
      - flow: authorizationCode
        authorizationUrl: https://api.veem.com/oauth/authorize
        tokenUrl: https://api.veem.com/oauth/token
scopes:
  - scope: all
    description: Full access to the Veem Public API on behalf of the authorized account; the only scope Veem documents.
    flows: [clientCredentials, authorizationCode]
    sources: [https://developer.veem.com/docs/oauth]

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/veem-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.

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