Skip to content

GET /tms/bookings/search

TMS > tms.booking

What it does

/tms/bookings/search accepts GET and is declared in app/systems/TMS/booking/api_routes.php:1562 as a path.

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

Call chain:

  1. → tmsBookingApiSearch() — app/systems/TMS/booking/api_routes.php:471
  2. ↳ tmsBookingApiLookupLimit() — app/systems/TMS/booking/api_routes.php:439

Who calls it

Called from:

  • public/assets/js/modules/shared/container-edit-modal.js
  • public/assets/js/modules/shared/mk-outbound-order-editor.js
  • public/assets/js/modules/tms/loading-planner-modal.js
  • public/assets/js/modules/yms/scale-portal.js

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

Input

Where Key
body ID
body Q
body QUERY
body SHIPPING_LINE
body SIZE

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

Data

Tables reached from the owner function:

  • T_BOOKING
  • T_COMPANY

Access

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

Validation and failure messages

  • Street turn booking filters require a shipping line and supported size.

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.