Skip to content

GET /tms/bookings/sales-orders

TMS > tms.booking

What it does

/tms/bookings/sales-orders accepts GET and is declared in app/systems/TMS/booking/api_routes.php:1596 as a path.

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

Call chain:

  1. → booking_sales_order_options() — app/systems/TMS/booking/query_helper.php:221
  2. ↳ booking_sales_order_summary_select_sql() — app/systems/TMS/booking/query_helper.php:7

Who calls it

Called from:

  • public/assets/js/modules/shared/booking-editor.js
  • public/assets/js/modules/shared/mk-booking-editor.js

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

Input

Where Key
body ID
body Q
body QUERY
body id
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.

Data

Tables reached from the owner function:

  • T_LOAD

Access

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