Skip to content

GET /tms/export-empty-plans

TMS > tms.delivery

What it does

/tms/export-empty-plans accepts GET and is declared in app/systems/TMS/export-empty-plan/api_routes.php:7 as a path.

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

Call chain:

  1. → eep_list() — app/systems/TMS/export-empty-plan/export_empty_plan_helper.php:90
  2. ↳ eep_require_ready() — app/systems/TMS/export-empty-plan/export_empty_plan_helper.php:4

Who calls it

Called from:

  • public/assets/js/modules/tms/truck-dispatch.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

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 * FROM T_EXPORT_EMPTY_PLAN WHERE CLIENT_ID=?

Data

Tables reached from the owner function:

  • T_EXPORT_EMPTY_PLAN

Access

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

Validation and failure messages

  • Export Empty Plan schema is not enabled.

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.