GET /tms/bookings/(?P\d+)/packing-list/files¶
What it does¶
#^/tms/bookings/(?P<id>\d+)/packing-list/files$# accepts GET and is declared in app/systems/TMS/booking/api_routes.php:1712 as a regex pattern.
The route handler delegates to packing_list_url(). 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¶
| Key |
|---|
PATH |
STORAGE |
URL |
Success is { "data": …, "requestId": "…" }.
Failure is { "error": { "code", "message" }, "requestId": "…" }.
Data¶
Tables reached from the owner function:
T_BOOKINGT_DELIVERYT_EQUIPMENTT_EQUIPMENT_LOADT_FILE
Access¶
- module-gated on
tms.booking, so tenant module access applies