PATCH /tms/import-delivery-orders/container-destination¶
What it does¶
/tms/import-delivery-orders/container-destination accepts PATCH and is declared in app/systems/TMS/delivery/api_routes.php:2388 as a path.
The route handler delegates to tmsDeliveryApiChangeImportDeliveryDestination(). That function is the owner of
this behaviour; the route entry is only dispatch.
Call chain:
- →
tmsDeliveryApiChangeImportDeliveryDestination()—app/systems/TMS/delivery/api_routes.php:1240 - ↳
tmsDeliveryWrite()—app/systems/TMS/delivery/api_routes.php:624 - ↳
tmsDeliveryApiWriteResult()—app/systems/TMS/delivery/api_routes.php:66
Who calls it¶
Called from:
public/assets/js/modules/tms/import-dispatch.js
A caller is the strongest available evidence of the intended use.
Input¶
| Where | Key |
|---|---|
body |
CONSIGNEE_COMPANY_ID |
body |
EQUIPMENT_LOAD_ID |
body |
destinationCompanyId |
body |
equipmentLoadId |
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.
Data¶
No table reference is visible in the owner function body.
Access¶
- module-gated on
tms.delivery, so tenant module access applies
Validation and failure messages¶
- No Matching Containers!
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.