Veem OAuth Scopes
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.
OAuth endpoints
https://api.veem.com/oauth/authorize
https://api.veem.com/oauth/token
clientCredentialsauthorizationCode
Scopes (1)
| Scope | Description | Flows |
|---|---|---|
| all | Full access to the Veem Public API on behalf of the authorized account; the only scope Veem documents. | clientCredentials, authorizationCode |
📄 Provider scope reference: https://developer.veem.com/docs/oauth
Source
OAuth Scopes
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.
Call it yourself
curl for this page
curl "https://apis.io/api/v1/scopes/veem-scopes"
curl "https://apis.io/api/v1/scopes?limit=25"
Discovery needs no key. Ratings and market analysis are Pro.