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 export Call Detail Records (CDRs) for a selected customer. It supports exporting CDR data in various formats such as CSV, CDR, and PDF, and allows filtering by date range, CDR file IDs, call amount thresholds, and whether to include bundled calls. This node is useful for telecom or billing system integrations where detailed call records need to be retrieved and processed for reporting, auditing, or billing purposes.

Use Case Examples

  1. Export CDRs for a specific customer in CSV format for a given date range.
  2. Retrieve CDRs filtered by call amount threshold to analyze high-value calls.
  3. Download CDRs in PDF format for customer billing statements.

Properties

Name Meaning
Customer Select the customer for whom the CDR export is requested.
Format Specify the output format of the CDR export (CSV, CDR, or PDF).
From Start date/time to filter the CDR records.
To End date/time to filter the CDR records.
Cf Id Filter by specific CDR file IDs.
Call Amount Threshold Filter CDRs by minimum call amount.
Threshold Include Bundled Calls Whether to include bundled calls in the call amount threshold filter.

Output

JSON

  • data - The exported CDR data returned from the API, structure depends on the selected format.
  • error - Error details if the export operation fails.

Dependencies

  • Billing Booth One API

Troubleshooting

  • Ensure the API credentials are correctly configured and have sufficient permissions to access CDR data.
  • Verify that the customer ID is valid and exists in the system.
  • Check date/time filters are in ISO 8601 format; the node converts date/time inputs to ISO strings automatically.
  • If exporting binary data (e.g., PDF), ensure the binary property name is correctly specified and the binary data exists.
  • Common error messages include missing routing information for the selected resource-operation, invalid or missing parameters, and HTTP request failures. These can be resolved by verifying node parameters and API connectivity.

Discussion