Skip to content

GET /yms/fleet-management/dashboard

YMS > yms.container-tracking

What it does

/yms/fleet-management/dashboard accepts GET and is declared in app/systems/YMS/container-tracking/api_routes.php:1880 as a path.

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

Call chain:

  1. → ymsFleetApiDashboard() — app/systems/YMS/container-tracking/api_routes.php:1306
  2. ↳ ymsFleetApiAssertSchema() — app/systems/YMS/container-tracking/api_routes.php:683

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 COUNT(*) FROM information_schema.TABLES

Data

No table reference is visible in the owner function body.

Access

  • module-gated on yms.container-tracking, so tenant module access applies

Validation and failure messages

  • Equipment activity schema is not installed. Run the fleet management migration first.
  • Equipment activity table is not installed. Run the fleet management migration first.

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.