Sharing remote configuration

The Italian version constitutes the only official and legally binding version of the document. The English-language version of this document is provided solely as a courtesy to facilitate consultation by users. In the event of any discrepancies, interpretive differences, or inconsistencies between the Italian-language version and any translated version, the Italian text alone shall prevail and be deemed authoritative.

This configuration is necessary if you want to use one of the following functions:

For both functions, it is in fact necessary to **provide a**REST web service in compliance with the relative OpenAPI.

The service must **have 2 or 3 **endpoints, depending on the type of agreement you signed with PagoPA, which the IO backend will call when necessary:

For details about how to design the endpoints and the relative APIs, refer to [openapi-recovery-endpoint-of-remote-content.md](../api-and-specifications/openapi-recovery-endpoint-of-remote-content.md "mention").

Once ready, inform the IO team of the endpoints (indicating the base URL) and the relative Api key that IO will use for authentication at your systems.

To communicate the configuration to the IO team, use the email address [io-service-management@pagopa.it](mailto:io-service-management@pagopa.it).

For all other requests, remember that the address to use to communicate with IO is onboarding@pagopa.it.

Haven't completed onboarding yet and need help?

Write an email describing your problem or question to the address areariservata@assistenza.pagopa.it.

Need help with APIs and Integration?

Write an email describing your problem or question to the address:

io-service-management@pagopa.it

Tell us what you think

To report problems or give feedback, leave a comment in the GitHub space of the IO app

Signed agreement	Preconditions	Message details	Attachments
Standard
Fast
Premium

Table of contents

Haven't completed onboarding yet and need help?

Need help with APIs and Integration?

Tell us what you think