Billing Booth One icon

Billing Booth One

Interact with Billing Booth One API

Actions476

Overview

This node interacts with the Billing Booth One API to retrieve all price adjustments based on specified filters and options. It is useful for scenarios where users need to fetch detailed pricing adjustment data for voice, data, or SMS units, filtered by various criteria such as destination, supplier, tariff, customer, or organization. For example, a telecom operator might use this node to get all price adjustments related to a specific supplier or tariff to analyze cost changes or billing adjustments.

Use Case Examples

  1. Retrieve all price adjustments for voice units with a limit of 20 entries.
  2. Fetch price adjustments filtered by a specific destination group and sorted by action.
  3. Get price adjustments for a particular customer and tariff with pagination using offset and limit.

Properties

Name Meaning
Limit Maximum number of entries to return.
Offset Starting offset for pagination.
Unit Type Filter price adjustments by unit type (voice, data, or SMS).
Destination Id Filter price adjustments by destination ID.
Destination Group Id Filter price adjustments by destination group ID.
Supplier Id Filter price adjustments by supplier ID.
Supplier Platform Id Filter price adjustments by supplier platform ID.
Tariff Id Filter price adjustments by tariff ID.
Customer Id Filter price adjustments by customer ID.
Organisation Id Filter price adjustments by organisation ID.
Sort Sort order of results, supporting multiple comma-separated values (e.g., name,reference).

Output

JSON

  • data - The main data object containing the list of price adjustments returned by the API.

Dependencies

  • Requires an API key credential for Billing Booth One API authentication.

Troubleshooting

  • Common issues include missing or invalid API credentials, resulting in authentication errors.
  • Incorrect or unsupported filter values may cause the API to return errors or empty results.
  • Network or connectivity issues can cause request failures; ensure the base URL is correct and accessible.
  • If the binary property name is specified but the binary data is missing, an error will be thrown.

Discussion