Skip to content

PATCH /tms/transload-planner/events/(?P\d+)

TMS > tms.transload

What it does

#^/tms/transload-planner/events/(?P<id>\d+)$# accepts PATCH and is declared in app/systems/TMS/transload/api_routes.php:336 as a regex pattern.

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

Call chain:

  1. → tmsTransloadApiPlannerUpdate() — app/systems/TMS/transload/planning_query_api_helper.php:5
  2. ↳ billing_post_handle_transload_planner() — app/systems/BMS/transaction/post_helper.php:130
  3. ↳ transload_planner_update() — app/systems/BMS/transaction/post_helper.php:780

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 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.

Data

No table reference is visible in the owner function body.

Access

  • module-gated on tms.transload, so tenant module access applies