Skip to content

GET /yms/fleet-management/assets/(?P\d+)

YMS > yms.container-tracking

What it does

#^/yms/fleet-management/assets/(?P<id>\d+)$# accepts GET and is declared in app/systems/YMS/container-tracking/api_routes.php:1904 as a regex pattern.

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

Call chain:

  1. → ymsFleetApiAssetDetail() — app/systems/YMS/container-tracking/api_routes.php:1381
  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

Where Key
path 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.

SQL executed

SELECT ID,

SELECT COUNT(*) FROM information_schema.TABLES

Data

Tables reached from the owner function:

  • T_EQUIPMENT_INFORMATION

Access

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

Validation and failure messages

  • Equipment id is required.
  • Equipment not found.
  • 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.