Qonto icon

Qonto

Interact with Qonto API
Join our community

Actions45

Overview

The node interacts with the Qonto API to retrieve multiple "Request" records based on specified filters and pagination options. It is designed to fetch a list of requests such as card issuance, transfers, or other financial operations managed within Qonto.

This node is beneficial when you want to automate workflows that require bulk retrieval of request data from Qonto, for example:

  • Generating reports on pending or approved requests.
  • Synchronizing request data into another system.
  • Monitoring requests created or processed within a specific timeframe.

Properties

Name Meaning
Authentication Method of authentication; currently supports only "API Key".
Return All Whether to return all matching results or limit the output.
Limit Maximum number of results to return if not returning all (default 100, max 100).
Page Page number to retrieve when limiting results (starts at 1).
Filters Collection of filters to narrow down the requests:
- Status Filter by request status; options: Pending, Approved, Declined, Canceled.
- Request Type Filter by type of request; options: Flash Card, Virtual Card, Transfer, Multi Transfer.
- Created From Minimum creation date to filter requests from.
- Processed From Minimum processed date to filter requests from.

Output

The node outputs an array of JSON objects representing the retrieved requests. Each object corresponds to a single request record fetched from Qonto's API.

The exact structure of each request object depends on the Qonto API response but typically includes fields such as request ID, status, type, creation date, processing date, and other relevant metadata.

No binary data output is indicated for this operation.

Dependencies

  • Requires an API key credential for authenticating with the Qonto API.
  • The node uses Qonto's REST API endpoints, switching between sandbox and production URLs based on environment configuration.
  • Network connectivity to Qonto's API endpoints is necessary.

Troubleshooting

  • Common issues:

    • Invalid or missing API key will cause authentication failures.
    • Exceeding rate limits imposed by Qonto API may result in errors or throttling.
    • Providing invalid filter values or dates may lead to empty results or API errors.
    • Pagination parameters out of range (e.g., page < 1 or limit > 100) will be rejected.

  • Error messages:

    • "Unknown resource: request" — indicates the resource parameter was not recognized; ensure "Request" is selected.
    • API errors related to authentication or permissions usually indicate problems with the provided API key.
    • Validation errors on input parameters should be resolved by checking property constraints (e.g., limit max 100).

Links and References

Discussion