status¶

TMS > tms.delivery

What it does¶

#^/tms/equipment-loads/(?P<id>\d+)/status$# accepts PATCH,POST and is declared in app/systems/TMS/delivery/api_routes.php:2188 as a regex pattern.

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

Call chain:

→ tmsDeliveryApiUpdateEquipmentLoadStatus() — app/systems/TMS/delivery/api_routes.php:676
↳ tmsDeliveryApiHasOfficeAccess() — app/systems/TMS/delivery/api_routes.php:956
↳ isSuperAdmin() — config/config.php:1477

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
`path`	`id`
`body`	`RETURN_BOOKING_ID`
`body`	`STATUS`
`body`	`returnBookingId`

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

Output¶

Key
`RETURN_BOOKING_ID`
`RETURN_BOOKING_UUID`
`STATUS`
`T_EQUIPMENT_LOAD`
`UPDATE`

Success is { "data": …, "requestId": "…" }. Failure is { "error": { "code", "message" }, "requestId": "…" }.

SQL executed¶

SELECT UUID FROM T_BOOKING WHERE CLIENT_ID=? AND ID=? AND DELETED_AT IS NULL LIMIT 1

SELECT EQL.ID,

Data¶

Tables reached from the owner function:

T_BOOKING
T_EQUIPMENT
T_EQUIPMENT_LOAD

Access¶

module-gated on tms.delivery, so tenant module access applies

Validation and failure messages¶

Office access is required to update load status.
Equipment load id is required.
Status must be EMPTY or FULL.
Equipment load row not found.
Equipment row not found.

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.

PATCH,POST /tms/equipment-loads/(?P\d+)/status¶