Skip to content

GET /bms/scale-tickets/history

BMS > bms.scale-ticket

What it does

/bms/scale-tickets/history accepts GET and is declared in app/systems/BMS/scale-ticket/api_routes.php:65 as a path.

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

Call chain:

  1. → bmsScaleTicketHistoryValue() — app/systems/BMS/scale-ticket/history_helper.php:104
  2. ↳ bmsScaleTicketHistoryDate() — app/systems/BMS/scale-ticket/history_helper.php:2

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

Where Key
body TICKET_NUMBER

Request bodies must not use TYPE, ACTION or USERNAME as contract fields.

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 * FROM T_SCALE_TICKET WHERE CLIENT_ID=? AND TICKET_NUMBER=? AND DELETED_AT IS NULL LIMIT 1

Data

Tables reached from the owner function:

  • T_SCALE_TICKET

Access

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

Validation and failure messages

  • TICKET_NUMBER is required.
  • Scale ticket not found.
  • Scale ticket number must use the TYYYYMMDD-NNNN format.
  • Scale ticket number has an invalid date.

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.