Movement Report

Use the Movement Report to reconcile activity for specific audit periods, remediate reconciliation breaks, and satisfy tax reporting requirements. Each row represents one transfer. Transaction-level fields repeat across the rows that belong to the same transaction.

To generate a Movement Report, you need the following:

POST /v1/exports/movement

The service generates a transaction history for the target domain within the date range you specify.

Send the request body as application/json.

By default, the Movement Report includes only settled transactions—those with a custody status of Completed and a ledger status of Confirmed. This default is designed for reconciliation, where you want only finalized activity.

To include other statuses, pass the full set of values you want:

curl -X POST "https://{host}/v1/exports/movement" \
  -H "Authorization: Bearer <jwt>" \
  -H "Content-Type: application/json" \
  -d '{
    "domainId": "a1b2c3d4-e5f6-7890-abcd-ef1234567890",
    "dateRange": {
      "start": "2026-06-01T00:00:00Z",
      "end": "2026-06-15T23:59:59Z"
    },
    "includeChildDomains": false,
    "custodyStatus": ["Completed"],
    "ledgerStatus": ["Confirmed"],
    "format": "CSV"
  }'

The response is returned as a single file with a Content-Disposition attachment header and an X-Export-Id header for tracing. For the response structure of each format, see Output formats.

Each row represents one transfer. Column order is a fixed contract. The report-level domainId and domainName come from your request. The per-transfer senderDomainId and recipientDomainId identify the domains of the counterparties.

The report includes both a converted and a raw value for each transfer:

• enrichedTransactionValue is the human-readable decimal value in the asset's native unit, such as 1.5 XRP. Use this for reconciliation and reporting.
• rawTransactionValue is the raw ledger-native value in the smallest denomination, such as 1500000 drops. The service doesn't convert it to decimal.

Both are strings. Always parse them as strings. See Financial precision.

Network fees appear as their own rows with a transferKind of Fee. The report doesn't link a fee row to the transfer that incurred it — if your reconciliation needs fees attributed to specific transfers, match them downstream using the transactionId or onLedgerTransactionId columns.

When a transfer has multiple senders—for example, on UTXO-model chains—the service separates all sender-side fields with a pipe (|) within the cell, in a consistent order across every sender field. This lets you align the sender attributes positionally.

When a sender or recipient is off-platform, the service uses a consistent external convention: the counterparty's ...VaultType is external, its ...DomainId and ID fields are empty, and its ...Internal flag is false.

The metadata header includes the following control total, a sum across every row in the report. Use it to verify that your ingested file is complete and uncorrupted. For how to verify, see Control totals.

If the service returns an error, the response body is a client-safe JSON object and never exposes internal details. Common cases for the Movement Report include:

• 400: A required field is missing, a UUID or timestamp is malformed, dateRange.end is before start, the range exceeds 30 days, a status array is empty, or a filter array exceeds 1,000 entries.
• 401: The JWT is missing or invalid.
• 403: You lack access to the target domain.
• 413: The request scope exceeds a report limit — either more than 100 accessible domains, or a result that would exceed 100,000 transfers.
• 429: A duplicate request within 60 seconds while a previous export is still processing, or you already have 2 exports processing.

For the full list, see Error responses.