Send Invoice
POST /invoices/{id}/send
Submit an invoice for sending via the Peppol network. The invoice is validated and queued for delivery. Requires the invoice:send scope on your API key.
Authorizations
Section titled “Authorizations ”Parameters
Section titled “ Parameters ”Path Parameters
Section titled “Path Parameters ”The UUID of the invoice to send.
Responses
Section titled “ Responses ”Invoice accepted and queued for sending.
object
object
Unique invoice identifier (UUID).
UUID of the company that owns this invoice.
UUID of the user who created the invoice, if applicable.
Current workflow state: draft, approved, sending, sent, delivered, failed, or cancelled.
Invoice direction: outgoing (sent by company) or incoming (received).
Invoice total amount in cents.
ISO 4217 currency code (e.g. EUR, USD).
UBL specification version used (2.1, 2.2, or 2.3).
Full invoice data in structured UBL JSON format (header, seller, buyer, items, totals, etc.).
Delivery network used: peppol, ksef, or email.
UUID of the business entity (seller identity) used for this invoice.
UUID of the address book contact this invoice was issued to, if any.
UUID of the branding profile used for the PDF; null means the company default profile.
Public invoice metadata, e.g. the delivery method. Always a JSON object.
object
Delivery method selected when sending: auto, peppol, email, etc.
Final Peppol access-point response for the send attempt.
Timestamp the Message Level Response was forwarded, if any.
Outbound Message Level Response verdict from the recipient’s access point:
- verdict: received_ap (delivered) | received_ab (delivered with note) | received_re (rejected)
- received_at: ISO 8601 timestamp the MLR was processed by the AP
- error_details: rejection reason if verdict is received_re Null until the recipient AP returns an MLR or 72h elapses.
object
object
ISO 8601 timestamp when the invoice was created.
ISO 8601 timestamp when the invoice was last updated.
ISO 8601 timestamp when the invoice was soft-deleted, or null.
ISO 8601 timestamp when the public (signed-URL) link was revoked, or null if active.
object
API key lacks the required invoice:send scope.
Invoice not found or does not belong to your company.
object
Invoice is not in a sendable state or API key not associated with a company.
object
Server error during send.