Get Expense
/users/{user_id}/expenses/{expense_id}Retrieves a single expense with full detail including adjudication, enrichment, merchant, and origin data.
Path Parameters
The Sail user id.
The Sail expense id.
Response
Expense details.
The Sail expense id.
The connection this expense was sourced from.
Echo of the customer-supplied id for expenses ingested through an external connection; null for Sail-sourced expenses. Join key back to the customer’s own transaction store.
The expense’s display name.
Human-readable description of the expense.
The transaction date.
USD.
The expense’s current workflow status.
How this expense entered Sail; pairs with the source_type list filter.
What the expense was derived from.
The merchant this expense was incurred at, as resolved by enrichment. supported_merchant_id references the /merchants directory only when the merchant is one Sail can connect to for store data; it is null for the long tail of merchants that are recognized but not scrape-supported.
General transaction enrichment, independent of Section 213(d) adjudication.
Set when this expense is a line item split from another expense (e.g. itemization of a mixed-basket transaction after receipt review); null for top-level expenses.
Section 213(d) eligibility adjudication. The review states pair with origin.type: lmn_required applies to product-origin expenses (a dual-purpose item that becomes eligible with a Letter of Medical Necessity); itemization_required applies to transaction-origin expenses (a mixed basket that needs an itemized receipt before line items can be adjudicated). Both surface as needs_review in the top-level workflow status.
When the expense was created.
When the expense was last updated.
Standard error envelope covering 400, 401, 403, 404, 429, and 500.
The error detail.