Kobana icon

Kobana

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

Actions215

Overview

This node integrates with the Kobana API to manage PIX transfers under the "Transfer > PIX" resource, specifically supporting the "Get Many" operation. It allows users to retrieve multiple PIX transfer records from their Kobana account efficiently. This is useful for scenarios where you need to list or analyze many PIX transfers, such as generating reports, auditing transactions, or syncing data with other systems.

For example, a finance team could use this node to fetch all PIX transfers made within a certain period or matching specific criteria, enabling automated reconciliation or monitoring workflows.

Properties

Name Meaning
Return All Whether to return all PIX transfer results or limit the number of returned items.
Limit The maximum number of PIX transfer results to return if not returning all (1 to 100).
Additional Fields JSON object with additional fields to include in the request (optional extra parameters).
Query Parameters JSON object with query parameters to filter or modify the request (e.g., date ranges, status).

Output

The node outputs an array of JSON objects representing PIX transfers retrieved from the Kobana API. Each object contains details about a single PIX transfer, such as identifiers, amounts, dates, and statuses, depending on what the API returns.

No binary data output is involved; the output is purely structured JSON data suitable for further processing or storage.

Dependencies

  • Requires an API key credential for authenticating with the Kobana API.
  • The node dynamically selects the API base URL based on the environment (production or sandbox).
  • No other external dependencies are required beyond standard HTTP requests to the Kobana API.

Troubleshooting

  • Common Issues:

    • Incorrect or missing API credentials will cause authentication failures.
    • Providing invalid JSON in "Additional Fields" or "Query Parameters" may result in request errors.
    • Exceeding the allowed limit (more than 100) will be rejected by the API.
    • Network connectivity issues can prevent successful API calls.

  • Error Messages:

    • Authentication errors typically indicate invalid or expired API keys; verify and update credentials.
    • JSON parsing errors suggest malformed JSON input in properties; ensure valid JSON syntax.
    • Rate limiting or quota exceeded errors require checking API usage limits and possibly throttling requests.
    • If the node throws unknown errors, enabling "Continue On Fail" can help isolate problematic inputs.

Links and References

Discussion