Skip to content

POST /tms/staff-time/manager-sync

TMS > tms.transload

What it does

/tms/staff-time/manager-sync accepts POST and is declared in app/systems/TMS/staff-time/api_routes.php:632 as a path.

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

Call chain:

  1. → tmsStaffTimeManagerSync() — app/systems/TMS/staff-time/api_routes.php:355
  2. ↳ staff_time_assert_can_manage() — app/systems/TMS/staff-time/staff_time_helper.php:220
  3. ↳ staff_time_can_manage() — app/systems/TMS/staff-time/staff_time_helper.php:212

Who calls it

Called from:

  • frontend/pages/system/TMS/transload/loader-analysis.php
  • frontend/pages/system/TMS/transload/loader-timeline.php

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

Input

Where Key
body CHANGES
body changes

Request bodies must not use TYPE, ACTION or USERNAME as contract fields.

Output

Key
COUNT
STATUS

Success is { "data": …, "requestId": "…" }. Failure is { "error": { "code", "message" }, "requestId": "…" }.

Data

No table reference is visible in the owner function body.

Access

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

Validation and failure messages

  • QuickBooks sync changes are invalid.
  • Manager permission is 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.