GET /bms/transaction-documents/(?P\d+)¶
What it does¶
#^/bms/transaction-documents/(?P<id>\d+)$# accepts GET and is declared in app/systems/BMS/invoice/api_routes.php:18 as a regex pattern.
The route handler delegates to bmsInvoiceQueryHandle(). That function is the owner of
this behaviour; the route entry is only dispatch.
Call chain:
- →
bmsInvoiceQueryHandle()—app/systems/BMS/invoice/query_handler.php:4 - ↳
purchase_local_invoice()—app/addons/reports/query_helper.php:1097
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 |
body |
ID |
body |
ORDER_ID |
body |
TRANSACTION_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.
Data¶
No table reference is visible in the owner function body.
Access¶
- module-gated on
bms.invoice, so tenant module access applies