> ## Documentation Index
> Fetch the complete documentation index at: https://docs.trustware.io/llms.txt
> Use this file to discover all available pages before exploring further.

# GET /transactions

> List your project's most recent transactions sent from a wallet address.

`GET https://api.trustware.io/api/v1/data/transactions/:address`

Returns up to 100 of your project's transactions sent from a wallet address, newest first. Each item is the transaction payload [`GET /status`](https://docs.trustware.io/api-reference/status#response-fields) returns for a committed route intent. Use it to show a wallet's history, or to find the `intent_id` of a payment you didn't store.

Only committed transactions are listed. A route intent with no committed transaction isn't, so read it with [`GET /status`](https://docs.trustware.io/api-reference/status). Items are transactions, not route intents, so two items can share an `intent_id`.

The endpoint only reads your own project's transactions, the ones made with SDK keys from the same project as the key you call it with.

## Path parameters

| Parameter | Description |
| - | - |
| `address` | The wallet address. A transaction matches when its `from_address` or its `origin_eoa` is this address, ignoring case. |

## Response

```json theme={null}
{
  "data": [
    {
      "id": "bc5a5e82-1ecb-453b-bf78-c7c3ccdc3223",
      "intent_id": "d9a10f42-7243-498d-914a-269a18b93660",
      "project_id": "6f1d2c3b-4a5e-4f60-8172-93a4b5c6d7e8",
      "sdk_request": false,
      "from_address": "0xeb212fe20f26243ec4d4df2dd49c8aa9fa75a201",
      "to_address": "0xeb212fe20f26243ec4d4df2dd49c8aa9fa75a201",
      "sender_verification": "verified",
      "from_chain_id": "43114",
      "to_chain_id": "137",
      "source_tx_hash": "0x4c8f91363c5f5e3ac2154f94995f5beac2993cc595af552c2681538af627e05d",
      "dest_tx_hash": "0x9b7e3f0a...",
      "request_id": "3f2504e0-4f89-41d3-9a0c-0305e82c3301",
      "provider_request_id": "eeaa53a4f2e254896ae690edac309e68",
      "transaction_request": {
        "to": "0xce16f69375520ab01377ce7b88f5ba8c48f8d666",
        "data": "0x846a1bc6...",
        "value": "215124226346059100"
      },
      "status": "success",
      "routing_provider": "squid",
      "quote_to_amount_usd": "0.19000000",
      "to_amount_wei": "198584",
      "landed_amount_verified": true,
      "refunded": false,
      "poll_attempt": 0,
      "create_date": "2026-04-15T03:13:22.592483Z",
      "update_date": "2026-04-15T03:14:41.103927Z",
      "gas_sponsored": false
    }
  ]
}
```

`data` is an array of transaction payloads, with the fields described in [`GET /status`](https://docs.trustware.io/api-reference/status#response-fields). Items don't carry `steps`. Read `/status` for an intent's execution steps.

When no transaction matches, the response is `200` with `"data": []`. An address that has never paid and an address only another project has seen give the same answer.

## Errors

| HTTP | `error` | Meaning |
| - | - | - |
| `403` | `api key does not have the required scope` | The key lacks the `data` scope, which keys have by default. The body also carries `"required_scope": "data"`. |
| `500` | `failed to load transactions` | Trustware couldn't read the transactions. Retry with backoff. It never means the address has no transactions. |

Each call counts against your key's [rate limit](https://docs.trustware.io/api-reference/overview.md#rate-limits).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.