Skip to main content
Qonto provides 2 collections of REST APIs and a Sandbox environment to help you build integrations on top of Qonto accounts, transactions, memberships, etc; no matter what your use case is. JSON is returned in all API responses, including errors. For security purposes:
  • All API requests must be made over HTTPS. Calls made over plain HTTP will fail.
  • All API requests (except the ones to /v2/oauth2/auth) must be made from your backend. Direct calls from browsers will fail.

Qonto APIs

Use cases

To access your Qonto business features remotely, use the Business API with:
  • OAuth 2.0 if you need to perform sensitive actions (cf. the endpoints access table to identify if you need to use an endpoint which is only accessible through OAuth) OR if you want to restrict the scopes accessible with your authentication credentials to a specific list of scopes;
  • Your API key otherwise.
The API key authentication method is much more simple to implement than OAuth 2.0.
To access Qonto business features on behalf of your customers, use the Business API with OAuth 2.0.
  • To create Qonto business accounts (and eventually companies) for your customers, use the Onboarding API;
  • To operate those accounts directly from your platform, use the Business API (with OAuth 2.0).
To create companies (digital KYB, KYC and capital deposit) for your customers, use the Onboarding API.