Skip to content

GET /bms/ar-billing/setup/customers

BMS > bms.transaction

What it does

/bms/ar-billing/setup/customers accepts GET and is declared in app/systems/BMS/ar-billing/api_routes.php:238 as a path.

The route handler delegates to bmsArBillingSetupCustomerOptions(). That function is the owner of this behaviour; the route entry is only dispatch.

Call chain:

  1. → bmsArBillingSetupCustomerOptions() — app/systems/BMS/ar-billing/setup_read_helper.php:48
  2. ↳ bmsArBillingSetupTenantUuid() — app/systems/BMS/ar-billing/setup_read_helper.php:4
  3. ↳ bmsArBillingUuidFromHex() — app/systems/BMS/ar-billing/foundation_helper.php:40

Who calls it

Called from:

  • public/assets/js/modules/bms/billing-setup.js

A caller is the strongest available evidence of the intended use.

Input

No named input key is visible in the handler or its owner function. The endpoint either takes no parameters or reads them through a shared helper in app/shared/api/.

Output

The response is produced by a shared helper, so the key set is not visible at the route. Read the owner function to confirm the shape before writing a client.

SQL executed

SELECT HEX(UUID) AS UUID_HEX,

SELECT HEX(UUID) FROM T_CLIENT WHERE ID = ?

Data

Tables reached from the owner function:

  • T_COMPANY

Access

  • module-gated on bms.transaction, so tenant module access applies

Validation and failure messages

  • Billing customer tenant identity is unavailable.

These strings come from the owner function and are the messages a client can receive. They are also the cheapest way to tell a rejected request from a broken one.