The API uses bearer authentication and returns { data: ... } or { error: { code, message } }.
The SDK unwraps and validates responses. Lookups belong to the key's customer. Sender,
recipient and refund addresses must be allowlisted. A Robinhood origin refunds only to its
sender: the vault returns a deposit to the wallet that made it, so refundTo must be omitted or
equal senderAddress there.
| Request | Purpose | Creates state? |
|---|---|---|
GET /api/v1/price |
Indicative estimate; only a quote sets minAmountOut |
No; safe to call while typing |
GET /api/v1/quote |
Reserve capacity and persist an intent | Yes; only after explicit customer action |
POST /api/v1/submit |
Relay the original signed deposit | Yes; explicit retries use identical bytes |
GET /api/v1/status/{intentId} |
Read current state | No |
GET /api/v1/status/{intentId}/wait?since=... |
Wait up to 60 seconds for an update | No |
WS /api/v1/stream |
Subscribe using a bearer-authenticated upgrade | No |
GET /api/v1/limits |
Read customer capacity | No |
Use Cache-Control: no-store on your adapter too. Expose quote as an explicit POST in a
browser-facing backend to avoid GET prefetch. Never add automatic quote retries.
parseAmount
and formatAmount support 0–36 decimals and reject overflow or extra precision.native. Symbols are labels.eip155:<chain id> (Robinhood mainnet eip155:4663) and
solana:<first 32 characters of the genesis hash> (mainnet
solana:5eykt4UsFv8P8NJdTREpY1vzqKqZKvdp). Take them from your deployment configuration; the
API refuses any other network, and the v0.3 forms solana:solana and evm:<N>.
EVM addresses compare without case; Solana addresses remain case-sensitive.'0.5', with at most two decimals. The server sets
permitted ranges. Omit it for the server recommendation.intentId is 16 bytes encoded as unpadded base64url. It identifies an intent, not a credential.deadline is Unix seconds. Status timestamps are Unix milliseconds.
lastValidBlockHeight is a Solana block height, not a timestamp.minAmountOut. Origin gas is paid separately.latencyMs is origin-block to destination-block time. Browser measurements can also include
wallet prompts, transport delays and offline time.Keep deposit data unchanged. Solana's memo is opaque and can contain a long versioned
payload; it is not necessarily the intent ID. EVM calldata carries an opaque payload in
depositNative(bytes16,bytes) or depositToken(bytes16,uint256,bytes).
prepareRobinhoodDeposit uses the current ABI and checks economic fields against the quote.
robinhoodDepositTransactions is a compatibility helper that returns calls without verifying
vault identity or calldata.
The HTTP submit handler decodes base64 for Solana and 0x raw bytes for EVM. Relay availability
depends on the deployed runtime's transports. The sample uses Solana relay and EVM wallet
send; an EVM wallet hash cannot be passed to submit as a signed transaction.
A status may carry an optional metrics object (Metrics). metrics.sends (SendMetrics[])
appears only when the operator enables [api] expose_send_lanes for the calling customer
([api] send_lanes_customers): one entry per deposit relay,
fill attempt and refund attempt, with each send lane's label, outcome, failure reason and
latency in microseconds, and the first lane to accept. It is diagnostics, never accounting. A
lane report can wake wait with an unchanged statusSeq; watch and poll yield only state
changes, so read status or wait for the latest metrics. A malformed metrics object is
dropped rather than failing the status. metrics.chainLatency (ChainLatency) is always present
once EasyPath has placed both the deposit and the fill or refund block: raw, shift and aligned
milliseconds, the era, the direction and where each side landed within its second; it stays
provisional until the swap is settled or refunded.
The HTTP reference comes from the shared docs/openapi.yaml. Its owner still needs to
reconcile the memo-only-intent description, the shorter vault ABI without payload, and the
claim that EVM submit is absent from the HTTP handler. These SDK guides describe the current
tested client and sample behavior. Do not reconstruct deposits from the older prose examples.
The runtime remains a development foundation; a generated reference does not enable live routes.