Skip to content

PATCH /tms/transloads/(?P\d+)/appointment-time

TMS > tms.transload

What it does

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

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

Call chain:

  1. → tmsTransloadApiUpdateAppointmentTime() — app/systems/TMS/transload/request_api_helper.php:368
  2. ↳ tmsTransloadApiRowNotFoundMessage() — app/systems/TMS/transload/form_mutation_api_helper.php:131

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
APPOINTMENT_TIME
BILLING_COMPANY_ID
STATUS
TRANSLOAD_ID

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

SQL executed

SELECT ID, BILLING_COMPANY_ID, STATUS

Data

Tables reached from the owner function:

  • T_TRANSLOAD

Access

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

Validation and failure messages

  • TRANSLOAD_ID is required.
  • Appointment time is required.
  • Appointment time is invalid.
  • Completed loads cannot be rescheduled.
  • This load status cannot be rescheduled.

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.