Skip to content
LogoLogo

List Transfers

List one page of transfer intents for the authenticated account, newest first. Use the type query parameter to filter by inferred operation type, limit to bound the page, and cursor to continue where the previous page stopped.

GET /transfers
GET /transfers?type=bridge
GET /transfers?type=batch&limit=2
GET /transfers?limit=2&cursor=<nextCursor>
GET /transfers?type=swap&totals=true

Query Parameters

ParameterTypeRequiredDescription
typeenumNoFilter by inferred operation type: transfer, swap, bridge, or batch.
limitintegerNoPage size, clamped to 1–200. Defaults to 50. Text that is not an integer answers 400.
cursorstringNoThe nextCursor from the previous page. Must match the filter set: the same type, or none.
totalsbooleanNoReturn the matching count in total. Accepts true or false. Defaults to false.

A multi-transfer intent is reachable only with ?type=batch. A per-transfer filter such as ?type=swap never returns an intent that merely contains a swap: the root value describes the request, not its movements. Because the classification rule runs before the page is read, a type-filtered page is a full page of that type.

Walking the pages

Send the same filters with the previous page's nextCursor until nextCursor is null. Consecutive pages partition the matching set: no row repeats and none is skipped. The page is ordered by created_at descending, with the intent id as the tiebreaker, so rows created in the same second still have one stable order.

cursor=""
while :; do
  page=$(curl -s -H "api-key: $API_KEY" \
    "https://api.mure.app/v2/transfers?limit=50${cursor:+&cursor=$cursor}")
  echo "$page" | jq -r '.items[].id'
  cursor=$(echo "$page" | jq -r '.nextCursor // empty')
  [ -z "$cursor" ] && break
done

Only the caller-chosen filter (type) is bound into the cursor, so limit and totals may change between pages. A cursor minted under another type is refused with invalid-cursor. The cursor is opaque and carries no owner: it can only move the caller's own authorised seek.

No pagination

The endpoint returns every non-deleted transfer for the key in one response, newest first. It accepts no limit, cursor, page, or offset, and there is no cursor in the response. A key that has created thousands of transfers gets all of them in one array.

Filter with type on the server, and filter the rest on the client. If you need a smaller response today, keep a local record of the ids you created rather than listing the whole account.

Response

One object per page. items holds at most limit summaries. total is an integer only when totals=true was sent, on cursor pages too. nextCursor is null on the last page, including a last page that is an exact multiple of limit.

{
  "items": [
    {
      "id": "int_transfer_01HT...",
      "type": "bridge",
      "status": "confirmed",
      "orderId": "0x0000000000000000000000000000000000000000000000000000000000000000",
      "createdAt": "2026-06-05T12:00:00Z",
      "updatedAt": "2026-06-05T12:05:00Z",
      "metadata": {
        "chainId": "eip155:1",
        "hash": "0x...",
        "transfers": [
          {
            "type": "bridge",
            "recipient": "eip155:42161:0x8f66...",
            "token": "eip155:42161:0xFF97...",
            "amount": "1000000",
            "outputHash": "0x..."
          }
        ]
      }
    }
  ],
  "total": null,
  "nextCursor": "eyJ2IjoxLCJyIjoidHJhbnNmZXJzIiwiayI6WzE3NjcyMjU2MDAsImludF90cmFuc2Zlcl8wMUhORzdUUVlZN1gzSzhLUUMzQjBYOFpRMiJdLCJmIjp7fX0"
}

Response Fields

FieldTypeDescription
itemsTransferSummary[]This page's summaries, newest first.
totalinteger | nullThe caller's matching rows; a number only when totals=true, null otherwise.
nextCursorstring | nullThe continuation to the next page, or null on the last page. Never absent.

Summaries omit the full tx payload to keep responses lightweight. The quote projection (provider, route, in, out) is returned on create only and is not persisted, so a summary never carries it.

FieldTypeDescription
idstringUnique intent ID.
typestringInferred operation type: transfer, swap, bridge, or batch.
metadata.transfersarrayOne record per transfer, in request order: { type, recipient, token, amount, outputHash }. At summary depth a record carries no band and no quote member. outputHash is present whenever the intent committed one; an intent created before the canonical-output table existed may omit it.
statusstringCurrent lifecycle status. See Intent Lifecycle.
orderIdstringDeterministic on-chain order identifier (bytes32 hex).
createdAtstringISO 8601 creation timestamp.
updatedAtstringISO 8601 last update timestamp.
metadataobjectChain ID and optional transaction hash.

Classification

type is inferred from the stored account and asset data, never from a stored label. The count decides first: an intent with more than one transfer is a batch. Then a bridge extension or cross-chain accounts make a bridge. The remaining same-chain intents are a swap when the assets differ and a transfer when they are equal.

An account's chain must match its own asset's chain: the sender's chain equals its input asset's chain, and the recipient's chain equals its output asset's chain. A row whose chains disagree with its assets is not classifiable.

A row the rule cannot accept appears under no type and on no unfiltered page either, so a page never serves a type its data contradicts. GET /transfers/:id answers 404 for such a row. The API reports each dropped row in the server log on the request that skipped it, with the row's owner, intent id and the rule's own reason, rather than skipping it silently.

Deviations from RFC 9865

TopicWhat this API does
Argument nameThe RFC names this argument count; this API names it limit.
Last pagenextCursor is present and null on the last page; it is never absent.
ExpiryA cursor does not expire and carries no owner; it only repositions the caller's own seek.
Totalstotal is returned only when totals=true, on every page.

Errors

HTTPTypeWhen
400bad-requestA query parameter fails schema validation.
400invalid-cursorThe cursor does not decode, or was minted under a different filter set.
401missing-api-keyNo api-key header.
403invalid-api-keyInvalid API key.
429rate-limitedRate limit exceeded.
500transfer-service-failureUnexpected transfer service error.