Skip to content
LogoLogo

Create Transfer

Submit a value-movement intent. The same endpoint handles same-chain transfers, same-chain swaps, and cross-chain bridges. Mure infers the operation type from the request:

  • transfer — same chain, same asset.
  • swap — same chain, different input and output assets.
  • bridge — different source and destination chains.
  • batch — more than one value movement in one request. The root carries the order-level members, and transfers carries one entry per movement.
POST /transfers

Request Body

FieldTypeRequiredDescription
fromCAIP-10YesSource account and chain (eip155:{chainId}:{address}).
toCAIP-10YesDestination account and chain.
assetCAIP-10 | { in: CAIP-10, out: CAIP-10 }YesToken to move. Use { in, out } for swaps.
amountstringYesAmount in the token's base units, as an integer string.
deadlinestringNoLatest execution time (ISO 8601). Defaults to +1 hour.
callDatastringNoHex-encoded calldata forwarded to the recipient output. Max 10,240 bytes.
optionsobjectNoPer-request options. See Options.

Options

Every field is optional. Omit options to take the defaults.

OptionTypeDescription
simulatebooleanCheck the transfer against the current chain state before answering. Defaults to false. See Simulation.
slippageBpsintegerExact-input slippage floor for a same-chain swap, in basis points. Defaults to 50. Ignored by transfers, bridges, and exact-output swaps.
protocols.includestring[]Narrow a swap or bridge to these served protocols.
protocols.excludestring[]Remove these served protocols; applied after include.
{
  "from": "eip155:11155111:0x3165...",
  "to": "eip155:11155111:0x8f66...",
  "asset": "eip155:11155111:0xA0b8...",
  "amount": "1000000"
}

Quote metadata

A request that routes to the quote service carries the quote projection flat on metadata. A plain same-chain transfer, and any request served by the legacy path, carries none of these fields.

FieldTypeDescription
providerstringThe protocol that produced the winning quote: across, cow, mayan, relay, sushiswap, or uniswap.
routearrayThe described path, in order. Each hop is { chainId, tokenIn, tokenOut, venue? }; a multi-hop swap is more entries.
costsobjectThe normalized quote costs: total in micro-USD, a non-empty sources list, and outputUsd.
inobjectThe input side: { chainId, amount?, expectedAmount?, minAmount? }.
outobjectThe output side, the same shape.
slippageBpsintegerThe settlement band the composer committed, in bps. minAmount derives from it.

For an exact-input request, in.amount is the amount you sent, and out carries expectedAmount and minAmount. For an exact-output request the sides swap: out.amount is the amount you pinned, and in carries expectedAmount and minAmount. minAmount is expectedAmount minus the committed band (slippageBps), so it is the floor the order can settle at.

Amounts are base-unit integer strings, like amount; costs.total is in micro-USD (1 unit = 1e-6 USD).

Batch requests

A batch request moves value to more than one place in one order. Put the order-level members at the root and the movements in transfers:

FieldTypeRequiredDescription
deadlinestringNoLatest execution time for the whole order (ISO 8601). Defaults to +1 hour.
options.simulatebooleanNoCheck the whole order against current chain state before answering.
transfersarrayYes1 to 25 movements. Each entry takes from, to, asset, amount, callData, and the two per-transfer options.

Each entry spends from the same account on the same source chain; a request that names two payers, or a from that disagrees with its input asset's chain, answers a 422 that names the entry.

Response Fields

FieldTypeDescription
idstringUnique intent ID (int_transfer_{ulid}).
typestringInferred operation type: transfer, swap, bridge, or batch. A request with more than one transfer answers batch.
statusstringLifecycle status. See Intent Lifecycle.
orderIdstringDeterministic on-chain order identifier (bytes32 hex).
createdAtstringISO 8601 creation timestamp.
updatedAtstringISO 8601 last update timestamp.
metadataobjectChain ID, gas estimate, optional transaction details, and — when the request routed to the quote service — the quote projection. See Quote metadata. Always carries metadata.transfers.
metadata.transfersarrayOne record per transfer, in request order. Each record carries that transfer's own type (transfer, swap, or bridge), its recipient and token (CAIP-10), its delivered amount, and its settled outputHash. A record carries no index: array order is the position. A one-transfer response also carries the quote members flat on metadata; a multi-transfer response does not.
txobjectTransaction payload ready for on-chain submission.

Errors

HTTPTypeWhen
400bad-requestMalformed JSON or a payload that fails schema validation.
400empty-protocol-setThe protocol filter removed every protocol the request could use.
400simulation-failedoptions.simulate was set and the transfer reverted against the current chain state.
401missing-api-keyNo api-key header.
403invalid-api-keyInvalid API key.
403chain-not-allowed-for-key-environmentThe key's environment cannot act on the requested chain.
422validation-failedDomain validation failure such as an unknown asset symbol.
422exact-output-requires-quoteAn exact-output swap was requested while the swap quote service is unavailable.
422exact-output-unsupportedAn exact-output swap targets a chain whose route settles through the DeFi adapter lane.
429rate-limitedRate limit exceeded.
500transfer-service-failureUnexpected transfer service error.