Skip to content

GET /tms/bookings/drayage-empty-options

TMS > tms.booking

What it does

/tms/bookings/drayage-empty-options accepts GET and is declared in app/systems/TMS/booking/api_routes.php:1570 as a path.

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

Call chain:

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

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

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 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