Skip to main content

​
At a glance

  • Availability: Experimental (how to enable).
  • Authentication: API key.
  • Connection: The key from QONTO_API_KEY is sent as the Authorization header.
  • Provider documentation: Authentication reference.

​
Credentials

Set these per environment. See Connect an integration.

​
Setup

  1. 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.
  2. 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.
  3. 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.
  4. Verify access: Run Get Organization. A successful response confirms the credential; a 401 means the Authorization value is malformed.

​
Provider notes

  • 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.
Provider API reference.

​
Tools

​
Verify the connection

Call a read tool such as qonto__get_organization with arguments for your account. Confirm that the result comes from the intended account or workspace before enabling write tools.