# Qonto

> **Provider code:** `qonto` **Service:** Invoicing

Business banking with integrated invoicing and e-invoicing support. Docs-Dispatcher integrates with the **Qonto Business API** and supports both production and sandbox environments.

## Services supported

* ✅ **Invoicing**

## Document types

* `INVOICE`
* `E_INVOICE`
* `QUOTE`
* `CREDIT`

## Configuration

The JSON schema for this configuration is served at:

```
GET /api/configurations/INVOICING/providers/qonto/config
```

| Field                | Type    |            Required           | Description                                                             |
| -------------------- | ------- | :---------------------------: | ----------------------------------------------------------------------- |
| `qontoLogin`         | String  |               ✅               | Organisation login for Qonto API authentication                         |
| `qontoSecretKey`     | String  |               ✅               | Secret key for Qonto API authentication                                 |
| `defaultIban`        | String  |               —               | Default IBAN (must be a Qonto account) used to receive invoice payments |
| `useSandbox`         | Boolean |      — (default `false`)      | Route calls to the Qonto sandbox environment                            |
| `sandboxHeaderValue` | String  | required if `useSandbox=true` | Staging token for the Qonto sandbox API                                 |

{% hint style="info" %}
**Sandbox**: set `useSandbox=true` and provide `sandboxHeaderValue` to exercise the integration without producing real invoices on the Qonto side.
{% endhint %}

## Usage example

```bash
curl -X POST https://api.docs-dispatcher.io/api/invoicing \
  -u "$EMAIL:$PASSWORD" \
  -H "Content-Type: application/json" \
  -d '{
    "providerName": "qonto",
    "documentType": "INVOICE",
    "template": { "id": 123, "data": { } }
  }'
```

Replace `-u "$EMAIL:$PASSWORD"` with `-H "Authorization: Bearer $JWT"` for the JWT flow — see [Authentication](/docs-dispatcher/authentication/basic-auth.md).

## Common errors

| Status | `error`                          | Cause                                              |
| ------ | -------------------------------- | -------------------------------------------------- |
| 401    | `provider_authentication_failed` | `qontoLogin` / `qontoSecretKey` rejected by Qonto  |
| 417    | `expectation_failed`             | `useSandbox=true` but `sandboxHeaderValue` missing |

## Where to go next

* [**Generate & send an invoice**](/docs-dispatcher/how-to-recipes/invoice.md)
* [**All providers**](/docs-dispatcher/providers/providers.md)


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.docs-dispatcher.io/docs-dispatcher/invoicing/qonto.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.