Send a client invoice via e-invoice

OAuth scope: client_invoice.write

Sends the client invoice identified by the id path parameter via e-invoice.

French specificity: For French organizations and partners, e-invoice refers to using Qonto’s Plateforme Agréée (also referred to as “PA”)

Eligibility (prerequisites)

1. The client on the invoice must be reachable on the e-invoicing network: e_invoicing_reachable on the client (from Retrieve a client or List clients) must be true. If it is false, do not call this endpoint, use Send a client invoice via email instead.
2. The client invoice must also not already have been submitted for e-invoice. If a send was already requested, calling this endpoint again completes successfully and does not resubmit the invoice.

Processing (asynchronous)

Relative to the e-invoicing network, delivery is asynchronous. A 204 means the request was accepted for processing, not that the invoice was fully delivered or issued on the network. The client invoice status does not change when you call this endpoint.

Tracking and observability

Track downstream steps on the invoice via einvoicing_lifecycle_events. The status_code values follow the platform’s lifecycle; a typical sequence is:

1. 200 — Submitted (deposited for e-invoicing)
2. 201 — Issued by the platform (released into the network)
3. 202 — Received from the platform (the receiving platform acknowledges receipt from the sender), when applicable

There is no separate lifecycle-only endpoint. Use Retrieve a client invoice (GET /v2/client_invoices/{id}): the client_invoice object includes einvoicing_lifecycle_events (each event has a lifecycle status_code—for example 201 for Issued by the platform when that milestone is recorded) and einvoicing_status. Client invoice webhooks support updated (and created) events; treat them as a signal to fetch the invoice again if you need the latest lifecycle list. The documented webhook payload includes einvoicing_status but not the full einvoicing_lifecycle_events array.

E-invoicing API flows

Flow 1 — Invoices created in Qonto

1. Create a client invoice in Qonto
2. Send it via e-invoice using the endpoint POST /v2/client_invoices/{id}/send_by_einvoice
3. Use the Qonto invoice id to track its lifecycle (einvoicing_lifecycle_events) and Mark is as paid, Unmark it as paid, etc.

Flow 2 — Invoices created in a third-party invoicing tool

This flow lets you send an invoice initially generated with a third-party invoicing tool via e-invoice, by first importing and creating it into Qonto:

1. Generate the invoice in the Factur-X format, including the correct .xml file
2. Create an invoice upload in Qonto
3. Qonto automatically creates a client invoice and assigns a Qonto invoice id
4. Send the invoice via e-invoice using the endpoint POST /v2/client_invoices/{id}/send_by_einvoice
5. Use the Qonto invoice id to track its lifecycle (einvoicing_lifecycle_events) and Mark is as paid, Unmark it as paid, etc.

Environment limitations

The e-invoicing flow is only available in the production environment. Sandbox does not support e-invoicing, as the underlying e-invoicing network operates exclusively in production - this is a platform-level constraint.

Errors

412 Precondition Failed is returned when the invoice cannot be sent via e-invoice—for example, invalid data, the recipient not being reachable on the e-invoicing network, or another unmet precondition.

POST /v2/client_invoices/{id}/send_by_einvoice

Send a client invoice via e-invoice

cURL

curl --request POST \
  --url https://thirdparty.qonto.com/v2/client_invoices/{id}/send_by_einvoice \
  --header 'Authorization: Bearer <token>'

204

Authorizations

OAuthSecretKey

Authorization · string · header · required

Bearer authorization header: Bearer <token>, where <token> is the access token received from the authorization server at the end of the OAuth 2.0 flow.

Headers

X-Qonto-Staging-Token · string

Required only for Sandbox API requests; to get one, please sign up to the Developer Portal.

Path Parameters

id · string<uuid> · required

The ID of the client invoice to send

Response

204

Request accepted for processing; e-invoice flow continues asynchronously