Signicat · OAuth Scopes

Signicat OAuth Scopes

OAuth 2.0 searched

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

Tokens are issued from http://api.signicat.com/auth/open/connect/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.

CompanyDigital IdentityAuthenticationE-SignatureKYCIdentity VerificationeIDFraud Prevention
Scopes: 2 Flows: clientCredentials, authorizationCode Method: searched

OAuth endpoints

Authorization URL
http://api.signicat.com/auth/open/connect/authorize
Token URL
http://api.signicat.com/auth/open/connect/token /oidc/token
Flows
clientCredentialsauthorizationCode

Scopes (2)

ScopeDescriptionFlows
openid OpenID User id authorizationCode
signicat-api Signicat API authorizationCode, clientCredentials

Source

OAuth Scopes

Raw ↑
generated: '2026-10-18'
method: searched
source: openapi/signicat-oidc-config-openapi.yml, openapi/signicat-reuseid-onboarding-openapi.yml,
  openapi/signicat-signing-enterprise-openapi.yml, https://developer.signicat.com/docs/dashboard/access-management/managing-roles-and-permissions.md
schemes:
- name: Signicat-OIDC
  source: openapi/signicat-oidc-config-openapi.yml
  flows:
  - flow: clientCredentials
    tokenUrl: http://api.signicat.com/auth/open/connect/token
  - flow: authorizationCode
    authorizationUrl: http://api.signicat.com/auth/open/connect/authorize
    tokenUrl: http://api.signicat.com/auth/open/connect/token
- name: Token
  source: openapi/signicat-reuseid-onboarding-openapi.yml
  flows:
  - flow: clientCredentials
- name: signrestOauth2Security
  source: openapi/signicat-signing-enterprise-openapi.yml
  flows:
  - flow: clientCredentials
    tokenUrl: /oidc/token
  description: Signicat Oauth security with clientCredentials
scopes:
- scope: openid
  description: OpenID User id
  flows:
  - authorizationCode
  sources:
  - openapi/signicat-oidc-config-openapi.yml
- scope: signicat-api
  description: Signicat API
  flows:
  - authorizationCode
  - clientCredentials
  sources:
  - openapi/signicat-oidc-config-openapi.yml
  - openapi/signicat-signing-enterprise-openapi.yml

docs: https://developer.signicat.com/docs/dashboard/access-management/managing-roles-and-permissions.md
permissions_model:
  description: Role-based access control with four basic role types (Viewer, Writer, Editor, Admin) that group permissions
  roles:
  - name: Organisation Admin
    description: Has all permissions for the organisation and all accounts belonging to that organisation
    scope: organisation
  - name: Account Admin
    description: Has all permissions for a given account but not for the overlying organisation
    scope: account
  - name: Usage Viewer
    description: Access to view usage and invoices
    scope: organisation
  - name: Support Editor
    description: Access to create, update and view support tickets and comments, including sensitive data
    scope: organisation

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