scheduled-inquiry-email¶

TMS > tms.transload

What it does¶

/tms/transloads/scheduled-inquiry-email accepts POST and is declared in app/systems/TMS/transload/api_routes.php:589 as a path.

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

Call chain:

→ tmsTransloadApiSendScheduledInquiryEmail() — app/systems/TMS/transload/communication_api_helper.php:2
↳ tmsTransloadApiNormalizeCompanyLookupKey() — app/systems/TMS/transload/communication_api_helper.php:227

Who calls it¶

Called from:

public/assets/js/modules/shared/kj-table-options-export.js

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

Input¶

Where	Key
`body`	`IDS`
`body`	`ids`

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.

SQL executed¶

SELECT T.ID,

Data¶

Tables reached from the owner function:

T_COMPANY
T_TRANSLOAD

Access¶

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

Validation and failure messages¶

Please select scheduled loads to email.

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.

POST /tms/transloads/scheduled-inquiry-email¶