Skip to main content
Need the authentication method or the OAuth scope required for an endpoint? Check the endpoints access table. Every endpoint page also shows it right below its method and URL.
OAuth scopes define what your application is allowed to do on behalf of a Qonto user. When a user connects their account, they see a consent screen listing the exact permissions your application is requesting. Only request the scopes you actually need.
Building a new integration? Before selecting scopes, make sure you’ve chosen the right use case for your application. If your integration uses sensitive scopes, check the approval requirements by use case before going to production.

Scope selection guidance

Do you need organization.read?

organization.read is one of the most commonly requested scopes, but also the most broad. Before requesting it, consider whether a narrower scope covers your actual need:

Do you need beneficiary.trust or payment.write for beneficiary management?

These two scopes cover different sides of SEPA beneficiary trust management and are often needed together:
Trusting a beneficiary lets your integration initiate transfers to that beneficiary without requiring SCA on every transaction. The actual transfer still requires payment.write.

Fetching invoice PDFs without organization.read

If your only requirement is downloading supplier or client invoice PDFs, you can avoid the sensitive organization.read scope entirely by using attachment.read. How it works:
  1. Fetch the supplier invoice (supplier_invoice.read) or client invoice (client_invoices.read). The response includes an attachment_id field.
  2. Call GET /v2/attachments/{id} using the attachment.read scope.
  3. The response includes a pre-signed url you can use to download the PDF directly.
This approach only works when fetching invoice PDFs is your sole need. If you also need transaction data, account balances, or organization details, organization.read is still required.
For client invoices in Factur-X format, the PDF may need to be regenerated before download. If the url is not immediately available in the response, retry the request after a short delay. Learn more

Endpoints access

Generated from the OpenAPI security field of every published Business API operation. API key and OAuth 2.0 show which authentication methods the endpoint accepts; Scope(s) are the OAuth scopes the access token needs; a Sensitive tag marks endpoints that need a sensitive scope.

Endpoints requiring Strong Customer Authentication

The following endpoints were marked as requiring Strong Customer Authentication (SCA) in the former endpoints access table. Endpoint pages also describe their SCA requirements below the method and URL.

Available scopes

Generated from api-reference/business-api/components/security/schemes.yml (scope descriptions and the x-sensitive-scopes list). Consent messages are displayed to Qonto users on the consent screen during the OAuth authorization flow. Scopes marked NA do not display a permission entry on the consent screen. Consent messages are displayed on the consent screen 👇 Consent screen