Kobana icon

Kobana

Interact with Kobana API - Quick access to common operations

Actions215

Admin > Subaccounts → Get Many

AI-generated

Overview

This node interacts with the Kobana API to manage subaccounts under the Admin resource, specifically supporting the "Get Many" operation for subaccounts. It allows users to retrieve multiple subaccount records from their Kobana environment, either returning all available results or limiting the number of results returned.

Typical use cases include:

  • Fetching a list of all subaccounts for administrative overview.
  • Retrieving a subset of subaccounts based on query parameters for reporting or integration purposes.
  • Automating workflows that require bulk processing or synchronization of subaccount data.

For example, an admin might use this node to pull all subaccounts to generate a report or to sync subaccount information with another system.

Properties

Name Meaning
Return All Whether to return all subaccount results or only up to a specified limit.
Limit The maximum number of subaccount results to return when "Return All" is false (1 to 100).
Additional Fields JSON object containing additional fields to include in the request (customizable options).
Query Parameters JSON object with query parameters to filter or modify the retrieval of subaccounts.

Output

The node outputs an array of JSON objects representing the retrieved subaccounts. Each object corresponds to a subaccount record as returned by the Kobana API.

  • The json output field contains the subaccount data.
  • No binary data output is indicated for 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 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 typically indicate invalid or missing API keys; verify and re-enter credentials.
    • JSON parsing errors suggest malformed JSON input in properties; ensure valid JSON syntax.
    • API rate limits or server errors should be handled by retrying after some time or checking API status.

Links and References

Discussion