Skip to content

GET /oms/outbound-orders

OMS > oms.outbound-order

What it does

/oms/outbound-orders accepts GET and is declared in app/systems/OMS/outbound-order/api_routes.php:20 as a path.

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

Call chain:

  1. → omsOutboundOrderQueryHandle() — app/systems/OMS/outbound-order/query_handler.php:5
  2. ↳ sales_order_options() — app/systems/OMS/outbound-order/outbound_order_query_helper.php:93
  3. ↳ commercial_order_options_for_type() — app/systems/OMS/inbound-order/query_helper.php:66

Who calls it

Called from:

  • app/platform/api_catalog.php
  • frontend/pages/system/OMS/outbound-order/mk-order-schedule.php
  • frontend/pages/system/OMS/outbound-order/mk-outbound-orders.php
  • public/assets/js/modules/shared/mk-outbound-order-editor.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

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

No table reference is visible in the owner function body.

Access

  • module-gated on oms.outbound-order, so tenant module access applies