Skip to content

POST,PATCH /bms/transactions/form

BMS > bms.transaction

What it does

/bms/transactions/form accepts POST,PATCH and is declared in app/systems/BMS/transaction/api_routes.php:111 as a path.

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

Call chain:

  1. → bmsTransactionApiFormMutation() — app/systems/BMS/transaction/api_routes.php:92
  2. ↳ apiTableMutationRun() — app/shared/api/table_mutation_helper.php:482
  3. ↳ apiTableMutationNormalize() — app/shared/api/table_mutation_helper.php:6

Who calls it

Called from:

  • public/assets/js/modules/shared/popup.core.js

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

Input

Where Key
query mode

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

Output

Key
T_TRANSACTION
T_TRANSACTION_LIST

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 bms.transaction, so tenant module access applies