PagoPA · Schema

SingleFlowCreatedResponse

CompanyPaymentsGovernmentPublic SectorDigital IdentityInteroperabilityNotificationsItaly

Properties

Name Type Description
status object
revision integer The revision (or version) of the flow.
created object
updated object
fdr string The unique identifier of the flow.
fdrDate object
regulation string The description related to the regulation payment related to the flow.
regulationDate object
bicCodePouringBank string The BIC code of the bank where the regulation payment related to the flow will be poured.
sender object
receiver object
computedTotPayments integer The computed total number of payments included in the flow during the compilation.
computedSumPayments number The computed total amount of payments calculated in the flow during the compilation.
totPayments integer The total number of payments to be included in the flow during the flow compilation.
sumPayments number The total amount of payments to be calculated in the flow during the flow compilation.
View JSON Schema on GitHub

JSON Schema

pagopa-single-flow-created-response-schema.json Raw ↑
{
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "$id": "https://raw.githubusercontent.com/api-evangelist/pagopa/main/json-schema/pagopa-single-flow-created-response-schema.json",
  "title": "SingleFlowCreatedResponse",
  "x-generated": "2026-10-09",
  "x-method": "derived",
  "x-generator": "derive-json-schema.py",
  "x-source": "openapi/pagopa-fdr-psp-openapi.yml#/components/schemas/SingleFlowCreatedResponse",
  "type": "object",
  "properties": {
    "status": {
      "$ref": "#/$defs/ReportingFlowStatusEnum"
    },
    "revision": {
      "type": "integer",
      "description": "The revision (or version) of the flow.",
      "format": "int64"
    },
    "created": {
      "$ref": "#/$defs/Instant"
    },
    "updated": {
      "$ref": "#/$defs/Instant"
    },
    "fdr": {
      "type": "string",
      "description": "The unique identifier of the flow."
    },
    "fdrDate": {
      "$ref": "#/$defs/Instant"
    },
    "regulation": {
      "type": "string",
      "description": "The description related to the regulation payment related to the flow."
    },
    "regulationDate": {
      "$ref": "#/$defs/LocalDate"
    },
    "bicCodePouringBank": {
      "type": "string",
      "description": "The BIC code of the bank where the regulation payment related to the flow will be poured."
    },
    "sender": {
      "$ref": "#/$defs/Sender"
    },
    "receiver": {
      "$ref": "#/$defs/Receiver"
    },
    "computedTotPayments": {
      "type": "integer",
      "description": "The computed total number of payments included in the flow during the compilation.",
      "format": "int64"
    },
    "computedSumPayments": {
      "pattern": "^\\d{1,2147483647}[.]\\d{1,2}?$",
      "type": "number",
      "description": "The computed total amount of payments calculated in the flow during the compilation.",
      "format": "double"
    },
    "totPayments": {
      "type": "integer",
      "description": "The total number of payments to be included in the flow during the flow compilation.",
      "format": "int64"
    },
    "sumPayments": {
      "pattern": "^\\d{1,2147483647}[.]\\d{1,2}?$",
      "type": "number",
      "description": "The total amount of payments to be calculated in the flow during the flow compilation.",
      "format": "double"
    }
  },
  "$defs": {
    "Instant": {
      "type": "string",
      "format": "date-time"
    },
    "LocalDate": {
      "type": "string",
      "format": "date"
    },
    "Receiver": {
      "required": [
        "id",
        "organizationId",
        "organizationName"
      ],
      "type": "object",
      "properties": {
        "id": {
          "pattern": "^(.{1,35})$",
          "type": "string",
          "description": "The identifier of the Creditor Institution receiver entity.<br>In the XML request for SOAP primitives, this field is mappable with the tag <b>[FlussoRiversamento.istitutoRicevente.identificativoUnivocoRicevente.codiceIdentificativoUnivoco]</b>."
        },
        "organizationId": {
          "pattern": "^(.{1,35})$",
          "type": "string",
          "description": "The domain identifier of the Creditor Institution receiver entity.<br>In the XML request for SOAP primitives, this field is mappable with the tag <b>[NodoInviaFlussoRendicontazione.identificativoDominio]</b>."
        },
        "organizationName": {
          "pattern": "^(.{1,140})$",
          "type": "string",
          "description": "The fiscal name of the Creditor Institution receiver entity.<br>In the XML request for SOAP primitives, this field is mappable with the tag <b>[FlussoRiversamento.istitutoRicevente.denominazioneRicevente]</b>."
        }
      }
    },
    "ReportingFlowStatusEnum": {
      "enum": [
        "CREATED",
        "INSERTED",
        "PUBLISHED"
      ],
      "type": "string"
    },
    "Sender": {
      "required": [
        "type",
        "id",
        "pspId",
        "pspName",
        "pspBrokerId",
        "channelId"
      ],
      "type": "object",
      "properties": {
        "type": {
          "$ref": "#/$defs/SenderTypeEnum"
        },
        "id": {
          "pattern": "^(.{1,35})$",
          "type": "string",
          "description": "The identifier of the PSP sender entity.<br>In the XML request for SOAP primitives, this field is mappable with the tag <b>[FlussoRiversamento.istitutoMittente.identificativoUnivocoMittente.codiceIdentificativoUnivoco]</b>."
        },
        "pspId": {
          "pattern": "^(.{1,35})$",
          "type": "string",
          "description": "The domain identifier of the PSP sender entity.<br>In the XML request for SOAP primitives, this field is mappable with the tag <b>[NodoInviaFlussoRendicontazione.identificativoPSP]</b>."
        },
        "pspName": {
          "pattern": "^(.{3,70})$",
          "type": "string",
          "description": "The fiscal name of the PSP sender entity.<br>In the XML request for SOAP primitives, this field is mappable with the tag <b>[FlussoRiversamento.istitutoMittente.denominazioneMittente]</b>."
        },
        "pspBrokerId": {
          "pattern": "^(.{1,35})$",
          "type": "string",
          "description": "The domain identifier of the PSP sender entity's Broker.<br>In the XML request for SOAP primitives, this field is mappable with the tag <b>[NodoInviaFlussoRendicontazione.identificativoIntermediarioPSP]</b>."
        },
        "channelId": {
          "pattern": "^(.{1,35})$",
          "type": "string",
          "description": "The identifier of the PSP sender entity's Channel.<br>In the XML request for SOAP primitives, this field is mappable with the tag <b>[NodoInviaFlussoRendicontazione.identificativoCanale]</b>."
        },
        "password": {
          "pattern": "^(\\w{8,15})$",
          "type": "string",
          "description": "The password of the PSP sender entity's Channel.<br>In the XML request for SOAP primitives, this field is mappable with the tag <b>[NodoInviaFlussoRendicontazione.password]</b>.",
          "deprecated": true
        }
      }
    },
    "SenderTypeEnum": {
      "enum": [
        "LEGAL_PERSON",
        "ABI_CODE",
        "BIC_CODE"
      ],
      "type": "string"
    }
  }
}

Work with this as data

Every JSON Schema 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 schemas

4 MCP tools reach this
  • find_json_schemasBrowse and filter every JSON Schema 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 JSON Schema
curl "https://apis.io/api/v1/json-schemas/pagopa-single-flow-created-response"
All schemas
curl "https://apis.io/api/v1/json-schemas?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.

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