DevPortalPagoPA

Table of contents

Common errors

Error 429

All the APIs can return the "429” status code. This error represents an IO infrastructure overload signal: in this case, it is necessary to implement a retry mechanism and reduce the rate of the requests, inserting pauses.

Error 400

1{
2  "detail": "value [undefined] at [root.0] is not a valid [Exact<NewMessage>]\nvalue [undefined] at [root.1] is not a valid [{ time_to_live: (integer >= 3600 and < 604800 | 604800) }]",
3  "status": 400,
4  "title": "Invalid (Exact<NewMessage> & { time_to_live: (integer >= 3600 and < 604800 | 604800) })"
5}
6
In this case the error is due to an incorrect transmission of the body, such as a body not sent in the correct format (JSON), for example.

Error 401

1{
2  "statusCode": 401,
3  "message": "Access denied due to invalid subscription key. Make sure to provide a valid key for an active subscription."
4}
5
In this case, make sure to have entered the correct value of the key Ocp-Apim-Subscription-Key in the header. Use one of the two keys present in the "Profile (subscriptions)" section of the portal.
1{
2   "statusCode": 401,
3   "message": "Access denied due to missing subscription key. Make sure to include subscription key when making requests to an API."
4}
5
In this case, make sure to have entered the value of the key Ocp-Apim-Subscription-Key in the request header. Use one of the two keys present in the "Profile (subscriptions)" section of the portal.

Error 403

1{
2  "detail": "You are not allowed to issue requests for the recipient.",
3  "status": 403,
4  "title": "Recipient forbidden"
5}
6
In this case, make sure to have entered a valid fiscal code that is present in the test.
1{
2   "detail": "You do not have enough permission to complete the operation you requested",
3   "status": 403,
4   "title": "You are not allowed here"
5}
6
In this case, make sure to have entered a valid IP in the original IP LIST authorized by the service or to have signed the additional Premium contract and to have performed the required onboarding procedures.

Error 404

1{
2  "statusCode": 404,
3  "message": "Resource not found"
4}
5
In this case, make sure to have written the path of the request correctly, e.g.: https://api.io.pagopa.it/api/v1/profiles

On this page

Error 429

Error 400

Error 401

Error 403

Error 404

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