> ## Documentation Index
> Fetch the complete documentation index at: https://docs.qonto.com/llms.txt
> Use this file to discover all available pages before exploring further.
# Send a client invoice via e-invoice
> OAuth scope: `client_invoices.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](/api-reference/business-api/clients/retrieve-a-client) or [List clients](/api-reference/business-api/clients/list-clients)) must be **`true`**. If it is **`false`**, do not call this endpoint, use [Send a client invoice via email](/api-reference/business-api/expense-management/client-quotes-notes/client-invoices/send-a-client-invoice) 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**
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](/api-reference/business-api/expense-management/client-quotes-notes/client-invoices/mark-a-client-invoice-as-paid), [Unmark it as paid](/api-reference/business-api/expense-management/client-quotes-notes/client-invoices/unmark-a-client-invoice-as-paid), etc.
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](/api-reference/business-api/expense-management/client-quotes-notes/introduction-factur-x), including the correct **`.xml`** file
2. Create an [invoice upload](/api-reference/business-api/expense-management/client-quotes-notes/client-invoices/create-a-client-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](/api-reference/business-api/expense-management/client-quotes-notes/client-invoices/mark-a-client-invoice-as-paid), [Unmark it as paid](/api-reference/business-api/expense-management/client-quotes-notes/client-invoices/unmark-a-client-invoice-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.
## OpenAPI
````yaml post /v2/client_invoices/{id}/send_by_einvoice
openapi: 3.1.1
info:
version: v2
title: Qonto
servers:
- url: https://thirdparty.qonto.com
description: Production URL
- url: https://thirdparty-sandbox.staging.qonto.co
description: Sandbox URL
security:
- OAuth:
- organization.read
- membership.read
- membership.write
- attachment.write
- internal_transfer.write
- payment.write
- supplier_invoice.write
- supplier_invoice.read
- client_invoices.read
- client_invoice.write
- client.read
- client.write
- product.read
- product.write
- request_review.write
- request_review.read
- team.read
- team.write
- request_transfers.write
- insurance_contract.read
- insurance_contract.write
- card.read
- card.write
- bank_account.write
- beneficiary.trust
- webhook
- payment_link.write
- payment_link.read
- sepa_direct_debit.read
- sepa_direct_debit.write
- terminal.read
- terminal.write
- SecretKey: []
paths:
/v2/client_invoices/{id}/send_by_einvoice:
post:
tags:
- Client Invoices
summary: Send a client invoice via e-invoice
description: >-
OAuth scope: `client_invoices.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](/api-reference/business-api/clients/retrieve-a-client) or [List
clients](/api-reference/business-api/clients/list-clients)) must be
**`true`**. If it is **`false`**, do not call this endpoint, use [Send a
client invoice via
email](/api-reference/business-api/expense-management/client-quotes-notes/client-invoices/send-a-client-invoice)
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**
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](/api-reference/business-api/expense-management/client-quotes-notes/client-invoices/mark-a-client-invoice-as-paid), [Unmark it as paid](/api-reference/business-api/expense-management/client-quotes-notes/client-invoices/unmark-a-client-invoice-as-paid), etc.
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](/api-reference/business-api/expense-management/client-quotes-notes/introduction-factur-x), including the correct **`.xml`** file
2. Create an [invoice upload](/api-reference/business-api/expense-management/client-quotes-notes/client-invoices/create-a-client-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](/api-reference/business-api/expense-management/client-quotes-notes/client-invoices/mark-a-client-invoice-as-paid), [Unmark it as paid](/api-reference/business-api/expense-management/client-quotes-notes/client-invoices/unmark-a-client-invoice-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.
operationId: send_client_invoice_by_e_invoice
parameters:
- $ref: '#/components/parameters/X-Qonto-Staging-Token'
- name: id
in: path
description: The ID of the client invoice to send
required: true
schema:
type: string
format: uuid
responses:
'204':
description: >-
Request accepted for processing; e-invoice flow continues
asynchronously
'400':
$ref: '#/components/responses/400-Bad-request'
'401':
$ref: '#/components/responses/401-Unauthorized'
'403':
$ref: '#/components/responses/403-Forbidden'
'404':
$ref: '#/components/responses/404-Not-Found'
'412':
$ref: '#/components/responses/412-Client-Invoice-Precondition-Failed'
'422':
$ref: '#/components/responses/422-Unprocessable-Entity'
'500':
$ref: '#/components/responses/500-Internal-Server-Error'
security:
- OAuth:
- client_invoices.write
- SecretKey: []
components:
parameters:
X-Qonto-Staging-Token:
name: X-Qonto-Staging-Token
in: header
description: >-
Required only for Sandbox API requests; to get one, please sign up to
the [Developer Portal](https://developers.qonto.com/).
schema:
type: string
responses:
400-Bad-request:
description: Returns a bad request error.
content:
application/json:
schema:
$ref: '#/components/schemas/BadRequestResponseBody'
examples:
Authorization field missing:
value:
errors:
- code: bad_request
detail: Authorization field missing
401-Unauthorized:
description: Returns an unauthorized error.
content:
application/json:
schema:
$ref: '#/components/schemas/UnauthorizedResponseBody'
examples:
authorization_header_missing:
value:
errors:
- code: authorization_header_missing
detail: authorization header missing
authorization_token_invalid:
value:
errors:
- code: authorization_token_invalid
detail: authorization token invalid
403-Forbidden:
description: Returns a forbidden error.
content:
application/json:
schema:
$ref: '#/components/schemas/ForbiddenResponseBody'
examples:
Insufficient permissions:
value:
errors:
- code: forbidden
detail: User does not have sufficient permissions for this action.
404-Not-Found:
description: Returns a not found error.
content:
application/json:
schema:
type: object
properties:
errors:
type: array
items:
$ref: '#/components/schemas/NotFoundError'
412-Client-Invoice-Precondition-Failed:
description: Returns a precondition failed error specific to client invoices.
content:
application/json:
schema:
type: object
properties:
errors:
type: array
items:
type: object
properties:
status:
type: string
example: '412'
code:
type: string
enum:
- forbidden_invoice_update
- forbidden_invoice_deletion
- invoice_not_in_draft_status
- recipient_not_reachable_on_einvoicing
example: forbidden_invoice_update
examples:
forbidden_invoice_update:
value:
errors:
- status: '412'
code: forbidden_invoice_update
forbidden_invoice_deletion:
value:
errors:
- status: '412'
code: forbidden_invoice_deletion
invoice_not_in_draft_status:
value:
errors:
- status: '412'
code: invoice_not_in_draft_status
recipient_not_reachable_on_einvoicing:
value:
errors:
- status: '412'
code: recipient_not_reachable_on_einvoicing
422-Unprocessable-Entity:
description: Returns an unprocessable entity error.
content:
application/json:
schema:
type: object
properties:
errors:
type: array
items:
$ref: '#/components/schemas/UnprocessableEntityError'
x-examples:
Example 1:
errors:
- code: missing_key
detail: reference is missing
source:
pointer: /external_transfer/reference
500-Internal-Server-Error:
description: Returns an internal server error.
schemas:
BadRequestResponseBody:
type: object
properties:
errors:
type: array
items:
$ref: '#/components/schemas/BadRequestError'
required:
- errors
UnauthorizedResponseBody:
type: object
properties:
errors:
type: array
items:
$ref: '#/components/schemas/UnauthorizedError'
required:
- errors
ForbiddenResponseBody:
type: object
properties:
errors:
type: array
items:
$ref: '#/components/schemas/ForbiddenError'
required:
- errors
NotFoundError:
type: object
properties:
code:
type: string
description: Error code.
detail:
type: string
description: Human readable error that explains error `code`.
source:
type: object
properties:
parameter:
type: string
description: The parameter that causes the error.
required:
- code
- detail
x-examples:
Object not found:
code: not_found
detail: Object not found
source:
parameter: id
UnprocessableEntityError:
type: object
properties:
status:
type: string
example: unprocessable entity
code:
type: string
description: Error code.
example: missing_key
detail:
type: string
description: Human readable error that explains error `code`.
example: property is missing
message:
type: string
example: property id is missing
source:
type: object
properties:
pointer:
type: string
description: >-
The property and the item in an array (if applicable) that
causes the error.
example: id
required:
- code
- detail
x-examples:
Missing property:
code: missing_key
detail: property is missing
source:
pointer: /external_transfer/atrribute
BadRequestError:
type: object
properties:
code:
type: string
description: Error code.
detail:
type: string
description: Human readable error that explains error `code`.
source:
type: object
properties:
pointer:
type: string
description: >-
The property in the request body that caused the error
(optional).
parameter:
type: string
description: The query parameter that caused the error (optional).
required:
- code
- detail
x-examples:
Authorization field missing:
code: bad_request
detail: Authorization field missing
UnauthorizedError:
type: object
properties:
code:
type: string
description: Error code.
detail:
type: string
description: Human readable error that explains error `code`.
required:
- code
- detail
x-examples:
Invalid credentials:
code: unauthorized
detail: Invalid credentials
ForbiddenError:
type: object
properties:
code:
type: string
description: Error code.
detail:
type: string
description: Human readable error that explains error `code`.
required:
- code
- detail
x-examples:
Insufficient permissions:
code: forbidden
detail: User does not have sufficient permissions for this action.
securitySchemes:
OAuth:
type: oauth2
description: >
Bearer authorization header: `Bearer `, where `` is the
access token received from the authorization server at the end of the
[OAuth 2.0
flow](/get-started/business-api/authentication/oauth/oauth-flow).
flows:
authorizationCode:
refreshUrl: https://oauth.qonto.com/oauth2/token
authorizationUrl: https://oauth.qonto.com/oauth2/auth
scopes:
attachment.read: Retrieve attachments
attachment.write: Upload attachments and remove attachments from transactions
bank_account.write: Create, update and close bank accounts
beneficiary.trust: Trust SEPA beneficiaries
card.read: Retrieve cards
card.write: Create or update cards
client.read: Retrieve clients
client.write: Create clients
client_invoice.write: Create client invoices
client_invoices.read: Retrieve client invoices and credit notes
einvoicing.read: Retrieve e-invoicing settings
embed_auth_link.write: Create Embed auth links
insurance_contract.read: Retrieve insurance contracts
insurance_contract.write: Create and update insurance contracts
internal_transfer.write: >-
Create internal transfers (between 2 Qonto accounts of the same
organization)
international_transfer.write: Create international transfers
membership.read: Retrieve the authentified membership
membership.write: Invite team members
offline_access: Retrieve a refresh token
organization.read: >-
Retrieve organization, bank accounts, transactions, transfers,
beneficiaries, labels, memberships, requests & statements
payment.write: Create external transfers and untrust beneficiaries
payment_link.read: >-
Retrieve payment links, their payments, and the available payment
methods
payment_link.write: >-
Connect to the payment links provider, create and deactivate
payment links
product.read: Retrieve products
product.write: Create products
request_cards.write: Create card requests
request_review.write: Approve or decline requests
request_transfers.write: Create transfer requests
sepa_direct_debit.read: View SEPA Direct Debit payments
sepa_direct_debit.write: Manage SEPA Direct Debit payments
supplier_invoice.read: Retrieve supplier invoices
supplier_invoice.write: Create supplier invoices
team.read: Retrieve teams
team.write: Create teams
terminal.read: View your payment terminals
terminal.write: Configure your terminals and initiate payments
webhook: >-
Receive a notification each time a particular event occurs in
Qonto
tokenUrl: https://oauth.qonto.com/oauth2/token
SecretKey:
type: apiKey
description: cf. [API key](/get-started/business-api/authentication/api-key)
name: Authorization
in: header
````