Overview
This node allows users to interact with the BVNK API, a financial service platform. It supports two main operations:
- List Wallets: Retrieves a list of all wallets associated with the authenticated account.
- Custom API Call: Enables making arbitrary HTTP requests to any BVNK API endpoint, allowing flexible interaction beyond predefined operations.
Typical use cases include automating wallet management tasks, retrieving wallet data for reporting, or integrating custom BVNK API endpoints into workflows without waiting for native node support.
For example, a user might list all wallets to sync them with another system or perform a custom POST request to create a new transaction or update wallet details.
Properties
| Name | Meaning |
|---|---|
| Operation | Selects the action to perform: "List Wallets" or "Custom API Call". |
| HTTP Method | The HTTP method for the custom API call. Options: DELETE, GET, PATCH, POST, PUT. |
| API Path | The path of the BVNK API endpoint to call (must start with "/"), e.g., /api/wallet. |
| Request Body (JSON) | Optional JSON string to send as the request body in the custom API call. |
Output
The node outputs an array of JSON objects representing the response from the BVNK API.
- For List Wallets, the output is the JSON array returned by the
/api/walletGET endpoint, typically containing wallet details. - For Custom API Call, the output is the parsed JSON response from the specified API endpoint.
If an error occurs and "Continue On Fail" is enabled, the output will contain an object with an error property describing the issue.
The node does not output binary data.
Dependencies
- Requires an API key credential for authenticating with the BVNK API.
- The base URL defaults to
https://api.bvnk.combut can be overridden via credentials. - Uses n8n's built-in HTTP request helper with authentication support.
Troubleshooting
- Invalid API Path: The API Path must be specified and start with a forward slash (
/). Omitting this or providing an invalid path will cause an error. - Invalid JSON in Request Body: If the JSON provided in the Request Body field is malformed, the node will throw an error indicating the JSON parsing issue.
- Authentication Errors: Ensure that the API key credential is correctly configured and has sufficient permissions.
- HTTP Errors: Any HTTP errors returned by the BVNK API will cause the node to fail unless "Continue On Fail" is enabled, in which case the error message is included in the output.
- Content-Type Header: For GET and DELETE methods without a request body, the
Content-Typeheader is omitted to avoid issues with some APIs.
Links and References
- BVNK API Documentation (Assumed official API docs; replace with actual if available)
- n8n Documentation on Creating Custom Nodes
- n8n Documentation on HTTP Request Node (for understanding HTTP methods and headers)