Skip to content

GET /tms/transloads/unloading-equipment/options

TMS > tms.transload

What it does

/tms/transloads/unloading-equipment/options accepts GET and is declared in app/systems/TMS/transload/api_routes.php:421 as a path.

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

Call chain:

  1. → tmsTransloadApiUnloadingEquipmentOptions() — app/systems/TMS/transload/planning_query_api_helper.php:974
  2. ↳ tmsTransloadApiLookupLimit() — app/systems/TMS/transload/planning_query_api_helper.php:820

Who calls it

Called from:

  • public/assets/js/modules/tms/loading-planner-modal.js

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

Input

Where Key
body ID
body LOADINGTYPE
body LOADING_TYPE
body Q
body QUERY

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 DISTINCT T.ID AS `key`,

Data

Tables reached from the owner function:

  • T_COMPANY
  • T_TRANSLOAD
  • T_YARD_LOCATION

Access

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