POST /tms/transload-emails/create-confirmation-reply¶
What it does¶
/tms/transload-emails/create-confirmation-reply accepts POST and is declared in app/systems/TMS/transload/api_routes.php:687 as a path.
The route handler delegates to tmsTransloadApiSendCreateConfirmationReply(). That function is the owner of
this behaviour; the route entry is only dispatch.
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¶
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 |
|---|
ITEM_IDS |
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¶
- itemIds is required.
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.