Create Invoice
POST /invoices
Create a new invoice from structured JSON data. Requires the invoice:create scope. The invoice is created in draft state. Set calculate_totals to true to have the server compute line and tax totals automatically.
Authorizations
Section titled “Authorizations ”Request Body
Section titled “Request Body ”object
object
object
object
object
object
object
object
object
object
object
object
object
object
object
object
object
object
object
object
Multiple payments
object
object
object
object
Legacy single payment (backwards compatible)
object
object
object
object
object
object
object
object
Sum of line totals (in cents)
Before tax
After tax
object
Price in cents
object
Item identifiers
object
object
Item classification
object
Item attributes
object
Line allowances
object
Line charges
object
object
object
object
object
Base64 encoded
object
Name of the invoice number series to use for auto-numbering. Only used when header.invoice_number is not provided — the server will generate a number from this series when the invoice is sent. Defaults to the company’s default series.
Example
billingResponses
Section titled “ Responses ”Invoice created successfully.
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. Peppol BIS 3.0 binds to UBL 2.1.
Full invoice data in structured UBL JSON format (header, seller, buyer, items, totals, etc.).
Additional metadata such as delivery details, error info, or processing history.
Delivery network used: peppol, ksef, or email.
UUID of the business entity (seller identity) used for this invoice.
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.
Validation error or API key not associated with a company.
object
Server error during invoice creation.