---
title: expenses.list | Doing Work API
description: Expenses on a job, or across the shop between dates, with totals by category. Owner and office see every expense; a field worker sees the ones they entered
url: https://doingwork.work/docs/reference/expenses-list/
---

# expenses.list

Expenses on a job, or across the shop between dates, with totals by category. Owner and office see every expense; a field worker sees the ones they entered.

|  |  |
|---|---|
| Who | Agents can call this |
| REST | `GET /v1/expenses` |
| MCP tool | `expenses_list` |
| Writes | no |
| Area | [Costs, expenses and reports](https://doingwork.work/docs/reference/#costs-expenses-and-reports) |

## When to use it

Expenses on a job, or across the shop between dates, with totals by category. Owner and office see every expense; a field worker sees the ones they entered.

## What to tell the owner

Tell them what you found in plain words. Don't read back raw fields.

## Input

| Field | Type | Required |
|---|---|---|
| `job_id` | string (uuid) | no |
| `shop_id` | string (uuid) | no |
| `from` | string | no |
| `to` | string | no |
| `category` | string (one of materials, equipment, subcontractor, permit, fuel, disposal, other) | no |

## Example

```http
GET https://doingwork.work/v1/expenses?job_id=00000000-0000-4000-8000-000000000000&shop_id=00000000-0000-4000-8000-000000000000&from=...&to=...&category=materials
```

## Output

JSON. The response shape isn't published yet; read the fields you need and ignore the rest. Errors are `{code, message, status}`.

## Errors

| Code | Status | What to do |
|---|---|---|
| `invalid_input`, `invalid_token`, `rate_limited` |  | Can happen on any call. See [errors](https://doingwork.work/docs/errors/). |