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 create a new destination resource. It allows users to specify various properties of the destination such as its unique identifier, name, unit type (voice, data, sms), currency unit, fallback status, tax exemption, billing exclusion, supplier details, pricing, charge codes, and more. This node is useful for automating the management of billing destinations in telecommunication or billing systems, enabling streamlined creation and configuration of destinations programmatically.

Use Case Examples

  1. Creating a new voice destination with specific pricing and supplier details.
  2. Adding a fallback destination that is tax exempt and excluded from billing.
  3. Defining a destination group with associated charge codes and output charge code for CDR processing.

Properties

Name Meaning
Additional Body Fields A collection of optional fields to specify detailed properties of the destination such as id, name, unit type, currency unit, fallback status, tax exemption, billing exclusion, supplier information, pricing, charge codes, and destination group details.

Output

JSON

  • json - The JSON response from the Billing Booth One API representing the created destination resource or error details if the operation fails.

Dependencies

  • Billing Booth One API with an API key credential for authentication

Troubleshooting

  • Common issues include missing or incorrect API credentials, resulting in authentication errors.
  • Invalid or incomplete input properties may cause the API to reject the request with validation errors.
  • Network connectivity issues can prevent the node from reaching the Billing Booth One API endpoint.
  • Error messages from the API are propagated and can include details about missing required fields or invalid data formats.

Links

Discussion