Payment Request List API
Payment APIs
Payment Request List API
List payment requests (vendor advances) by review, active, or history view with cursor pagination
Payment Request List API
Authentication
All requests require an API key in the request headers. Headers:Request
Query Parameters
List Views
Results are scoped organization-wide — every matching request in the organization is returned, not just those the API key’s user created.
Pagination
cursor is an opaque offset token. Request the first page without a cursor, then pass the returned context.nextCursor on each subsequent call until context.hasMore is false (at which point nextCursor is null).
Keep
limit stable across pages of the same traversal. The cursor is interpreted relative to the page size, so changing limit mid-traversal can skip or repeat rows.Code Examples
Paginating Through All Pages
JavaScript (Fetch API)
Success Response
HTTP Status:200 OK
Response Fields:
Response Example
Empty Result
A view with no matching requests returns200 with an empty array, not an error:
Error Responses
Validation Errors
HTTP Status:400 Bad Request
Missing a required query parameter:
type or status value:
limit outside the allowed range:
Access Denied
HTTP Status:403 Forbidden
Authentication Errors
HTTP Status:401 Unauthorized
Permission Errors
HTTP Status:403 Forbidden
Best Practices
- Send
limit=100when syncing in bulk to minimise round trips, and keep it constant for every page of that traversal - Drive pagination off
context.hasMorerather than comparingcounttolimit— a short page is not proof that the traversal is finished - This list returns summary rows only; call Payment Request Details for tax breakdown, narration, tags, and the linked purchase order
- Poll the
reviewview to find requests awaiting action, andhistoryfor reconciliation of completed ones