PagoPA · OAuth Scopes

PagoPA OAuth Scopes

OAuth 2.0 derived

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

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

CompanyPaymentsGovernmentPublic SectorDigital IdentityInteroperabilityNotificationsItaly

Scopes: 6 Flows: clientCredentials Method: derived

OAuth endpoints

Token URL
/token https://api-mcshared.cstar.pagopa.it/auth-itn/realms/merchant-operator/protocol/openid-connect/token https://api-mcshared.cstar.pagopa.it/auth-itn/realms/srtp/protocol/openid-connect/token

Flows
clientCredentials

Scopes (6)

Scope	Description	Flows
admin_rtp_activations	Grants full administrative access to all activations.	clientCredentials
read_rtp_activations	Read RTP activation belonging to the requesting subject.	clientCredentials
read_rtp_all	Read all RTP activations.	clientCredentials
read_rtp_payees	Grants permission to read the RTP Payees registry.	clientCredentials
read_rtp_service_providers	Grants permission to read the list of RTP service providers.	clientCredentials
write_rtp_activations	Grants permission to create, update, or delete activations.	clientCredentials

📄 Provider scope reference:

Source

OAuth Scopes

generated: '2026-10-09'
method: derived
source: openapi/pagopa-mdc-citizen-consent-openapi.yml, openapi/pagopa-mdc-payment-openapi.yml,
  openapi/pagopa-mdc-tpp-testing-openapi.yml, openapi/pagopa-pari-ecommerce-openapi.yml, openapi/pagopa-srtp-activation-openapi.yml,
  openapi/pagopa-srtp-payees-openapi.yml, openapi/pagopa-srtp-service-providers-openapi.yml
schemes:
- name: oAuth2
  source: openapi/pagopa-mdc-citizen-consent-openapi.yml
  flows:
  - flow: clientCredentials
    tokenUrl: /token
  description: |-
    A bearer token in the format of a JWS and conforms to the specifications
    included in RFC8725.
- name: oAuth2
  source: openapi/pagopa-mdc-payment-openapi.yml
  flows:
  - flow: clientCredentials
    tokenUrl: /token
  description: |-
    A bearer token in the format of a JWS and conforms to the specifications
    included in RFC8725.
- name: oAuth2
  source: openapi/pagopa-mdc-tpp-testing-openapi.yml
  flows:
  - flow: clientCredentials
    tokenUrl: /token
  description: |-
    A bearer token in the format of a JWS and conforms to the specifications
    included in RFC8725.
- name: Bearer
  source: openapi/pagopa-pari-ecommerce-openapi.yml
  flows:
  - flow: clientCredentials
    tokenUrl: https://api-mcshared.cstar.pagopa.it/auth-itn/realms/merchant-operator/protocol/openid-connect/token
  description: A bearer token in the format of a JWS and conforms to the specifications included
    in RFC8725.
- name: oAuth2
  source: openapi/pagopa-srtp-activation-openapi.yml
  flows:
  - flow: clientCredentials
    tokenUrl: https://api-mcshared.cstar.pagopa.it/auth-itn/realms/srtp/protocol/openid-connect/token
  description: |-
    A bearer token in the format of a JWS and conforms to the specifications
    included in RFC8725.
- name: oAuth2
  source: openapi/pagopa-srtp-payees-openapi.yml
  flows:
  - flow: clientCredentials
    tokenUrl: https://api-mcshared.cstar.pagopa.it/auth-itn/realms/srtp/protocol/openid-connect/token
  description: Authentication is handled via OAuth2 Client Credentials flow. Clients must obtain
    a Bearer token (JWT), which conforms to RFC8725, and include it in the `Authorization` header
    of their requests.
- name: oAuth2
  source: openapi/pagopa-srtp-service-providers-openapi.yml
  flows:
  - flow: clientCredentials
    tokenUrl: https://api-mcshared.cstar.pagopa.it/auth-itn/realms/srtp/protocol/openid-connect/token
  description: Authentication is handled via OAuth2 Client Credentials flow. Clients must obtain
    a Bearer token (JWT), which conforms to RFC8725, and include it in the `Authorization` header
    of their requests.
scopes:
- scope: admin_rtp_activations
  description: Grants full administrative access to all activations.
  flows:
  - clientCredentials
  sources:
  - openapi/pagopa-srtp-activation-openapi.yml
- scope: read_rtp_activations
  description: Read RTP activation belonging to the requesting subject.
  flows:
  - clientCredentials
  sources:
  - openapi/pagopa-srtp-activation-openapi.yml
- scope: read_rtp_all
  description: Read all RTP activations.
  flows:
  - clientCredentials
  sources:
  - openapi/pagopa-srtp-activation-openapi.yml
- scope: read_rtp_payees
  description: Grants permission to read the RTP Payees registry.
  flows:
  - clientCredentials
  sources:
  - openapi/pagopa-srtp-payees-openapi.yml
- scope: read_rtp_service_providers
  description: Grants permission to read the list of RTP service providers.
  flows:
  - clientCredentials
  sources:
  - openapi/pagopa-srtp-service-providers-openapi.yml
- scope: write_rtp_activations
  description: Grants permission to create, update, or delete activations.
  flows:
  - clientCredentials
  sources:
  - openapi/pagopa-srtp-activation-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/pagopa-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.