Skip to main content
Payment Request List API

Authentication

All requests require an API key in the request headers. Headers:
The permission required on your API key is Payment Request with the Read action enabled.
In addition to the API key permission, the user the API key belongs to must have an admin or bookkeeper role in the organization. Any other role gets a 403 ACCESS_DENIED — see Error Responses.

Request

Query Parameters

Unknown query parameters are rejected rather than ignored — sending anything other than the four parameters above returns a 400 VALIDATION_ERROR.

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 returns 200 with an empty array, not an error:

Error Responses

Validation Errors

HTTP Status: 400 Bad Request Missing a required query parameter:
Unsupported type or status value:
limit outside the allowed range:
An unrecognised query parameter:

Access Denied

HTTP Status: 403 Forbidden

Authentication Errors

HTTP Status: 401 Unauthorized

Permission Errors

HTTP Status: 403 Forbidden

Best Practices

  • Send limit=100 when syncing in bulk to minimise round trips, and keep it constant for every page of that traversal
  • Drive pagination off context.hasMore rather than comparing count to limit — 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 review view to find requests awaiting action, and history for reconciliation of completed ones