Qonto
Qonto is a European business banking / neobank platform for freelancers and SMEs, founded in Paris in 2016 and operating on an EU-passported payment institution licence. Its Business API and Onboarding API give programmatic access to business accounts, EUR transactions, SEPA and international transfers, cards, client and supplier invoices, SEPA Direct Debit, payment links, terminals, webhooks, and partner-led company onboarding, authenticated by a login+secret-key API key or OAuth 2.0.
Reference-quality API operations across every facet — a rich contract, published governance, transparent operations, and machine-readable commercial terms.
API Evangelist profiles Qonto the way a machine reads it — 51 machine-readable artifacts across 1 API, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — Qonto scores 71.7/100 (exemplar), with a separate agent-readiness read of 45/100 (agent native). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance. Every facet and dimension name is a link: it opens that measurement's page on APIs.io, where the rating runs across the whole catalog — the exact checks that feed it, how every profiled provider distributes on it, and who is at the top of it.
Kin Score
How this is scored →scored 2026-09-08 · rubric v0.20.0
Put this on your own site. The badge is drawn live from Qonto's current Kin Score — paste it once and it updates itself every time the score is recomputed. It follows your visitor's light or dark setting, and it links back here so anyone who sees it can read the full breakdown.
<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/qonto/"
title="Qonto on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/qonto.svg"
alt="Qonto Kin Score — API readiness rating by API Evangelist" width="150" height="150" loading="lazy">
</a>[](https://providers.apievangelist.com/providers/qonto/)<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/qonto/"
title="Qonto on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/qonto/card.svg"
alt="Qonto Kin Score — API readiness rating by API Evangelist" width="340" height="120" loading="lazy">
</a>More shapes, themes and sizes → · Score as JSON · How badges work
How we profile Qonto
Each block below is one kind of artifact we hold for Qonto. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 13
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
Qonto Cards API
The Cards API from Qonto — 1 operation(s) for cards.
Qonto Client Invoices API
The Client Invoices API from Qonto — 1 operation(s) for client invoices.
Qonto Internal Transfers API
The Internal Transfers API from Qonto — 1 operation(s) for internal transfers.
Qonto International Transfers API
The International Transfers API from Qonto — 2 operation(s) for international transfers.
Qonto OAuth API
The OAuth API from Qonto — 1 operation(s) for oauth.
Qonto Organizations & Accounts API
The Organizations & Accounts API from Qonto — 4 operation(s) for organizations & accounts.
Qonto Payment Links API
The Payment Links API from Qonto — 1 operation(s) for payment links.
Qonto SEPA Direct Debit API
The SEPA Direct Debit API from Qonto — 2 operation(s) for sepa direct debit.
Qonto SEPA Transfers API
The SEPA Transfers API from Qonto — 3 operation(s) for sepa transfers.
Qonto Supplier Invoices API
The Supplier Invoices API from Qonto — 2 operation(s) for supplier invoices.
Qonto Terminals API
The Terminals API from Qonto — 2 operation(s) for terminals.
Qonto Transactions & Statements API
The Transactions & Statements API from Qonto — 3 operation(s) for transactions & statements.
Qonto Webhooks API
The Webhooks API from Qonto — 2 operation(s) for webhooks.
Scroll within the panel for all 13 ·
Postman Collections 13
A runnable collection turns the contract into something a developer can execute in seconds. We profile them because the fastest way to trust an API is to make a real call against it.
Ready-to-run Postman collections for exercising this provider's APIs.
Qonto Business Cards API
POSTMANScroll within the panel for all 13 ·
Open Collections 14
Open, tool-agnostic collections carry the same runnable value as Postman without locking you to one client — the portable, forkable form of the same exercise.
Open, tool-agnostic API collections (OpenAPI-derived and Bruno).
API Collection
OPEN COLLECTIONQonto Business Cards API
OPEN COLLECTIONQonto Business Cards Client Invoices API
OPEN COLLECTIONQonto Business Cards Internal Transfers API
OPEN COLLECTIONQonto Business Cards International Transfers API
OPEN COLLECTIONQonto Business Cards OAuth API
OPEN COLLECTIONQonto Business Cards Organizations & Accounts API
OPEN COLLECTIONQonto Business Cards Payment Links API
OPEN COLLECTIONQonto Business Cards SEPA Direct Debit API
OPEN COLLECTIONQonto Business Cards SEPA Transfers API
OPEN COLLECTIONQonto Business Cards Supplier Invoices API
OPEN COLLECTIONQonto Business Cards Terminals API
OPEN COLLECTIONQonto Business Cards Transactions & Statements API
OPEN COLLECTIONQonto Business Cards Webhooks API
OPEN COLLECTIONScroll within the panel for all 14 ·
MCP Servers 1
Model Context Protocol servers expose these APIs directly to AI agents. We profile them because agent-native access is the fastest-growing way this provider's capabilities actually get used.
Model Context Protocol servers that expose these APIs to AI agents.
Qonto MCP Server
Officially supported, actively maintained Qonto MCP server. Lets an AI assistant read and act on Qonto business-banking data through a curated set of tools. Built on top of the ...
MCP SERVERPricing Plans 1
Pricing is part of the interface. Machine-readable plans tell you what a tier costs and includes before you commit — one of the things the Kin Score reads for access clarity — renamed from commercial clarity in rubric 0.12, because a free statutory interface has access terms and no commercial ones.
Published pricing tiers and plan structures.
Qonto Plans Pricing
PLANSRate Limits 1
Rate limits are the difference between a demo that works and a production integration that doesn't fall over. Publishing them is an operational-transparency signal — and a hard requirement for any agent that plans its own throughput.
Documented rate limits and quota policies.
Qonto Rate Limits
RATE LIMITSFinOps 1
Cost, billing, and metering signals let a buyer model the financial operations of an API before it's live. We profile them for the same reason we profile pricing: the money is part of the contract.
Cost, billing, and metering signals for API financial operations.
Qonto Finops
FINOPSEvent Specifications 1
Not every API is request/response. AsyncAPI describes the event-driven and streaming side — the webhooks and channels — so the asynchronous half of the interface is documented the same way the synchronous half is.
AsyncAPI definitions for this provider's event-driven and streaming APIs.
Qonto Webhooks
ASYNCAPISecurity Posture 4
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Scopes 1
OAuth scopes are the vocabulary of least-privilege access. Profiling them shows exactly what an integration — or an agent acting on a user's behalf — is allowed to do.
OAuth scopes governing access to this provider's APIs.
Agentic Access 1
An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.
Recommended x-agentic-access execution contracts for AI agents.
Resources
Every other property we hold for Qonto — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Get Started 4
Portal, sign-up, and the first successful call
Documentation 2
Reference material describing how the API behaves
Agent Surfaces 5
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 8
Pagination, idempotency, versioning, errors, and events
Scroll within the panel for all 8 ·
Build 5
SDKs, sample code, and the tooling you integrate with
Access & Security 8
Authentication, authorization, and security posture
Scroll within the panel for all 8 ·
Operate 4
Status, limits, changes, and where to get help
Commercial 5
Pricing, plans, and the legal terms of use
Company 3
The organization behind the API
Other 2
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/qonto · machine-readable index on apis.io
This is an independent, third-party profile of Qonto, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.
The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.
Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.
info@apievangelist.com
·
Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and
you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.