# Investigate a transaction

Gather full context before proposing changes.

Use get_transaction to load the transaction row plus all linked notes and receipts in a single call. Prefer that over list_notes to save tool round-trips and tokens.

### `GET /api/v1/transactions/{id}`

Full transaction with linked notes and receipts. Prefer this over list_notes for investigation.

- operationId: `get_transaction`
- scope: `read`

**Parameters**

- `id` (uuid, required) — Transaction ID

**Response**

```json
{
  "data": {
    "transaction": { … },
    "notes": [ { "id": "…", "content": "…", "createdAt": "…" } ],
    "receipts": [ { "id": "…", "fileName": "invoice.pdf", … } ]
  }
}
```

## Related reads

### `GET /api/v1/receipts/search`

Search receipts by file name or OCR text. Returns up to 50 results.

- operationId: `search_receipts`
- scope: `read`

**Parameters**

- `q` (string, required) — Search query

**Response**

```json
{ "data": [ … ], "meta": { "count": 3, "limit": 50 } }
```

Search receipts when you have a vendor name or amount but no linked document yet. list_notes remains available but is redundant with get_transaction for most agents.