Skip to content

POST /tms/dispatch/delivery

TMS > tms.delivery

What it does

/tms/dispatch/delivery accepts POST and is declared in app/systems/TMS/delivery/api_routes.php:2424 as a path.

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

Call chain:

  1. → tmsDeliveryApiDispatchCreate() — app/systems/TMS/delivery/api_routes.php:1224
  2. ↳ tmsDeliveryWrite() — app/systems/TMS/delivery/api_routes.php:624
  3. ↳ tmsDeliveryApiWriteResult() — app/systems/TMS/delivery/api_routes.php:66

Who calls it

Called from:

  • public/assets/js/modules/shared/popup.core.js
  • public/assets/js/modules/tms/delivery-dispatch-modal.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

Key
VALUE

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

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.