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 DARF payment batches within the Payment resource. Specifically, the "Get Many" operation retrieves a list of DARF batches, allowing users to fetch multiple batch records in one request. This is useful for financial workflows where you need to review, report on, or process multiple DARF payment batches at once.

Practical examples include:

  • Fetching all DARF batches created within a certain period for reconciliation.
  • Retrieving a limited number of recent DARF batches for auditing purposes.
  • Applying query filters to get batches matching specific criteria such as status or date range.

Properties

Name Meaning
Return All Whether to return all results or only up to a given limit.
Limit Maximum number of results to return (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 list request (e.g., filtering, sorting).

Output

The output is a JSON array where each item represents a DARF batch object returned by the Kobana API. Each object contains details about a DARF payment batch such as its ID, status, creation date, and other relevant metadata as provided by the API.

No binary data output is involved in this operation.

Dependencies

  • Requires an API key credential for authenticating with the Kobana API.
  • The node dynamically selects the API base URL depending on the environment (production or sandbox).
  • No additional external dependencies are required beyond the Kobana API access.

Troubleshooting

  • Common issues:

    • Authentication errors if the API key credential is missing or invalid.
    • Request limits exceeded if too many items are requested without enabling pagination or limiting results.
    • Malformed JSON in Additional Fields or Query Parameters can cause request failures.

  • Error messages:

    • Errors from the Kobana API will be returned in the output JSON under an error field if "Continue On Fail" is enabled.
    • Typical HTTP errors like 401 Unauthorized indicate credential problems.
    • 400 Bad Request may indicate invalid query parameters or malformed JSON input.

  • Resolutions:

    • Verify that the API key credential is correctly configured and has necessary permissions.
    • Use the "Limit" property to restrict the number of results when not returning all.
    • Ensure JSON inputs for additional fields and query parameters are valid and properly formatted.

Links and References

Discussion