Skip to main content
The Business API enables:
  1. our customers to access their Qonto business features remotely in order to automate their business operations (e.g. payments, card creation, transaction synchronisation and reconciliation);
  2. our partners to access Qonto business features on behalf of their customers in order to:
    • offer to those customers an integration with Qonto (and eventually publish this integration in our Marketplace),
    • or, thanks to our Qonto Embed offering, operate Qonto business accounts directly from their platform with minimal back-and-forth between their application and the Qonto application.
Qonto business features includes the following (depending on the price plan of the business account): banking, invoicing, bookkeeping & more (cf. the endpoints available to discover all the capacities of the Business API). Here are some examples of the Business API most used capabilities:
To do so, you will need to call 2 endpoints:
  1. Retrieve the authenticated organization and list bank accounts
    🔗 EndpointGET https://thirdparty.qonto.com/v2/organization
    🔒 AuthAPI Key or OAuth 2.0 (organization.read scope)
    📲 SCANo
    To learn more about this endpoint, click here.
  2. List transactions
    You will need to specify the idor the iban of the bank account retrieved with the previous API call.
    🔗 EndpointGET https://thirdparty.qonto.com/v2/transactions
    🔒 AuthAPI Key or OAuth 2.0 (organization.read scope)
    📲 SCANo
    To learn more about this endpoint, click here.
There are 3 different ways of initiating external transfers:
  • Create external transfers with beneficiaries data
    This endpoint is only accessible using Strong Customer Authentication 👉 it requires a user interaction during the external transfers creation flow: the authenticated membership needs to approve the external transfers in the Qonto mobile app (after receiving a push notification).
    🔗 EndpointPOST https://thirdparty.qonto.com/v2/external_transfers/checkout
    🔒 AuthOAuth 2.0 only (payment.write scope)
    📲 SCAYes 👉 the external transfers creation will not be fully automated; the authenticated membership will receive a push notification and will have to approve the external transfers within 15 minutes.
    👤 Beneficiary typeAny type of beneficiary (i.e. new or existing one, trusted or not); if the beneficiary doesn’t exist, it will be created once the transfer is successfully created.
    🔢 Number of transfersUp to 400
    To learn more about this endpoint, click here.
  • Create an external transfer with trusted beneficiary
    This endpoint doesn’t require any user interaction once the beneficiary is trusted. A beneficiary can only be trusted through Qonto app.
    🔗 EndpointPOST https://thirdparty.qonto.com/v2/external_transfers
    🔒 OAuth scopeOAuth 2.0 only (payment.write scope)
    📲 SCANo 👉 the external transfer creation will be fully automated.
    👤 Beneficiary typeOnly trusted beneficiary; the list of trusted beneficiaries can be retrieved through the List beneficiaries endpoint.
    🔢 Number of transfers1
    To learn more about this endpoint, click here.
  • Create a transfers request
    This endpoint requires a user interaction after the transfers request creation: the transfers request must be approved by a membership of the authenticated organization with permissions to review requests.
    🔗 EndpointPOST https://thirdparty.qonto.com/v2/requests/multi_transfers
    🔒 OAuth scopeOAuth 2.0 only (request_transfers.write scope)
    📲 SCANo 👉 the transfers request creation will be fully automated but not the external transfers creation since the request will have first to be approved by a membership in the Qonto app without any time constraints.
    👤 Beneficiary typeAny type of beneficiary (i.e. new or existing one, trusted or not); if the beneficiary doesn’t exist, it will be created once the transfer is successfully created.
    🔢 Number of transfersUp to 400
    To learn more about this endpoint, click here.