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 CLI (Caller Line Identification) records. It allows users to modify details of a CLI such as its identifier, type, associated customer, and various optional fields like description, cost centre, and billing exclusions. This node is useful in scenarios where automated updates to telephony line information are needed, for example, updating customer line details in bulk or integrating CLI management into a larger workflow.

Use Case Examples

  1. Updating a CLI's identifier and type for a specific customer.
  2. Setting spending caps and billing exclusions on a CLI to control costs.
  3. Adding descriptive information to a CLI for easier identification in reports.

Properties

Name Meaning
Id Unique identifier of the CLI record to update, required for the update operation.
Identifier Line identifier string, required to specify the CLI's identifier.
Cli Type Id Numeric type of the line, required to specify the CLI type.
Customer Id Numeric identifier associating the CLI to a customer, required for the update.
Additional Body Fields Optional additional fields to include in the update request body, such as description, cost centre, billing exclusions, and spending caps.

Output

JSON

  • data - The response data from the Billing Booth One API after updating the CLI.

Dependencies

  • Billing Booth One API access with an API key credential

Troubleshooting

  • Common issues include missing required fields such as 'id', 'identifier', 'cli_type_id', or 'customer_id', which will cause the API request to fail.
  • Errors related to authentication usually indicate invalid or missing API credentials; ensure the API key is correctly configured.
  • If the node throws an error about missing routing information, it means the resource-operation combination is not properly defined or supported.
  • Network or API endpoint errors can occur if the base URL is incorrect or the API service is unavailable.

Discussion