InfoCert · OAuth Scopes

InfoCert OAuth Scopes

OAuth 2.0 derived

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

Tokens are issued from https://idpstage.infocert.digital/auth/realms/delivery/protocol/openid-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 TrustElectronic SignaturesDigital IdentityCertified EmailE-InvoicingTrust ServiceseIDAS

Scopes: 13 Flows: clientCredentials, authorizationCode, password Method: derived

OAuth endpoints

Authorization URL
https://idp.infocert.digital/auth/realms/edelivery/protocol/openid-connect/auth https://gosign-be.infocert.it/gosign/oauth/authorize https://idp.infocert.digital/auth/realms/safe/protocol/openid-connect/auth

Token URL
https://idpstage.infocert.digital/auth/realms/delivery/protocol/openid-connect/token https://idp.infocert.digital/auth/realms/delivery/protocol/openid-connect/token https://idp.infocert.digital/auth/realms/edelivery/protocol/openid-connect/token https://gosign-be.infocert.it/gosign/oauth/token https://infocertsign.com:{port}/oauth/token https://corporate-be.infocertsign.com:{port}/be/oauth/token https://idpstage.infocert.digital/auth/realms/infocert-sign-mt/protocol/openid-connect/token https://{server_idp}/auth/realms/delivery/protocol/openid-connect/token /api/v2/token https://idp.infocert.digital/auth/realms/safe/protocol/openid-connect/token

Flows
clientCredentialsauthorizationCodepassword

Scopes (13)

Scope	Description	Flows
afm	afm scope	clientCredentials
busapiv2-mailboxes:org-msg	Operations to organise messages	clientCredentials
busapiv2-mailboxes:riconciliazione	Operations to retrieve the status of submissions	clientCredentials
edelivery	This scope is required	authorizationCode, password
identification	identification scope	clientCredentials
identification-iqp		clientCredentials
openid	Required	clientCredentials
preservation	preservation scope	clientCredentials
read	Grant read-only access to all data	authorizationCode, password
signature	signature scope to perform both signature and timestamp	clientCredentials
timestamp	timestamp scope	clientCredentials
validate-contact	validate contact scope	clientCredentials
write	Grant write-only access to all data	authorizationCode, password

📄 Provider scope reference:

Source

OAuth Scopes

generated: '2026-10-18'
method: derived
source: openapi/infocert-ai-face-matching-openapi.yml, openapi/infocert-contact-validation-openapi.yml,
  openapi/infocert-gonotice-openapi.yml, openapi/infocert-gosign-ext-5-1-openapi.yml, openapi/infocert-gosign-ext-5r1-openapi.yml,
  openapi/infocert-gosign5-openapi.yml, openapi/infocert-infocert-sign-ext-5-1-openapi.yml,
  openapi/infocert-infocert-sign-other-services-openapi.yml, openapi/infocert-infocert-sign-provisioning-admin-openapi.yml,
  openapi/infocert-infocert-sign-provisioning-inbound-openapi.yml, openapi/infocert-iqp-openapi.yml,
  openapi/infocert-legalmail-business-mailboxes-openapi.yml, openapi/infocert-qualified-preservation-openapi.yml,
  openapi/infocert-safe-lta-business-openapi.yml, openapi/infocert-safe-lta-provisioning-core-openapi.yml,
  openapi/infocert-timestamp-openapi.yml
schemes:
- name: oauth2
  source: openapi/infocert-ai-face-matching-openapi.yml
  flows:
  - flow: clientCredentials
    tokenUrl: https://idpstage.infocert.digital/auth/realms/delivery/protocol/openid-connect/token
- name: oauth2
  source: openapi/infocert-contact-validation-openapi.yml
  flows:
  - flow: clientCredentials
    tokenUrl: https://idp.infocert.digital/auth/realms/delivery/protocol/openid-connect/token
- name: oAuth2
  source: openapi/infocert-gonotice-openapi.yml
  flows:
  - flow: authorizationCode
    authorizationUrl: https://idp.infocert.digital/auth/realms/edelivery/protocol/openid-connect/auth
    tokenUrl: https://idp.infocert.digital/auth/realms/edelivery/protocol/openid-connect/token
  - flow: password
    tokenUrl: https://idp.infocert.digital/auth/realms/edelivery/protocol/openid-connect/token
  description: Oauth2 information
- name: oAuth2
  source: openapi/infocert-gosign-ext-5-1-openapi.yml
  flows:
  - flow: clientCredentials
    tokenUrl: https://gosign-be.infocert.it/gosign/oauth/token
  description: See https://www.oauth.com/oauth2-servers/access-tokens/client-credentials/
- name: oAuth2
  source: openapi/infocert-gosign-ext-5r1-openapi.yml
  flows:
  - flow: clientCredentials
    tokenUrl: https://gosign-be.infocert.it/gosign/oauth/token
  description: See https://www.oauth.com/oauth2-servers/access-tokens/client-credentials/
- name: oAuth2
  source: openapi/infocert-gosign5-openapi.yml
  flows:
  - flow: authorizationCode
    authorizationUrl: https://gosign-be.infocert.it/gosign/oauth/authorize
    tokenUrl: https://gosign-be.infocert.it/gosign/oauth/token
  - flow: password
    tokenUrl: https://gosign-be.infocert.it/gosign/oauth/token
- name: oAuth2
  source: openapi/infocert-infocert-sign-ext-5-1-openapi.yml
  flows:
  - flow: clientCredentials
    tokenUrl: https://infocertsign.com:{port}/oauth/token
  description: See https://www.oauth.com/oauth2-servers/access-tokens/client-credentials/
- name: oAuth2
  source: openapi/infocert-infocert-sign-other-services-openapi.yml
  flows:
  - flow: clientCredentials
    tokenUrl: https://corporate-be.infocertsign.com:{port}/be/oauth/token
  description: See https://www.oauth.com/oauth2-servers/access-tokens/client-credentials/
- name: oAuth2
  source: openapi/infocert-infocert-sign-provisioning-admin-openapi.yml
  flows:
  - flow: clientCredentials
    tokenUrl: https://idpstage.infocert.digital/auth/realms/infocert-sign-mt/protocol/openid-connect/token
  description: See https://www.oauth.com/oauth2-servers/access-tokens/client-credentials/
- name: oAuth2
  source: openapi/infocert-infocert-sign-provisioning-inbound-openapi.yml
  flows:
  - flow: clientCredentials
    tokenUrl: https://idpstage.infocert.digital/auth/realms/infocert-sign-mt/protocol/openid-connect/token
  description: See https://www.oauth.com/oauth2-servers/access-tokens/client-credentials/
- name: Authentication
  source: openapi/infocert-iqp-openapi.yml
  flows:
  - flow: clientCredentials
    tokenUrl: https://{server_idp}/auth/realms/delivery/protocol/openid-connect/token
  description: See https://developers.infocert.digital/identification/how-to-use-iqp-api/
- name: busapiv2_mailboxes_oauth2
  source: openapi/infocert-legalmail-business-mailboxes-openapi.yml
  flows:
  - flow: clientCredentials
    tokenUrl: /api/v2/token
  description: This API uses OAuth 2 with the [Client Credentials Flow](https://auth0.com/docs/get-started/authentication-and-authorization-flow/client-credentials-flow).
- name: oauth2
  source: openapi/infocert-qualified-preservation-openapi.yml
  flows:
  - flow: clientCredentials
    tokenUrl: https://idpstage.infocert.digital/auth/realms/delivery/protocol/openid-connect/token
- name: oauth2
  source: openapi/infocert-safe-lta-business-openapi.yml
  flows:
  - flow: authorizationCode
    authorizationUrl: https://idp.infocert.digital/auth/realms/safe/protocol/openid-connect/auth
    tokenUrl: https://idp.infocert.digital/auth/realms/safe/protocol/openid-connect/token
  - flow: password
    tokenUrl: https://idp.infocert.digital/auth/realms/safe/protocol/openid-connect/token
  - flow: clientCredentials
    tokenUrl: https://idp.infocert.digital/auth/realms/safe/protocol/openid-connect/token
- name: oauth2
  source: openapi/infocert-safe-lta-provisioning-core-openapi.yml
  flows:
  - flow: authorizationCode
    authorizationUrl: https://idp.infocert.digital/auth/realms/safe/protocol/openid-connect/auth
    tokenUrl: https://idp.infocert.digital/auth/realms/safe/protocol/openid-connect/token
  - flow: password
    tokenUrl: https://idp.infocert.digital/auth/realms/safe/protocol/openid-connect/token
  - flow: clientCredentials
    tokenUrl: https://idp.infocert.digital/auth/realms/safe/protocol/openid-connect/token
- name: oauth2
  source: openapi/infocert-timestamp-openapi.yml
  flows:
  - flow: clientCredentials
    tokenUrl: https://idpstage.infocert.digital/auth/realms/delivery/protocol/openid-connect/token
scopes:
- scope: afm
  description: afm scope
  flows:
  - clientCredentials
  sources:
  - openapi/infocert-ai-face-matching-openapi.yml
- scope: busapiv2-mailboxes:org-msg
  description: Operations to organise messages
  flows:
  - clientCredentials
  sources:
  - openapi/infocert-legalmail-business-mailboxes-openapi.yml
- scope: busapiv2-mailboxes:riconciliazione
  description: Operations to retrieve the status of submissions
  flows:
  - clientCredentials
  sources:
  - openapi/infocert-legalmail-business-mailboxes-openapi.yml
- scope: edelivery
  description: This scope is required
  flows:
  - authorizationCode
  - password
  sources:
  - openapi/infocert-gonotice-openapi.yml
- scope: identification
  description: identification scope
  flows:
  - clientCredentials
  sources:
  - openapi/infocert-ai-face-matching-openapi.yml
- scope: identification-iqp
  flows:
  - clientCredentials
  sources:
  - openapi/infocert-iqp-openapi.yml
- scope: openid
  description: Required
  flows:
  - clientCredentials
  sources:
  - openapi/infocert-gosign-ext-5-1-openapi.yml
  - openapi/infocert-gosign-ext-5r1-openapi.yml
  - openapi/infocert-infocert-sign-ext-5-1-openapi.yml
  - openapi/infocert-infocert-sign-other-services-openapi.yml
  - openapi/infocert-infocert-sign-provisioning-admin-openapi.yml
  - openapi/infocert-infocert-sign-provisioning-inbound-openapi.yml
- scope: preservation
  description: preservation scope
  flows:
  - clientCredentials
  sources:
  - openapi/infocert-qualified-preservation-openapi.yml
- scope: read
  description: Grant read-only access to all data
  flows:
  - authorizationCode
  - password
  sources:
  - openapi/infocert-gosign5-openapi.yml
- scope: signature
  description: signature scope to perform both signature and timestamp
  flows:
  - clientCredentials
  sources:
  - openapi/infocert-timestamp-openapi.yml
- scope: timestamp
  description: timestamp scope
  flows:
  - clientCredentials
  sources:
  - openapi/infocert-timestamp-openapi.yml
- scope: validate-contact
  description: validate contact scope
  flows:
  - clientCredentials
  sources:
  - openapi/infocert-contact-validation-openapi.yml
- scope: write
  description: Grant write-only access to all data
  flows:
  - authorizationCode
  - password
  sources:
  - openapi/infocert-gosign5-openapi.yml

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

GitHub Google LinkedIn

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