Skip to content

GET /bms/ar-billing/rates

BMS > bms.transaction

What it does

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

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

Call chain:

  1. → bmsArBillingRegisteredRates() — app/systems/BMS/ar-billing/foundation_helper.php:413
  2. ↳ bmsArBillingRegisteredRateCompany() — app/systems/BMS/ar-billing/foundation_helper.php:390
  3. ↳ bmsArBillingUuidToBinary() — app/systems/BMS/ar-billing/foundation_helper.php:27

Who calls it

No literal caller path was found in frontend/, public/ or new-system/. The endpoint may be called through a constructed path, a helper wrapper, or only by an external client. Treat the route table and owner function as the authority.

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 R.ID, HEX(R.UUID) AS UUID_HEX,

SELECT ID, HEX(UUID) AS UUID_HEX, COALESCE(DISPLAY_NAME, COMPANY_NAME, '') AS COMPANY_NAME

Data

Tables reached from the owner function:

  • T_COMPANY
  • T_TRUCKING_RATE

Access

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

Validation and failure messages

  • Customer is required.
  • Customer was not found.
  • UUID is required.

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.