canonical: https://jentic.com/apis/qonto.com/qonto

# Qonto API

Qonto business banking, invoicing and expense management API. The API exposes 73 endpoints secured with oauth2 authentication.

## For AI agents

Programmatically get organization, create account. Covers 73 operations with oauth2 authentication.

## Scope

Does not handle payments, communications, or crm - use for finance and accounting only.

## Capabilities

- Get organization
- Create account
- List accounts
- Update account
- Close account
- Download IBAN certificate

## Use cases

### Finance and Accounting Operations

Use the Qonto API to perform finance operations programmatically. The API provides 73 endpoints covering core functionality including get organization, create account, list accounts.

Example prompt: Call GET /organization to get organization

### Automated Accounts Management

Automate accounts operations by combining multiple Qonto API endpoints. Agents can create account and then list accounts in a single workflow.

Example prompt: Call POST /accounts to create account, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call Qonto API endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle oauth2 tokens manually.

Example prompt: Search Jentic for 'get organization', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/organization` | Get organization |
| POST | `/accounts` | Create account |
| GET | `/accounts` | List accounts |
| GET | `/accounts/{id}` | Get account |
| PUT | `/accounts/{id}` | Update account |
| POST | `/accounts/{id}/close` | Close account |
| GET | `/accounts/{id}/iban-certificate` | Download IBAN certificate |
| GET | `/memberships` | List memberships |

## Key resources

- **Accounts** — Operations for accounts
- **Beneficiaries** — Operations for beneficiaries
- **Bulk Transfers** — Operations for bulk transfers
- **Cards** — Operations for cards
- **Client Invoices** — Operations for client invoices

## Why Jentic

- **Setup:** Wiring Qonto by hand means running its OAuth2 authorization-code flow, refreshing tokens, and targeting the thirdparty.qonto.com/v2 host on every call. Through Jentic you install once, import the Qonto API from the API Directory, store the credential once, and your agent calls it.
- **Permission scoping:** Qonto puts the account id in the URL path (`/accounts/{id}`), so a rule can pin your agent to one bank account: it can read that account and its IBAN certificate and nothing else. You choose the operations it may call, so ones like updating or closing an account are not included unless you add them.
- **Credential handling:** Your Qonto OAuth credentials are stored once, encrypted, by your own Jentic One instance and injected at execution time. They never enter the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'get organization details' or 'list bank accounts', and Jentic returns the matching Qonto operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Plaid** — Alternative finance API
- **Xero** — Alternative finance API

## FAQ

### What authentication does the Qonto API use?

The Qonto API uses OAuth 2.0 for authorization. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context.

### Can I get organization with the Qonto API?

Yes. Use the GET /organization endpoint. The API returns structured JSON responses that agents can parse and act on directly.

### What are the rate limits for the Qonto API?

Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.

### How do I get organization through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'get organization'. Jentic returns the matching Qonto API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the Qonto API have?

The Qonto API exposes 73 endpoints covering accounts, beneficiaries, bulk transfers operations.

### Can I limit what my agent is allowed to do with the Qonto API?

Yes. Because Jentic One is self-hosted, you set the rules that decide which Qonto operations and credentials your agent may use. Since Qonto puts the account id in the URL path (`/accounts/{id}`), you can pin the agent to a single bank account so it only reads that account and downloads its IBAN certificate. You also choose which operations are exposed, so write actions like updating or closing an account (PUT `/accounts/{id}`, POST `/accounts/{id}/close`) stay off limits unless you add them.