PolySign · OAuth Scopes

PolySign OAuth Scopes

OAuth 2.0 derived

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

Tokens are issued from /v1/auth/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.

digital-assetsblockchaininstitutional-custodysettlementescrowcapital-marketspaymentsfintechdistributed-ledgeratomicnet

Scopes: 1 Flows: clientCredentials Method: derived

OAuth endpoints

Token URL
/v1/auth/token

Flows
clientCredentials

Scopes (1)

Scope	Description	Flows
participant	Grants access to participant.	clientCredentials

📄 Provider scope reference:

Source

OAuth Scopes

generated: '2026-08-02'
method: derived
source: openapi/polysign-abc-proxy-service-openapi.json, openapi/polysign-atomicnet-api-server-openapi.json,
  openapi/polysign-merchant-gate-openapi.json
schemes:
- name: OAuth2
  source: openapi/polysign-abc-proxy-service-openapi.json
  flows:
  - flow: clientCredentials
    tokenUrl: /v1/auth/token
  description: OAuth 2.0 with the client credentials grant flow.
- name: OAuth2
  source: openapi/polysign-atomicnet-api-server-openapi.json
  flows:
  - flow: clientCredentials
    tokenUrl: /v1/auth/token
  description: OAuth 2.0 with the client credentials grant flow.
- name: OAuth2
  source: openapi/polysign-merchant-gate-openapi.json
  flows:
  - flow: clientCredentials
    tokenUrl: /v1/auth/token
  description: OAuth 2.0 with the client credentials grant flow.
scopes:
- scope: participant
  description: Grants access to participant.
  flows:
  - clientCredentials
  sources:
  - openapi/polysign-abc-proxy-service-openapi.json
  - openapi/polysign-atomicnet-api-server-openapi.json
  - openapi/polysign-merchant-gate-openapi.json