Getting Started with the Electronic Invoicing API (SdI via POP)
\nTo start sending electronic invoices through the POP system (e.g. SdI for Italy), follow these steps:
\n1. Create a POP Account
\nFirst, sign up for a POP account with at least the Growth plan.
\n2. Enable SdI Integration
\nOnce your account is active, go to your User Area and open the Integrations panel.
\n- \n
Select the SdI via POP integration.
\n \nEnable your company for electronic invoicing and choose from the following optional features:
\n- \n
β Apply digital signature before sending invoices to SdI
\n \nβ Apply legal storage for sent invoices
\n \n
\n
3. Access API Endpoints
\nOnce your company is connected and the SdI integration is enabled, you are authorized to use the API endpoints for sending invoices.
\nYou can now proceed to authenticate and interact with the available endpoints described below.
\n\n
Using SDI via POP Integration
\nπ Authentication
\nAll requests require the inclusion of a valid license_key in the main payload.
\n
π¦ Payload Structure
\nTo create an invoice that will be managed and sent via SdI through POP integration, you need to include the following integration object in the payload using the{{base_url}}/wp-json/api/v2/create-xml endpoint
{\n \"license_key\": \"your_license_key\",\n \"data\": { ... },\n \"integration\": {\n \"use\": \"sdi-via-pop\",\n \"action\": \"create\"\n }\n}\n\nThis instructs the system to:
\n- \n
- Generate the XML invoice using the SdI integration. \n
β Successful Response
\nWhen the invoice is successfully created using the SdI via POP integration, the API will return a JSON response like the following:
\n{\n \"integration\": \"SdI via POP\",\n \"message\": \"Invoice created successfully!\",\n \"data\": {\n \"uuid\": \"0197200c-b922-78e2-99b6-1b4d40969ba8\"\n },\n \"code\": 201,\n \"success\": true\n}\n\nResponse Fields
\n- \n
integration: The name of the integration used (
\n\"SdI via POP\"). \nmessage: A human-readable message indicating the result of the operation.
\n \ndata.uuid: The unique identifier (UUID) of the created invoice.
\n
This ID must be used in subsequent requests. \ncode: HTTP status code (202 indicates successful creation).
\n \nsuccess: Boolean value confirming the operation was successful.
\n \n
\n
Verify Invoice
\nEndpoint: {{base_url}}/wp-json/api/v2/sdi-via-pop/document-verify
Method: POST
This endpoint allows you to verify the structure and content of an electronic invoice (in XML format) before submitting it to SdI.
\nUse it to validate the Base64-encoded XML against compliance rules and technical specifications.
\n\n
πΈ Request Payload
\n{\n \"license_key\": \"1ae8b944cbebcf4592ed0b6ac367587e0840dd9e\",\n \"integration\": {\n \"xml\": \"PD94bWwgdmVyc2lvbj0iMS4wIiBlbmNvZGluZz0iVVRGLTgiPz4KPHA6Rm...\"\n }\n}\n\nPayload Parameters
\n- \n
license_key (string, required):
\n
Your POP license key used for authentication. \nintegration.uuid (string, required):
\n
The UUID of the document to be verified. \nintegration.xml (string, required):
\n
The invoice content in Base64-encoded XML format. \n
β Successful Response
\n{\n \"integration\": \"SdI via POP\",\n \"message\": \"Invoice verification successfully!\",\n \"data\": [],\n \"code\": 200,\n \"success\": true\n}\n\nResponse Fields
\n- \n
message: Confirmation that the invoice was verified successfully.
\n \ndata: Empty array if no issues were found.
\n \ncode: HTTP status code 200.
\n \nsuccess: true indicates that the verification passed.
\n \n
\n
Send Invoice to Legal Archive
\nEndpoint: {{base_url}}/wp-json/api/v2/sdi-via-pop/document-preserve
Method: POST
This endpoint is used to send an invoice to the legal preservation system (archivio legale).
\nThe invoice must be eligible for preservation β if not, a 400 Bad Request error will be returned.
π Important Notes
\n- \n
An invoice is considered eligible for preservation when:
\n- \n
It has been successfully submitted to SdI.
\n \nFor B2B invoices, an RC (Ricevuta di Consegna) or MC (Mancata Consegna) notification has been received.
\n \n
\n
\n
πΈ Request Payload
\n{\n \"license_key\": \"1ae8b944cbebcf4592ed0b6ac367587e0840dd9e\",\n \"integration\": {\n \"uuid\": \"01971277-c9d9-76c9-ad53-e640bbdffb8e\"\n }\n}\n\nPayload Parameters
\n- \n
license_key (string, required):
\n
Your POP license key. \nintegration.uuid (string, required):
\n
The UUID of the invoice to be preserved. \n
β Successful Response
\n{\n \"integration\": \"SdI via POP\",\n \"message\": \"Invoice sent to legal archive successfully!\",\n \"code\": 200,\n \"success\": true\n}\n\nResponse Fields
\n- \n
message: Confirms the invoice has been accepted by the legal archive.
\n \ncode: HTTP status code 200 OK.
\n \nsuccess: true indicates success.
\n \n
β Error Response β 400 Bad Request
\n{\n \"integration\": \"SdI via POP\",\n \"message\": \"Invoice not eligible for preservation\",\n \"code\": 400,\n \"success\": false\n}\n\n\n\nThe invoice does not meet the criteria for legal preservation.
\n
\n
Retrieve SdI Notifications
\nEndpoint: {{base_url}}/wp-json/api/v2/sdi-via-pop/document-notifications
Method: POST
This endpoint allows you to retrieve all the notifications (such as RC, MC, NS, etc.) received from the Italian SdI (Sistema di Interscambio) for a specific invoice.
\n\n
πΈ Request Payload
\n{\n \"license_key\": \"1ae8b944cbebcf4592ed0b6ac367587e0840dd9e\",\n \"integration\": {\n \"uuid\": \"01971277-c9d9-76c9-ad53-e640bbdffb8e\"\n }\n}\n\nPayload Parameters
\n- \n
license_key (string, required):
\n
Your POP license key. \nintegration.uuid (string, required):
\n
The UUID of the invoice whose SDI notifications you want to retrieve. \n
β Successful Response β 200 OK
\n{\n \"integration\": \"SdI via POP\",\n \"message\": \"Invoice notifications successfully!\",\n \"data\": [\n {\n \"uuid\": \"string\",\n \"invoice_uuid\": \"string\",\n \"created_at\": \"string\",\n \"type\": \"string\",\n \"message\": {\n \"identificativo_sdi\": null\n },\n \"downloaded\": true,\n \"downloaded_at\": \"2019-08-24T14:15:22Z\",\n \"file_name\": \"string\"\n }\n ],\n \"code\": 200,\n \"success\": true\n}\n\nResponse Fields
\nEach item in the data array represents a notification and contains:
- \n
uuid (string): UUID of the notification.
\n \ninvoice_uuid (string): UUID of the related invoice.
\n \ncreated_at (string): Date and time when the notification was received.
\n \ntype (string): Type of notification (e.g., RC = Receipt Confirmation, MC = Failed Delivery).
\n \nmessage.identificativo_sdi (string or null): SDI identifier.
\n \ndownloaded (boolean): Whether the notification was downloaded.
\n \ndownloaded_at (string): Timestamp of download.
\n \nfile_name (string): Name of the notification file.
\n \n
\n
Get Invoice XML
\nEndpoint: {{base_url}}/wp-json/api/v2/sdi-via-pop/documenti-get
Method: POST
This endpoint allows you to retrieve the XML file of an invoice generated via the SdI via POP integration.
\nThe draft flag is used to specify whether you want to retrieve the draft version of the invoice.
If set to true, the system will search for a draft invoice matching the provided UUID.
If set to false, it will search for a finalized invoice.
\n
πΈ Request Payload
\n{\n \"license_key\": \"1ae8b944cbebcf4592ed0b6ac367587e0840dd9e\",\n \"integration\": {\n \"uuid\": \"019736a2-dcd1-7ad3-adad-30479425112b\",\n \"draft\": true\n }\n}\n\nPayload Parameters
\n- \n
license_key (string, required):
\n
Your POP license key. \nintegration.uuid (string): The unique identifier of the invoice.
\n \nintegration.draft (boolean, optional): If
\ntrue, returns the draft version of the XML. \n
β Successful Response β 200 OK
\n<Invoice>\n ...\n</Invoice>\n\nβ Error Response
\n{\n \"success\": false,\n \"data\": {\n \"message\": \"Invoice not found\",\n \"uuid\": \"invoice-uuid\",\n \"draft\": true\n }\n}\n\nGetting Started with the Electronic Invoicing API (PEPPOL via POP)
\nTo start sending electronic invoices through the PEPPOL network using the POP system, follow these steps:
\n1. Create a POP Account
\nFirst, sign up for a POP account with at least the Growth plan.
\n2. Enable PEPPOL Integration
\nOnce your account is active, go to your User Area and open the Integrations panel to enable PEPPOL connectivity.
\n- \n
Select the PEPPOL integration.
\n \nRegister your Legal EntityEnter the following information to enable your company for electronic invoicing:
\n- \n
Address
\n \nCity
\n \nZIP Code
\n \n
\n
3. Access API Endpoints
\nOnce your company is connected and the PEPPOL integration is enabled, you are authorized to use the API endpoints for sending invoices.
\nYou can now proceed to authenticate and interact with the available endpoints described below.
\n\n
Using PEPPOL Integration
\nπ Authentication
\nAll requests require the inclusion of a valid license_key in the main payload.
\n
π¦ Payload Structure
\nTo create an invoice that will be managed and sent via PEPPOL through the POP integration, you need to include the following integration object in the payload using the{{base_url}}/wp-json/api/v2/create-ubl endpoint
{\n \"license_key\": \"your_license_key\",\n \"data\": { ... },\n \"integration\": {\n \"use\": \"peppol-via-pop\",\n \"action\": \"create\"\n }\n}\n\nThis instructs the system to:
\n- \n
- Generate the XML invoice using the PEPPOL integration. \n
β Successful Response
\nWhen the invoice is successfully created using the PEPPOL integration, the API will return a JSON response like the following:
\n{\n \"integration\": \"Peppol via POP\",\n \"message\": \"Invoice created successfully!\",\n \"data\": {\n \"uuid\": \"0197200c-b922-78e2-99b6-1b4d40969ba8\"\n },\n \"code\": 201,\n \"success\": true\n}\n\nResponse Fields
\n- \n
integration: The name of the integration used (
\n\"Peppol via POP\"). \nmessage: A human-readable message indicating the result of the operation.
\n \ndata.uuid: The unique identifier (UUID) of the created invoice.
\n
This ID must be used in subsequent requests. \ncode: HTTP status code (202 indicates successful creation).
\n \nsuccess: Boolean value confirming the operation was successful.
\n \n
POP to Webhook Integration
\nThe Webhook integration allows you to automatically send invoice data generated by POP to external tools such as Zapier, Make (Integromat), CRMs, cloud storage tools like Google Drive, and many more.
\nAvailability
\nThis feature is available starting from the Growth plan.
\nHow to Enable the Webhook Integration
\n1. Activate the integration on your POP account
\nLog in to your account at popapi.io and follow these steps:
\n- \n
Go to My Account > Integrations > POP to Webhook > Connect
\n \nEnter the following information for each webhook you want to create:
\n- \n
Webhook identifier name (e.g., βZapier β Google Driveβ)
\n \nDestination webhook URL (e.g., URL generated by Zapier or another tool)
\n \nData format to send:
\n- \n
JSON: suitable for most integrations like Zapier
\n \nXML: recommended if the receiving system requires a structured file (e.g., for storage or invoicing)
\n \n
\nActivate the webhook
\n
You can create and activate multiple webhooks at the same time, each with a different URL and format. \n
\n
\n
Real-World Use Cases
\nIntegration with Zapier
\n- \n
Create a Zap that starts from a Webhook (Catch Hook)
\n \nPaste the URL generated by Zapier into the URL field in your POP account
\n \nOnce the payload is received, you can:
\n- \n
Save the invoice to Google Drive
\n \nSend an email with the XML file attached
\n \nAdd a row to Google Sheets or update a CRM
\n \n
\n
Integration with Make
\n- \n
Use the module Webhook > Custom Webhook
\n \nCopy the generated URL and paste it into your POP account
\n \nReceive the data in JSON format and connect it to any Make scenario
\n \n
Supported Formats
\nPOP supports two data formats for webhook payloads:
\n- \n
JSON: ideal for no-code tools (Zapier, Make, Airtable, etc.)
\n- \n
- The JSON payload is automatically flattened to simplify processing in external tools, avoiding deeply nested structures. \n
\nXML: recommended for storing invoices or sending them to systems that require the FatturaPA standard
\n \n
\n
Frequently Asked Questions
\nCan I send the XML file as an attachment?
\nYes. When choosing the XML format, the plugin also sends the invoice XML file as an attachment (e.g., in Zapier you can save it to Drive or attach it to an email).
\nCan I create multiple webhooks?
\nYes. You can activate multiple webhooks with different URLs and formats for different purposes (e.g., one for storage, one for CRM, one for email notifications).
\nExample: Sending Invoice Data to a Webhook
\nIntegration configuration:
\n\"integration\": {\n \"use\": \"pop-to-webhook\",\n \"id\": \"xxxxxx\" // the ID of the webhook registered in the panel > https://popapi.io/en/my-account/api-integrations/pop-to-webhook/connect/\n}\n\n