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 product details. It is designed for scenarios where users need to modify existing product information such as name, type, pricing, category, and additional attributes. Practical applications include updating product catalogs in billing or invoicing systems, adjusting pricing strategies, or managing product metadata for integration with third-party services.

Use Case Examples

  1. Updating the name and sell price of a product identified by its ID.
  2. Changing the product type from single to recurring for subscription-based services.
  3. Adding or modifying additional product details like accounting codes, tax rates, or supplier information.

Properties

Name Meaning
Id Unique identifier of the product to update, required to specify which product to modify.
Name The name or description of the product or service, required for identification and display.
Type Specifies whether the product is a single purchase or recurring, affecting billing cycles.
Sell Price The price at which the product is sold per unit, essential for billing calculations.
Category Id Identifier for the category the product belongs to, used for organization and filtering.
Additional Body Fields Optional collection of extra product attributes such as details, reference codes, metadata, accounting codes, pricing options, tax rates, service codes, supplier info, and various flags controlling processing behavior.

Output

JSON

  • json - The response from the Billing Booth One API after updating the product, typically containing the updated product details or status information.

Dependencies

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

Troubleshooting

  • Ensure the product Id is valid and exists in the system to avoid errors related to missing or invalid identifiers.
  • Verify that all required fields (Id, Name, Type, Sell Price, Category Id) are provided and correctly formatted to prevent validation errors.
  • Check API base URL configuration and network connectivity if requests fail to reach the Billing Booth One API.
  • Handle API error responses gracefully; the node supports continue-on-fail to allow processing of multiple items even if some fail.

Links

Discussion