GET /tms/bookings/(?P\d+)/containers¶
What it does¶
#^/tms/bookings/(?P<id>\d+)/containers$# accepts GET and is declared in app/systems/TMS/booking/api_routes.php:1690 as a regex pattern.
The route handler delegates to container_list_by_booking_id(). That function is the owner of
this behaviour; the route entry is only dispatch.
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 |
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_BOOKING WHERE CLIENT_ID = ? AND ID = ? AND DELETED_AT IS NULL
SELECT EQL.ID, EQL.OUTBOUND_ORDER_ID,
Data¶
Tables reached from the owner function:
T_BOOKINGT_COMPANYT_EQUIPMENTT_EQUIPMENT_COMMODITYT_EQUIPMENT_LOADT_LOADT_YARD_LOCATION
Access¶
- module-gated on
tms.booking, so tenant module access applies