DELETE /tms/transload-appointment-blocks

TMS > tms.transload

What it does

/tms/transload-appointment-blocks accepts DELETE and is declared in app/systems/TMS/transload/api_routes.php:619 as a path.

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

Call chain:

1. → tmsTransloadApiBlockWrite() — app/systems/TMS/transload/completion_effect_api_helper.php:143
2. ↳ transload_post_handle_appointment_block() — app/systems/TMS/transload/request_create_helper.php:163

Who calls it

Called from:

• frontend/pages/system/TMS/transload/transload-planner.php

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.

Data

No table reference is visible in the owner function body.

Access

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