---
title: "Retrieve a list of expenses"
method: GET
path: "/expenses"
tags: ["Expenses"]
---

# Retrieve a list of expenses

`GET /expenses`

## Request

- Base URL: `https://b2b.revolut.com/api/1.0`
- URL: `https://b2b.revolut.com/api/1.0/expenses`
- Auth: HTTP bearer

Get all your expenses, or use the query parameters to filter the results.

The expenses are sorted by the `expense_date` value in reverse chronological order, and they're **paginated**.
The maximum number of expenses returned per page is specified by the `count` parameter.
To get the next page of results, make a new request and use the `expense_date` value from the last item of the previous page as the value for the `to` parameter.

The data enriched by the user, for example, VAT and cost centre, is returned under `splits[].tax_rate` and `splits[].labels`, respectively.

:::note
- The API returns a maximum of 500 expenses per request.
- This feature is not available in Sandbox.
:::

For more information, see the guides: [Retrieve expenses and receipts](https://developer.revolut.com/docs/guides/manage-accounts/accounts-and-transactions/retrieve-expenses).

## Query parameters

- `from` string, date-time
- `to` string, date-time
- `count` integer
- `state` 'missing_info' | 'awaiting_review' | 'reverted' | 'pending_reimbursement' | 'refund_requested' | 'refunded' | 'approved' | 'rejected'
- `transaction_type` 'atm' | 'card_payment' | 'fee' | 'transfer' | 'external' | 'mileage_reimbursement' | 'rev_payment'

## Response `200`

List of expenses

- Expense[]
  - `id` string, uuid, required: The ID of the expense.
  - `state` 'missing_info' | 'awaiting_review' | 'rejected' | 'pending_reimbursement' | 'refund_requested' | 'refunded' | 'approved' | 'reverted', required: Indicates the state of the expense. Possible values: | Value | Description | | --- | --- | | **`missing_info`** | The expense is missing some required information. This is the initial state of the expense when it's first created. Once the missing information is provided, the expense is ready to be submitted. | | **`awaiting_review`** | The expense is awaiting approval before it can be completed. The approver can approve, reject, or request repayment for the expense. It is also possible for the submitter to undo the submission at this stage. | | **`rejected`** | The expense has been rejected by the approver. The expense submitter (typically, the payer) should fix the issue that was the reason for the rejection and resubmit the expense. | | **`pending_reimbursement`** | The reimbursement request has been approved, and the expense is awaiting reimbursement. This state is possible for reimbursements (transaction type = `External`). | | **`refund_requested`** | The expense has been rejected and repayment has been requested.* This state is possible for card transactions. It indicates that following the review, the approver rejected the expense and requested that it be paid back to the business account. This can happen, for example, if an employee accidentally makes a personal purchase with their business card. Once the money has been returned, the **admin** can mark this expense as repaid. | | **`refunded`** | The expense has been repaid.* This state indicates that the admin has marked the expense as repaid. | | **`approved`** | The expense has been approved and is now completed.* | | **`reverted`** | The expense has been reverted. This status indicates that the transaction related to the expense has been reverted. In such a case, the expense status is automatically set to `reverted`, and the expense is completed. This can happen, for example, when the transaction has been reverted by the merchant. | _*Additionally, if an admin has previously approved the expense, marked it as repaid/completed, or requested repayment, they can revert their decision. In such a case, the expense goes back to the initial `missing_info` state._ For more information, see the guides: [Retrieve expenses and receipts](https://developer.revolut.com/docs/guides/manage-accounts/accounts-and-transactions/retrieve-expenses#expense-state).
  - `transaction_type` 'atm' | 'card_payment' | 'fee' | 'transfer' | 'external' | 'mileage_reimbursement' | 'rev_payment', required: The type of the [transaction](https://developer.revolut.com/docs/api/business#get-transaction) related to the expense.
  - `description` string: The description of the expense.
  - `submitted_at` string, date-time: The date and time the expense was submitted in [ISO 8601](https://en.wikipedia.org/wiki/ISO_8601) format.
  - `completed_at` string, date-time: The date and time the expense was completed in [ISO 8601](https://en.wikipedia.org/wiki/ISO_8601) format.
  - `payer` string: The name of the [team member](https://developer.revolut.com/docs/api/business#delete-team-member) who made the transaction, refund request, or ATM withdrawal, or the name of the business if the related transaction is of type `fee`.
  - `merchant` string: The name of the merchant.
  - `transaction_id` string, uuid: The ID of the [transaction](https://developer.revolut.com/docs/api/business#get-transaction) related to the expense. Not available for transactions of type `external`.
  - `expense_date` string, date-time, required: The expense data depends on the type of the expense and whether it has been completed. Typically, it's the date and time of the expense [transaction](https://developer.revolut.com/docs/api/business#get-transaction) in [ISO 8601](https://en.wikipedia.org/wiki/ISO_8601) format. - If the transaction related to the expense is completed, it is the date and time of its completion ([`completed_at`](https://developer.revolut.com/docs/api/business#get-transaction#response)). - Otherwise, it is the date and time of its creation ([`created_at`](https://developer.revolut.com/docs/api/business#get-transaction#response)). For reimbursements, it's the payment date provided in the reimbursement request.
  - `labels` object, required: :::warning [Deprecated] This field is deprecated. Labels are now assigned per split and returned in `splits[].labels`. During the deprecation period, this field is still returned for backwards compatibility, and the labels are filled as follows: - For expenses created before the migration, the expense-level label is copied to all splits of the expense. - For new expenses, the labels are set at the split level, and the expense-level label is populated with the label from the first split. This field will be removed in a future release. ::: The [labels](https://developer.revolut.com/docs/api/business#delete-label) added to the expense, organised in groups. You can have up to 5 label groups, with max. 1 label per group. The labels are provided as an object, where each key is the name of a label group, and each value is a single-element array containing the selected label from that group. This field is always returned, but it can be an empty object (`{}`) if no label is assigned.
  - `splits` ExpenseSplit[], required: The splits of the expense. A single expense can be divided into multiple parts (splits), for example, to allocate different portions of the expense to different categories.
    - `amount` object, required: The original amount of the expense split.
      - `amount` number, double: The amount of money.
      - `currency` string: [ISO 4217](https://en.wikipedia.org/wiki/ISO_4217) currency code in upper case.
    - `category` Category, required: The [accounting category](https://developer.revolut.com/docs/api/business#delete-accounting-category) of the expense split.
      - `id` string, uuid, required: The ID of the accounting category.
      - `name` string, required: The name of the accounting category.
      - `code` string: The code of the accounting category.
    - `labels` object, required: :::note This field replaces the expense-level `labels` field, which is now deprecated. During the deprecation period, the labels are filled as follows: - For expenses created before the migration, the expense-level label is copied to all splits of the expense. - For new expenses, the labels are set at the split level, and the expense-level label is populated with the first label from the first split. ::: The [labels](https://developer.revolut.com/docs/api/business#delete-label) assigned to the split, organised in groups. You can have up to 5 label groups, with max. 1 label per group. Each split can have a different set of labels. The labels are provided as an object, where each key is the name of a label group, and each value is a single-element array containing the selected label from that group. This field is always returned, but it can be an empty object (`{}`) when the split has no labels.
    - `tax_rate` TaxRate, required: The [tax rate](https://developer.revolut.com/docs/api/business#delete-tax-rate) applied to the expense split.
      - `id` string, uuid, required: The ID of the tax rate.
      - `name` string, required: The name of the tax.
      - `percentage` number, double: The tax rate percentage applied to the taxable amount. For example, `23` for 23%.
  - `receipt_ids` string[], required: The IDs of the receipts related to the expense.
  - `spent_amount` object, required: The expense amount in billed currency. If the expense involves FX, this currency can differ from the currency of the splits.
    - `amount` number, double, required: The amount of money.
    - `currency` string, required: [ISO 4217](https://en.wikipedia.org/wiki/ISO_4217) currency code in upper case.

## Other responses

- `400`: Bad request
- `403`: Forbidden Returned, for example, when the Expenses API is disabled for the business that is trying to use it.
- `422`: Unprocessable content Returned, for example, when the Expenses feature (not just the API) is disabled for the business.
- `default`: Unexpected error

---

[API](https://skmtc.dev/revolut/apis/business-api.md) - [All operations](https://skmtc.dev/revolut/apis/business-api/llms.txt) - [OpenAPI document](https://skmtc.dev/revolut/apis/business-api/revisions/be089d9fa8b4?raw)