Skip to content

POST /tms/transloads/(?P\d+)/bol-email

TMS > tms.transload

What it does

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

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

Call chain:

  1. → tmsTransloadApiSendBolEmail() — app/systems/TMS/transload/communication_api_helper.php:368
  2. ↳ tmsTransloadApiBolFailure() — app/systems/TMS/transload/communication_api_helper.php:285

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

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 ID FROM T_TRANSLOAD WHERE ID = ? AND CLIENT_ID = ? AND DELETED_AT IS NULL LIMIT 1

SELECT GROUP_CONCAT(DISTINCT CE.EMAIL_ADDRESS, ',') AS EMAIL_ADDRESS

SELECT BILLING_COMPANY_ID, REFERENCE_NUMBER, SCALE_TICKET_ID

UPDATE T_TRANSLOAD SET BOL_LAST_SENT_AT = NOW(),

Data

Tables reached from the owner function:

  • T_COMPANY_EMAIL
  • T_MASTER
  • T_TRANSLOAD

Access

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