Kobana icon

Kobana

Interact with Kobana API - Quick access to common operations

Actions215

Overview

This node interacts with the Kobana API to manage bank billet batches within the Payment resource. Specifically, the Update operation allows you to modify an existing bank billet batch by sending a JSON request body with the desired changes. This is useful for updating batch details such as metadata or status after creation.

Practical scenarios include:

  • Adjusting batch attributes like description or due dates.
  • Correcting information in an existing batch without recreating it.
  • Automating updates to batches based on external triggers or workflows.

Properties

Name Meaning
ID The unique identifier of the bank billet batch to update.
Request Body A JSON object containing the fields and values to update in the bank billet batch.
Additional Fields (Optional) A JSON object with extra fields for the request; can be used to extend data.

Output

The node outputs a JSON object representing the updated bank billet batch as returned by the Kobana API. This typically includes all batch details after the update, such as IDs, status, timestamps, and any modified fields.

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

  • Invalid ID error: Ensure the provided batch ID exists and is correctly formatted.
  • Malformed JSON in Request Body: The request body must be valid JSON; syntax errors will cause failures.
  • Authentication errors: Verify that the API key credential is valid and has permissions to update bank billet batches.
  • API rate limits or network issues: May cause request failures; retry or check connectivity.
  • Unexpected response structure: Confirm that the Kobana API version matches expectations and that the node configuration aligns with the API documentation.

Links and References

Discussion