Kobana icon

Kobana

Interact with Kobana API - Quick access to common operations
Join our community

Actions215

Overview

This node interacts with the Kobana API to manage financial accounts and other related resources. Specifically, for the Financial > Accounts resource with the Get Many operation, it retrieves multiple financial account records from Kobana. This is useful when you want to list or analyze many accounts at once, such as generating reports, syncing account data, or performing bulk operations.

Practical examples:

  • Fetching all financial accounts to display in a dashboard.
  • Retrieving a limited number of accounts based on filters for auditing purposes.
  • Using query parameters to filter accounts by status, type, or other criteria.

Properties

Name Meaning
Return All Whether to return all results or only up to a given limit.
Limit Max number of results to return (only used if "Return All" is false). Range: 1 to 100.
Additional Fields JSON object with additional fields for the request (optional extra parameters).
Query Parameters JSON object with query parameters to filter or modify the request (e.g., filtering options).

Output

The output is a JSON array where each element represents a financial account object retrieved from the Kobana API. The exact structure of each account object depends on the API response but typically includes details like account ID, name, balance, status, and other relevant financial metadata.

No binary data output is produced by this operation.

Dependencies

  • Requires an active Kobana API credential with appropriate permissions.
  • The node uses the Kobana API endpoint, switching between production (https://api.kobana.com.br) and sandbox (https://api-sandbox.kobana.com.br) environments based on the credential configuration.
  • No additional external dependencies are required beyond the Kobana API access.

Troubleshooting

  • Common issues:

    • Invalid or missing API credentials will cause authentication failures.
    • Exceeding API rate limits may result in errors or throttling.
    • Providing malformed JSON in "Additional Fields" or "Query Parameters" can cause request errors.
    • Requesting more items than allowed by the API limit may be rejected.

  • Error messages:

    • Authentication errors: Check that the API key or token is valid and has necessary permissions.
    • JSON parse errors: Ensure that JSON inputs for additional fields and query parameters are correctly formatted.
    • HTTP errors (4xx or 5xx): Review the API documentation for error codes; verify request parameters and network connectivity.

Links and References

Discussion