GET /tms/bookings/options

TMS > tms.booking

What it does

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

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

Call chain:

1. → booking_editor_options() — app/systems/TMS/booking/query_helper.php:85
2. ↳ tenant_mk_document_workflow_enabled() — app/platform/tenant/config_helper.php:751
3. ↳ tenant_config_get_bool() — app/platform/tenant/config_helper.php:730

Who calls it

Called from:

• new-system/apps/web/src/composition/pages/booking/bookingClient.ts
• 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

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

Key
BOOKING_TYPES
CLIENT_ID
COMPANIES
DESTINATIONS
INSPECTORS
INSTRUCTION_ENABLED
LABEL_OPTIONS
MK_DOCUMENT_WORKFLOW_ENABLED
SALES_ORDERS
SEAL_TYPES

Success is { "data": …, "requestId": "…" }. Failure is { "error": { "code", "message" }, "requestId": "…" }.

SQL executed

SELECT CATEGORY, KEY1, VALUE1

SELECT

Data

Tables reached from the owner function:

• T_COMPANY
• T_LOAD
• T_MASTER

Access

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