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 transfer batches, specifically allowing users to retrieve multiple transfer batch records. It is useful in scenarios where you need to list or analyze batches of transfers made via the Kobana platform, such as financial reconciliation, reporting, or auditing transfer activities.

For example, a user might want to fetch all transfer batches within a certain date range or filter by status to monitor pending or completed transfers.

Properties

Name Meaning
Return All Whether to return all results or only up to a given limit.
Limit Maximum number of results to return (1 to 100). Only used if "Return All" is false.
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, sorting).

Output

The output is a JSON array containing the transfer batch objects returned by the Kobana API. Each item in the array represents a transfer batch with its associated data fields as provided by the API.

No binary data output is produced by this operation.

Dependencies

  • Requires an API key credential for authenticating with the Kobana API.
  • The node automatically selects the API base URL depending on whether the environment is production or sandbox.
  • No other external dependencies are required.

Troubleshooting

  • Common issues:
    • Invalid or missing API credentials will cause authentication errors.
    • Providing malformed JSON in "Additional Fields" or "Query Parameters" may result in request failures.
    • Exceeding the maximum allowed limit (over 100) will be rejected by the API.
  • Error messages:
    • Authentication errors indicate invalid or expired API keys; verify and update credentials.
    • JSON parsing errors suggest incorrect JSON syntax in input fields; validate JSON format.
    • Rate limiting or quota exceeded errors require checking API usage limits and possibly throttling requests.

Links and References

Discussion