Kobana icon

Kobana

Interact with Kobana API - Quick access to common operations

Actions215

Overview

This node integrates with the Kobana API to manage PIX charge accounts, specifically allowing users to retrieve multiple PIX accounts in a single operation. It is useful for scenarios where you need to list or query many PIX accounts associated with charges, such as financial reconciliation, reporting, or bulk processing of account data.

For example, a user might want to fetch all PIX accounts linked to their charges to analyze payment sources or verify account details before initiating transfers or payments.

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 request when listing PIX accounts.
  • Return All: If true, the node will fetch all available PIX accounts without limiting the number.
  • Limit: When "Return All" is false, limits the number of PIX accounts returned (minimum 1, maximum 100).
  • Additional Fields: Allows passing extra JSON-formatted fields to customize the request.
  • Query Parameters: Enables specifying additional query parameters as a JSON object to refine the search or filtering criteria.

Output

The output is a JSON array where each element represents a PIX account related to charges retrieved from the Kobana API. Each item contains the full details of a PIX account as returned by the API, including identifiers, account information, and any metadata provided by the service.

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 the environment (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 or improper use of pagination parameters can lead to incomplete data retrieval.
  • Error Messages:

    • Authentication errors typically indicate issues with the API key or permissions.
    • JSON parsing errors suggest malformed input in the JSON fields.
    • HTTP errors from the API (e.g., 400 or 500 status codes) usually mean invalid parameters or server-side problems; reviewing the query parameters and request body is recommended.

Links and References

Discussion