Skip to content

POST /bms/scale-tickets

BMS > bms.scale-ticket

What it does

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

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

Call chain:

  1. → bmsScaleTicketApiCreate() — app/systems/BMS/scale-ticket/api_routes.php:19
  2. ↳ bmsScaleTicketWrite() — app/systems/BMS/scale-ticket/api_routes.php:9
  3. ↳ bmsScaleTicketHandleWrite() — app/systems/BMS/scale-ticket/lifecycle_helper.php:4

Who calls it

Called from:

  • app/platform/api_catalog.php
  • app/systems/BMS/scale-ticket/history_helper.php
  • public/assets/js/modules/shared/kj-scale-ticket-modal.js
  • public/assets/js/modules/shared/scale-ticket-editor.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.

Data

No table reference is visible in the owner function body.

Access

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

Validation and failure messages

  • Scale ticket payload 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.