Skip to main content
Expense Details API

Authentication

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

Request

Path Parameters

Code Examples

Success Response

HTTP Status: 200 OK Response Fields:

Response Example

Error Responses

Missing Expense ID

HTTP Status: 400 Bad Request

Expense Not Found

HTTP Status: 404 Not Found

Access Denied

HTTP Status: 403 Forbidden

Authentication Errors

HTTP Status: 401 Unauthorized

Permission Errors

HTTP Status: 403 Forbidden

Internal Error

HTTP Status: 500 Internal Server Error

Best Practices

  • Use the id returned by the Expense List API as the expenseId path parameter
  • amountBreakdown is computed per line item: subTotal excludes transaction tax, grossTotal adds it back, and netPayable subtracts withholding tax
  • merchant.mcc and processingStatus are only present when the underlying data exists — guard for their absence
  • Access is limited to users with expense read permission and an admin or bookkeeper role