Requisition orders
List visible requisition IDs
/a/RequisitionOrders_list
Discover active requisition headers within the caller’s record boundary.
When to use this endpoint
Use for a small unpaged ID discovery pass, then fetch known IDs through RequisitionOrder_get or mapped details. Use getDataTable for a paged list.
Authentication and permissions
Authenticate with signed API-key fields or a logged-in CRM session. Session requests use dispatcher CSRF protection when configured. API keys use their owner’s identity.
The dispatcher requires explicit View on Requisition Order or Requisition Orders, even without a TeamAccess policy. API keys retain their owner’s permissions. Records are filtered to active headers within RequisitionOrder_scopeSQL: configured TeamAccess, or the legacy department boundary, including the owner exception for unlinked requisitions in the TeamAccess policy.
Parameters
This endpoint has no operation-specific parameters.
Example request
$result = FM_api('RequisitionOrders_list');Example response
[
{
"id": "312"
}
]Errors and unusual responses
| Response | Condition |
|---|---|
{"error":"not logged in"} | No authenticated tenant context is available. Invalid signed credentials can be rejected by the dispatcher before the handler runs. |
{"error": "permission denied"} | The dispatcher denies the required View right. |
{"error":"permission denied"} | The required page permission is missing. Hidden/deleted records are omitted from collections; explicit parent readers reject an inaccessible parent. |
Legacy application errors may be returned with HTTP 200. Check the decoded response for error, not only the HTTP status.
Behaviour and edge cases
- Returns a bare array of id objects. Filters deleted=0 and RequisitionOrder_scopeSQL; no received/status condition is applied, so Open, Approved, Processed, Received and Cancelled records can appear.
- No ordering, pagination, counts, date filter or result cap. Extra fields/start/length controls are ignored. TeamAccess permits an unlinked requisition assigned to the current user; the legacy department scope follows Customer/Quote/customer-Job links without that unlinked exception.
Side effects
- Reads tenant data without modifying orders, lines, stock, approval, history or notifications.
See it in Fieldmotion
CRM1
No direct CRM1 literal caller was found in the searched client source. The CRM1 requisition list uses RequisitionOrders_getDT.
CRM2
No direct CRM2 literal caller was found in the searched client source. CRM2 uses RequisitionOrders_getDataTable.
Related endpoints
RequisitionOrders_getDataTable— Read a paged mapped collection.RequisitionOrders_getExportData— Read selected configurable export rows.RequisitionOrder_get— Read one checked requisition.