trucking-terminal-appointments¶

TMS > tms.delivery

What it does¶

/tms/trucking-terminal-appointments accepts GET and is declared in app/systems/TMS/trucking-terminal-appointment/api_routes.php:9 as a path.

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

Call chain:

→ tta_terminal_options() — app/systems/TMS/trucking-terminal-appointment/appointment_helper.php:52
↳ company_type_key_by_label() — app/platform/tenant/company_helper.php:3

Who calls it¶

Called from:

public/assets/js/modules/tms/truck-dispatch.js

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¶

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 UUID,COALESCE(NULLIF(DISPLAY_NAME,''),COMPANY_NAME,'') NAME FROM T_COMPANY WHERE CLIENT_ID=? AND DELETED_AT IS NULL AND FIND_IN_SET(?,M_COMPANY_TYPE_IDS)>0 ORDER BY NAME

SELECT KEY1 FROM T_MASTER

Data¶

Tables reached from the owner function:

T_COMPANY

Access¶

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

GET /tms/trucking-terminal-appointments¶