DevPortalPagoPA




Table of contents

📥 Massive management via SFTP

Access credentials

The first step to perform for activating the service is the request to create credentials for accessing the SFTP server.
The request must be sent directly to the pagoPA-Core team at pagopa-core@pagopa.it , specifying the name and last name of the technical representative and an email to which the credentials will be sent.
Once the request is processed, the parameters will be sent for accessing the SFTP folder containing two subfolders, one for input for depositing the files containing the list of the debt positions to be loaded (ref. Input trace specifications),and one for output where the platform will provide the outcome of the loading.
Access credentials:
  • path - connection string es. pagopadweugpsgpdsasftp.\<USERNAME_INPUT>@pagopadweugpsgpdsasftp.blob.core.windows.net
  • password - password for the user USERNAME_INPUT
Each partner/intermediary will therefore have a folder available, identified by the fiscal code/VAT no. and that has the following structure:
1/CF_BROKER_01
2    | CF_EC_01
3        | /input
4        | /output
5    | CF_EC_02
6        | /input
7        | /output
8/CF_BROKER_02
9    | CF_EC_03
10        | /input
11        | /output
12

File loading

To trigger the process for loading the debt positions, it is necessary to connect to the folder /CF_BROKER_ID/CF_EC_ID/input using the access credentials and upload one or more files in JSON format.
Uploading the file to the folder triggers the massive creation, update and deletion process that will have a variable duration based on the size of the loaded files.
Once massive loading is complete, a receipt will be produced for each file in the folder /CF_BROKER_ID/CF_EC_ID/output, the receipt is structured as follows:
1{
2  "uploadID": "string",
3  "processedItem": "integer",
4  "submittedItem": "integer",
5  "responses": [
6    {
7      "statusCode": "integer",
8      "statusMessage": "string",
9      "requestIDs": [
10        "string"
11      ]
12    }
13  ],
14  "startTime": "string($date-time)",
15  "endTime": "string($date-time)"
16}
17
  • uploadID - univocal identifier of the loaded file (coincides with the file name in the case of SFTP)
  • responses - the list of the loading outcomes grouped by state code and details.
  • requestIDs - the list of the debt position IDs, e.g. IUPD
  • startTime - Date and time of upload process completion
  • endTime - Date and time of upload process completion

Need help?

Open a ticket using the dedicated function within your Reserved Area

Tell us what you think

For clarifications on implementation specifications, such as SACI and SANP, you can open an issue on GitHub