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 update supplier CDR (Call Detail Record) settings. It allows users to modify various CDR-related configurations for a supplier, such as enabling CDR support, setting the parser type, match type, header presence, start row, delimiter, validation code, parsing code, and parser version. This node is useful in scenarios where telecom or billing systems need to customize how CDR files from suppliers are processed and validated, ensuring accurate data import and handling.

Use Case Examples

  1. Updating a supplier to enable CDR support and specify that the CDR files are CSV formatted with headers.
  2. Configuring a supplier's CDR parser to use a recursive match type and custom JavaScript code for parsing each row.

Properties

Name Meaning
Id Unique identifier of the supplier to update.
Additional Body Fields Optional fields to customize the CDR settings for the supplier, including enabling CDR support, parser type, match type, header presence, start row, delimiter, validation code, parsing code, and parser version.

Output

JSON

  • json - Response data from the Billing Booth One API after updating the supplier CDR settings.

Dependencies

  • Billing Booth One API
  • An API key credential for authentication

Troubleshooting

  • Ensure the 'Id' property is correctly set to the supplier's unique identifier; missing or incorrect Id will cause errors.
  • If using binary data input, verify the binary property name exists and contains valid data.
  • Check that the API base URL and access token are correctly configured in the credentials.
  • Common error messages include missing routing information for the specified resource and operation, which indicates misconfiguration or unsupported operation.
  • JavaScript code provided in 'Cdr Validate Header Code' and 'Cdr Parse Row Code' must be valid to avoid runtime errors during parsing.

Discussion