Qonto is a business banking platform for European SMBs that provides business accounts, payment cards, and expense management. Its Business API exposes organizations, bank accounts, cards, memberships, teams, clients, labels, and attachments, allowing you to read this data into Nexla and push changes back to Qonto.
Power end-to-end data operations for your Qonto API with Nexla. Our bi-directional Qonto connector is purpose-built for Qonto, making it simple to ingest data, sync it across systems, and deliver it anywhere — all with no coding required. Nexla turns API-sourced data into ready-to-use, reusable data products and makes it easy to send data to Qonto or any other destination. With comprehensive monitoring, lineage tracking, and access controls, Nexla keeps your Qonto workflows fast, secure, and fully governed.
Features
Type: API
SourceDestination
Seamless API Integration: Connect to any endpoint as source or destination without coding, with automatic data product creation
Visual Composition & Chaining: Build complex integrations using visual templates, chain API calls, and compose workflows with data validation and filtering
API Proxy: Expose curated slices of your data securely with a secure and customizable API proxy that validates and transforms data on the fly
Request optimization with intelligent batching, retry, and caching to minimize API calls and costs
Before creating a Qonto credential, you need your Qonto API login and secret key. Qonto's Business API authenticates each request with an Authorization header containing your login:secret_key pair (for example, pied-piper-7132:62885d39f3a0ddedd3d3ee0432a43ccr). This is not the same as your Qonto email and password, and it is not Base64-encoded HTTP Basic authentication — the header value is the literal login:secret_key string with a real colon separator.
To obtain your API login and secret key:
Sign in to the Qonto web app with an account that has the appropriate permissions.
If you belong to more than one organization, select the organization you want to connect.
Open the Integrations and Partnerships section, then select API key.
Copy your login, and click Generate to create (or reveal) your secret key. Store the secret key securely, as it grants programmatic access to your Qonto organization.
Combine the two values into a single login:secret_key string. You will enter this combined value when creating the Nexla credential.
Most Qonto endpoints are available through an API key, while a specific subset is only accessible via OAuth. If your secret key is compromised, regenerate it from the same Integrations and Partnerships > API key screen. For details on authentication and available resources, see the Qonto API reference.
After selecting the data source/destination type, click the Add Credential tile to open the Add New Credential overlay.
Enter a name for the credential in the Credential Name field and a short, meaningful description in the Credential Description field.
Enter your Qonto login:secret_key value in the API Key Value field. Nexla sends this value in the Authorization header on every request to the Qonto API, so it must be kept confidential.
If your secret key is compromised, regenerate it from the Qonto web app under Integrations and Partnerships > API key, and update this credential with the new value. For more information about authentication and available endpoints, see the Qonto API reference.
Click the Save button at the bottom of the overlay. The newly added credential will now appear in a tile on the Authenticate screen during data source/destination creation.
To create a new data flow, navigate to the Integrate section, and click the New Data Flow button. Select the Qonto connector tile, then select the credential that will be used to connect to Qonto, and click Next; or, create a new Qonto credential for use in this flow.
Nexla provides pre-built templates that can be used to rapidly configure data sources to ingest data from common Qonto endpoints. Select the endpoint from which this source will fetch data from the Endpoint pulldown menu. Available endpoint templates are listed in the expandable boxes below.
[Rest API] Retrieve the authenticated organization and list bank accounts
This endpoint template retrieves the organization associated with your credential, including the list of bank accounts it holds. Use it to read core organization details and account identifiers for downstream flows.
For details about the organization resource and its fields, see the Qonto API reference.
[Rest API] Get user organizations
This endpoint template retrieves a specific organization by its identifier. Provide the Organization Id for the organization you want to fetch.
For details about the organization resource and its fields, see the Qonto API reference.
[Rest API] List business accounts
This endpoint template retrieves the bank accounts belonging to your organization. Use the optional Current Page and Per Page parameters to page through the results.
For details about the bank account resource and pagination, see the Qonto API reference.
[Rest API] Get a business account
This endpoint template retrieves a single bank account by its identifier. Provide the Bank Account Id for the account you want to fetch.
For details about the bank account resource and its fields, see the Qonto API reference.
[Rest API] List labels
This endpoint template retrieves the labels defined in your organization, which are used to categorize transactions. Use the optional Current Page parameter to page through the results.
For details about the label resource and pagination, see the Qonto API reference.
[Rest API] Retrieve a label
This endpoint template retrieves a single label by its identifier. Provide the Label Id for the label you want to fetch.
For details about the label resource and its fields, see the Qonto API reference.
[Rest API] List memberships
This endpoint template retrieves the memberships (people who belong to your organization). Use the optional Current Page and Per Page parameters to page through the results.
For details about the membership resource and pagination, see the Qonto API reference.
[Rest API] Retrieve the authenticated membership
This endpoint template retrieves the membership associated with the authenticated credential. Use it to read details about the current API user within the organization.
For details about the membership resource and its fields, see the Qonto API reference.
[Rest API] List teams
This endpoint template retrieves the teams defined in your organization. Use it to read team structure for reporting or synchronization.
For details about the team resource and its fields, see the Qonto API reference.
[Rest API] Retrieve the organization's current subscription plan
This endpoint template retrieves the organization's current subscription plan. Use it to read details about the active Qonto plan for your organization.
For details about the subscription resource and its fields, see the Qonto API reference.
[Rest API] List cards
This endpoint template retrieves the payment cards issued within your organization. Use the optional Current Page parameter to page through the results.
For details about the card resource and pagination, see the Qonto API reference.
[Rest API] List clients
This endpoint template retrieves the clients defined in your organization, which are used for invoicing. Use the optional Current Page parameter to page through the results.
For details about the client resource and pagination, see the Qonto API reference.
[Rest API] Retrieve a client
This endpoint template retrieves a single client by its identifier. Provide the Client Id for the client you want to fetch.
For details about the client resource and its fields, see the Qonto API reference.
[Rest API] Retrieve an attachment
This endpoint template retrieves a single attachment by its identifier. Provide the Attachment Id for the attachment you want to fetch.
For details about the attachment resource and its fields, see the Qonto API reference.
[Rest API] List attachments for a transaction
This endpoint template retrieves the attachments associated with a specific transaction. Provide the Transaction Id for the transaction whose attachments you want to fetch.
For details about the attachment resource and its fields, see the Qonto API reference.
Once the selected endpoint template has been configured, click the Test button to the right of the endpoint selection menu to retrieve a sample of the data that will be fetched. Sample data will be displayed in the Endpoint Test Result panel on the right, allowing you to verify that the source is configured correctly before saving.
Qonto data sources can also be manually configured to ingest data from any valid Qonto API endpoint, including endpoints not covered by the pre-built templates, chained API calls, or custom request parameters. Select the Advanced tab at the top of the configuration screen, and follow the instructions in Connect to Any API to configure the API method, endpoint URL, date/time and lookup macros, path to data, metadata, and request headers.
Once all of the relevant settings have been configured, click the Create button in the upper right corner of the screen to save and create the new Qonto data source. Nexla will now begin ingesting data from the configured endpoint and will organize any data that it finds into one or more Nexsets.
Click the + icon on the Nexset that will be sent to the Qonto destination, and select the Send to Destination option from the menu. Select the Qonto connector from the list of available destination connectors, then select the credential that will be used to connect to Qonto, and click Next; or, create a new Qonto credential for use in this flow.
Nexla provides pre-built templates that can be used to rapidly configure destinations to send data to common Qonto endpoints. Select the endpoint to which data will be sent from the Endpoint pulldown menu. Then, click on the template in the list below to expand it, and follow the instructions to configure additional endpoint settings.
[Rest API] Create a business account
This endpoint template creates a new business (bank) account in your organization using records from a Nexset. Each record is sent as a JSON request body describing the account to create.
The request body must match the format expected by the Qonto API. For details about the bank account resource and required fields, see the Qonto API reference.
[Rest API] Update a business account
This endpoint template updates an existing business account identified by the Bank Account Id. Each record is sent as a JSON request body describing the fields to update.
The request body must match the format expected by the Qonto API. For details about the bank account resource and updatable fields, see the Qonto API reference.
[Rest API] Close a business account
This endpoint template closes an existing business account identified by the Bank Account Id. Use it to programmatically close accounts based on records from a Nexset.
The request body must match the format expected by the Qonto API. For details about closing a bank account, see the Qonto API reference.
[Rest API] Create a membership
This endpoint template creates a new membership in your organization using records from a Nexset. Each record is sent as a JSON request body describing the membership to create.
The request body must match the format expected by the Qonto API. For details about the membership resource and required fields, see the Qonto API reference.
[Rest API] Create a team
This endpoint template creates a new team in your organization using records from a Nexset. Each record is sent as a JSON request body describing the team to create.
The request body must match the format expected by the Qonto API. For details about the team resource and required fields, see the Qonto API reference.
[Rest API] Create a card
This endpoint template creates a new payment card in your organization using records from a Nexset. Each record is sent as a JSON request body describing the card to create.
The request body must match the format expected by the Qonto API. For details about the card resource and required fields, see the Qonto API reference.
[Rest API] Discard a card
This endpoint template discards (deletes) a payment card identified by the Card Id. Use it to programmatically remove cards based on records from a Nexset.
The request body must match the format expected by the Qonto API. For details about discarding a card, see the Qonto API reference.
[Rest API] Lock a card
This endpoint template locks a payment card identified by the Card Id, temporarily preventing its use. Use it to programmatically lock cards based on records from a Nexset.
The request body must match the format expected by the Qonto API. For details about locking a card, see the Qonto API reference.
[Rest API] Unlock a card
This endpoint template unlocks a payment card identified by the Card Id, restoring its use after it has been locked. Use it to programmatically unlock cards based on records from a Nexset.
The request body must match the format expected by the Qonto API. For details about unlocking a card, see the Qonto API reference.
[Rest API] Update a card's limits
This endpoint template updates the spending limits of a payment card identified by the Card Id. Each record is sent as a JSON request body describing the new limits.
The request body must match the format expected by the Qonto API. For details about card limits and updatable fields, see the Qonto API reference.
[Rest API] Create a client
This endpoint template creates a new client in your organization using records from a Nexset. Each record is sent as a JSON request body describing the client to create.
The request body must match the format expected by the Qonto API. For details about the client resource and required fields, see the Qonto API reference.
[Rest API] Update a client
This endpoint template updates an existing client identified by the Client Id. Each record is sent as a JSON request body describing the fields to update.
The request body must match the format expected by the Qonto API. For details about the client resource and updatable fields, see the Qonto API reference.
[Rest API] Delete a client
This endpoint template deletes an existing client identified by the Client Id. Use it to programmatically remove clients based on records from a Nexset.
The request body must match the format expected by the Qonto API. For details about deleting a client, see the Qonto API reference.
[Rest API] Upload an attachment
This endpoint template uploads a new attachment to your organization using records from a Nexset. Each record is sent as a JSON request body describing the attachment to upload.
The request body must match the format expected by the Qonto API. For details about the attachment resource and required fields, see the Qonto API reference.
[Rest API] Upload an attachment to a transaction
This endpoint template uploads an attachment to a specific transaction identified by the Transaction Id. Each record is sent as a JSON request body describing the attachment to upload.
The request body must match the format expected by the Qonto API. For details about transaction attachments and required fields, see the Qonto API reference.
Qonto destinations can also be manually configured to send data to any valid Qonto API endpoint. Select the Advanced tab at the top of the configuration screen, and follow the instructions in Connect to Any API to configure the API method, data format, endpoint URL, request headers, attribute exclusions, record batching, and response webhooks.
Qonto APIs expect JSON format for most operations. For update operations, include the ID of the object to be updated in the endpoint URL.
Once all endpoint settings have been configured, click the Done button in the upper right corner of the screen to save and create the destination. To send the data to the configured Qonto endpoint, open the destination resource menu, and select Activate.
The Nexset data will not be sent to the Qonto endpoint until the destination is activated. Destinations can be activated immediately or at a later time, providing full control over data movement.
