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 financial statement transactions, specifically allowing users to retrieve multiple statement transactions in bulk. It is useful for scenarios where you need to fetch a list of financial transactions from a bank or accounting system for reporting, reconciliation, or further processing.

For example, a user might want to:

  • Retrieve all statement transactions within a certain date range.
  • Limit the number of transactions fetched for performance reasons.
  • Apply custom query parameters to filter or sort the transactions.

This operation helps automate workflows that require up-to-date transaction data from financial statements.

Properties

Name Meaning
Return All Whether to return all available statement transactions or limit the number of results.
Limit The maximum number of statement transactions to return if not returning all (1 to 100).
Additional Fields JSON object containing additional fields to include in the request for extended options.
Query Parameters JSON object with query parameters to filter or customize the retrieval of statement transactions.

Output

The node outputs an array of JSON objects representing the retrieved statement transactions. Each object corresponds to a single transaction and contains all relevant details as returned by the Kobana API.

If binary data were involved (not indicated here), it would typically represent files or attachments related to transactions, but this operation focuses on JSON data only.

Dependencies

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

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 (max 100) will be rejected by the API.

  • Error Messages:

    • Authentication errors indicate issues with the provided API key; verify credentials.
    • Validation errors often relate to malformed JSON input or unsupported query parameters; ensure JSON syntax correctness.
    • Rate limiting or server errors from the API should be handled by retrying after some delay.

Links and References

Discussion