Skip to main content
Reimbursement List API

Authentication

All requests require an API key in the request headers. Headers:

Request

Query Parameters

Code Examples

Success Response

HTTP Status: 200 OK Response Fields:

Reimbursement State Values

Response Example

Error Responses

Authentication and permission failures are returned in the standard structured format shown below. Business-logic errors (such as access being denied) are returned with an HTTP 200 OK status and a string error message: { "ok": false, "error": "<message>" }.

Access Denied

HTTP Status: 200 OK

Validation Error

HTTP Status: 400 Bad Request

Authentication Errors

HTTP Status: 401 Unauthorized

Permission Errors

HTTP Status: 403 Forbidden

Best Practices

  • Use cursor and limit together to paginate; pass the nextCursor from the response as the cursor value for the next call
  • startDate and endDate are interpreted against the column specified by dateType — change dateType to filter by payment, created, or approval date instead of the reimbursement date
  • Use the id from the response as the input to the Reimbursement Details API for full reimbursement information
  • Always check the ok flag in the response body in addition to the HTTP status code, since business-logic errors are returned with an HTTP 200 OK status
  • Access is limited to users with reimbursement read permission and an admin or bookkeeper role