Upload an invoice
Submit a primary invoice document and optional attachments as multipart/form-data.
Files (primary and attachments) must be PDF, Peppol BIS Billing 3.0 (UBL 2.1 — root Invoice or CreditNote), or Finvoice 3.0 (root Finvoice). XML is matched on the root element name only; documents are not schema-validated. If any file fails validation, no invoice is created.
Deduplicated by primary-document MD5 within the organization. A replay returns 409 duplicate_invoice, or primary_md5_locked_by_deleted_invoice if the original was soft-deleted (an admin must hard-delete to free the MD5).
New invoices also require current processing capacity. A 403 invoice_processing_capacity_exhausted means no invoice or documents were retained; retry only after organization capacity may have changed. A temporary admission-coordination failure returns 503 service_unavailable with Retry-After: 1.
The 201 includes a Location header at /v1/invoices/{invoice_id}. Poll that resource with an invoices:read token and respect its Retry-After header while either processing status is pending or processing.
Authorizations
API key from Settings → API Keys. Plaintext is shown once at creation and cannot be recovered. Header: Authorization: Bearer wdg_<token>.