Skip to content

POST /tms/transload-emails/approval-submit

TMS > tms.transload

What it does

/tms/transload-emails/approval-submit accepts POST and is declared in app/systems/TMS/transload/api_routes.php:679 as a path.

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

Call chain:

  1. → tmsTransloadApiPostAction() — app/systems/TMS/transload/request_api_helper.php:550
  2. ↳ apiRequestId() — app/shared/api/response.php:47
  3. ↳ apiNormalizeRequestId() — app/shared/api/response.php:33

Who calls it

Called from:

  • frontend/pages/system/TMS/transload/transload-email-approval.php

A caller is the strongest available evidence of the intended use.

Input

Where Key
body DEFER_REPLY

Request bodies must not use TYPE, ACTION or USERNAME as contract fields.

Output

Key
DATA

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.transload, so tenant module access applies

Validation and failure messages

  • Transload changed. Reload and try again.

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.