Skip to content

POST /yms/apmt-appointments/create

YMS > yms.container-tracking

What it does

/yms/apmt-appointments/create accepts POST and is declared in app/systems/YMS/container-tracking/api_routes.php:1826 as a path.

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

Call chain:

  1. → ymsContainerApiApmAppointmentCreate() — app/systems/YMS/container-tracking/api_routes.php:272
  2. ↳ ymsContainerBody() — app/systems/YMS/container-tracking/api_routes.php:26

Who calls it

Called from:

  • public/assets/js/modules/tms/export-dispatch.js
  • public/assets/js/modules/tms/import-dispatch.js

A caller is the strongest available evidence of the intended use.

Input

Where Key
body DATE
body SLOT_TIME
body date
body slotTime

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 yms.container-tracking, so tenant module access applies

Validation and failure messages

  • Appointment date and slot are required.

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.