AdvicePay · OAuth Scopes

AdvicePay OAuth Scopes

OAuth 2.0 searched

AdvicePay 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 AdvicePay API on a user’s behalf.

Tokens are issued from https://app.advicepay.com/oauth2/access_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.

Financial ServicesPaymentsBillingInvoicingFinancial PlanningWealth ManagementSubscriptionE-SignatureComplianceFintech
Scopes: 1 Flows: authorizationCode, clientCredentials Method: searched

OAuth endpoints

Authorization URL
https://app.advicepay.com/oauth2/authorize
Token URL
https://app.advicepay.com/oauth2/access_token
Flows
authorizationCodeclientCredentials

Scopes (1)

ScopeDescriptionFlows
all Full access to the AdvicePay public API on behalf of the authorizing user or account owner. The only scope value the authorization endpoint accepts. authorizationCode, clientCredentials

Source

OAuth Scopes

advicepay-scopes.yml Raw ↑
generated: '2026-09-09'
method: searched
source: https://docs.advicepay.com/#oauth-authorization-code-flow
docs: https://docs.advicepay.com/#authentication
note: >-
  AdvicePay publishes no OpenAPI, so derive-oauth-scopes.py has no spec to read; this file was
  written from the published OAuth documentation instead. AdvicePay operates OAuth 2.0 but has
  not (yet) decomposed access into granular scopes — the docs state plainly that "Currently, only
  'all' is supported" for the scope parameter on the authorization request. Authorization is
  therefore all-or-nothing at the token level and is narrowed instead by the role of the
  authorizing user (admin / advisor / account owner) and by the plan. This is an honest record of
  a single coarse scope, not a gap in our reading.
schemes:
- name: OAuth2
  source: https://docs.advicepay.com/#authentication
  flows:
  - flow: authorizationCode
    authorizationUrl: https://app.advicepay.com/oauth2/authorize
    tokenUrl: https://app.advicepay.com/oauth2/access_token
  - flow: clientCredentials
    tokenUrl: https://app.advicepay.com/oauth2/access_token
scopes:
- scope: all
  description: >-
    Full access to the AdvicePay public API on behalf of the authorizing user or account owner.
    The only scope value the authorization endpoint accepts.
  flows:
  - authorizationCode
  - clientCredentials
  sources:
  - https://docs.advicepay.com/#oauth-authorization-code-flow
scope_granularity: coarse
scope_count: 1
effective_authorization:
  model: role-and-tenant
  description: >-
    Because there is one scope, what a token can actually reach is decided by who authorized it.
    An authorization-code token is bound to a single AdvicePay user and inherits that user's role
    (admin, advisor, reviewer) and office/firm boundary; a client-credentials token acts as the
    enterprise account owner across the firm. The /me endpoint is the documented way for an
    integrator to discover which identity and role a token actually carries.
  discovery_operation: GET /api/public/v1/me

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

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