Skip to main content

Submit invoice (partner)

POST 
/v1/partner/invoices

Partner-facing invoice submission endpoint. Auth: X-API-Key header. Workflow is always full_enrichment. Attachments must be inline base64. Routing resolves in this order: (1) receiving_inbox direct match, (2) external_identifier lookup, (3) customer default inbox. If neither routing field matches but a default is configured, the request still succeeds and returns a Warning header. Supports Idempotency-Key for safe retries.

Request​

Responses​

Invoice accepted

Response Headers
    Warning

    Present only when an unknown receiving_inbox / external_identifier was silently replaced with the customer default.