Skip to content

Connect Qonto to a tool built with Claude or ChatGPT (2026)

Your tool built with Claude needs to read Qonto’s transactions to track cash flow, or prepare quotes and invoices there. The Qonto secret opens the company’s accounts, and it must end up neither in the code nor in the conversation. On while, it stays in while, and your AI never sees it. Here is how.

By Aloïs Oddon, co-founder of Nextmap. Facts checked on November 18, 2026.

View as Markdown

Connect the Qonto API to a tool built with Claude or ChatGPT: the Qonto secret kept in while, out of the code and out of the AI’s reach, and the tool reading the bank’s accounts, transactions and statements

Qonto holds the company’s accounts, incoming payments, the team’s cards, the statements. A tool built with Claude or ChatGPT becomes valuable when it reads that data. It shows the week’s cash flow, the client payments that came in, spending by label. To do that, it needs the Qonto API secret, and that secret opens the accounts of the whole company.

That is where things often go wrong: the secret ends up pasted into the code, or into the conversation with the AI, where it can leak. On while, the Qonto secret stays in while. The tool calls Qonto without ever holding it, and your AI never sees it.

The short version. Get your organization’s login and secret key in Qonto. Ask your AI to connect Qonto, then paste the secret into while through the link it gives you. The tool reads your accounts, every call is logged, and a write waits for the rule you approve.

What the Qonto API key allows

Qonto offers two ways to connect to its API. For a small business’s internal tool, the organization’s API key is enough1,2.

Organization API keyOAuth 2.0
Who it is forA Qonto customer, for its own toolsQonto’s partner software
What it allowsPart of the APIThe whole API, depending on granted scopes
Accounts, transactions and statementsYesYes
Clients, quotes and invoicesYesYes
Transfers between your accountsYesYes
SEPA transfers to a beneficiaryNoYes

With the API key, a tool reads the organization and its accounts, the transactions, the statements and the attachments. It also manages clients, quotes and invoices, both client and supplier, and transfers between the organization’s accounts2. A SEPA transfer to a beneficiary requires OAuth 2.0: no payment to a third party goes out this way.

Connect Qonto to your tool, in three steps

The whole thing takes a few minutes, and you have no code to write.

  1. Get the secret in Qonto. On the web, choose the organization if you have several, then open Integrations and Partnerships and the API key section. Qonto shows the organization’s login and its secret key there. If the key does not exist yet, generate it1.
  2. Ask your AI to connect Qonto. It declares the connection in while, in the form Qonto expects, and gives you a link.
  3. Paste the secret into while. You open the link, paste what it asks for and confirm. Neither your AI nor the tool’s code sees the secret.

Qonto expects the login and the secret key together, separated by a colon, in the Authorization header1. Your AI knows this when it declares the connection, and while adds it to each call.

You, to your AI: Connect Qonto to this tool and show the week’s cash flow: the balance of each account, the payments received and the largest expenses.

The tool built with AI calls the Qonto API through while: the Qonto secret is added to each call inside while, out of the code, every read of the accounts and transactions is logged in the history
The tool calls Qonto through while, which adds the secret to each call.

What while does on each call

The tool calls Qonto through while, without a secret. while adds the login and the secret to each call, and logs it in the history. For the first seven days, reads go through and teach while what the tool calls. A write, like creating a quote or sending an invoice, goes through once you approve its rule. After that, an unexpected call is refused, and your AI is told.

For a bank, caution makes sense. You can ask for your approval before a sensitive call.

You, to your AI: Ask me before every invoice sent and every transfer between our accounts.

The credentials of your software are detailed on our security page, and the same mechanism works for any API in connect an API with no credentials in the code.

Changing the secret

If the secret leaks, generate a new one in Qonto. Paste it into while: the tool uses it from the next call, without being put back in place, and your AI has nothing to redo.

What while adds around it

  • Your colleagues use the tool with a while account for up to 3 people, or, on the Pro plan, with their email account, Google or Microsoft. See keep a tool for your colleagues.
  • Your accountant can use it with an access link and a password, valid for 1, 7 or 30 days.
  • Connected software: one on the Libre plan, and 25 on the Pro plan, Qonto included.
  • The tool’s data is backed up every day, and your tools are hosted in France by Nextmap.

For accounting, see connect Pennylane, and for tool ideas, expense reports and the quote tracker.

Try it with your tool

Give this message to your AI, then ask it to connect Qonto. The trial is free, with no sign-up, and your tool has its address in 3 minutes.

The message to give your AI
Read while.sh/agents and help me get started with while.

In the docs: Variables and secrets.

Sources

  1. Qonto, API key, accessed November 18, 2026
  2. Qonto, Scopes and endpoints access, accessed November 18, 2026

Questions

How do you get access to the Qonto API?

In Qonto, on the web, choose the organization, then open Integrations and Partnerships and the API key section. Qonto shows the organization’s login and its secret key there, to generate if it does not exist yet1.

What does the Qonto API key allow?

Part of the API: reading the organization, accounts, transactions and statements, and managing clients, quotes, client and supplier invoices and attachments. For the rest, Qonto requires OAuth 2.01,2.

Can you make a transfer with the Qonto API key?

Only between your organization’s own accounts. A SEPA transfer to a beneficiary is not among the endpoints the API key allows, and goes through OAuth 2.02.

Does my AI see the Qonto secret?

No. Your AI declares the connection to Qonto and gives you a link. You paste the secret into while there, and neither your AI nor the tool’s code sees it.

How does Qonto expect the credentials in the request?

In the Authorization header, the login and the secret key separated by a colon, with no encoding1. while adds it to each of the tool’s calls.

Give your AI the message, and it takes care of the rest

Give this to your AI

Read while.sh/agents and help me get started with while.

Copy the message

In 3 minutes, with no sign-up, the tool has its own address. To keep it, create your account.

For a company project, write to the while team: hello@while.sh