At a glance
- Availability: Experimental (how to enable).
- Auth: API key.
- Connection: The key from
QONTO_API_KEYis sent as theAuthorizationheader. - Docs: https://docs.qonto.com/get-started/business-api/authentication/api-key
Credentials
Set these per environment. See Connect an integration.| Variable | Required | Description |
|---|---|---|
QONTO_API_KEY | Yes | Qonto API credential in the form organization-slug:secret-key - your organization slug (login) and API secret key joined by a colon. Sent as the raw Authorization header value (no Bearer prefix, no Base64 encoding). Docs. |
Setup
- Open your Qonto organization: Log in to the Qonto web app at https://app.qonto.com. For testing without a live account, create a sandbox organization through the Qonto Developer Portal toolkit at https://developers.qonto.com.
- Generate an API key: In the web app, go to Integrations and Partnerships > API key and click Generate. Note both your organization slug (the login, e.g. my-company-1234) and the generated secret key.
- Set the environment variable: Set QONTO_API_KEY to the organization slug and secret key joined by a colon, e.g. my-company-1234:62885d39f3a0ddedd3d3ee0432a43ccr. The value is sent as-is in the Authorization header - no Bearer prefix and no Base64 encoding.
- Verify access: Run Get Organization. A successful response confirms the credential; a 401 means the Authorization value is malformed.
- The Authorization header is the raw ‘organization-slug:secret-key’ string - unlike most APIs there is no Bearer prefix and no encoding.
- This connector targets the production API (thirdparty.qonto.com/v2). The sandbox uses a different host (thirdparty-sandbox.staging.qonto.co) and additionally requires an X-Qonto-Staging-Token header.
- Uploading an attachment to a transaction (POST /v2/transactions/{id}/attachments) requires a multipart/form-data file part, which this connector’s JSON endpoint executor does not support yet - only listing attachments is included.
Tools
| Tool | Access | Description |
|---|---|---|
| Get Organization | Read | Retrieve the authenticated organization with its bank accounts, including IBAN, BIC, currency, status, and current/authorized balances |
| List Transactions | Read | List transactions for one bank account (identified by bank_account_id or IBAN) with status, side, and date filtering |
| Get Transaction | Read | Retrieve a single transaction by its UUID, optionally embedding VAT details, labels, or attachments |
| List Transaction Attachments | Read | List the attachments (receipts, invoices) of a transaction with download URLs |
| Upload Transaction Attachment | Write | Upload a receipt or invoice (JPEG, PNG, or PDF) onto a transaction to justify it for bookkeeping; the file is processed in the background, so the attachment is not visible immediately |
| Get Attachment | Read | Retrieve an attachment by id to get a fresh download URL - URLs returned by the attachment endpoints expire after 30 minutes, so re-fetch before any delayed download |
| List Supplier Invoices | Read | List the organization’s supplier invoices (accounts payable inbox) with status and payment matching; available on all price plans except Solo Basic |
Example prompts
- Show my Qonto bank accounts with their current and authorized balances.
- List the most recent completed transactions on my main Qonto account and summarize debits vs credits.
- Find recent Qonto transactions that have no attachment so I can chase missing receipts.