Track an order

GetOrder takes the quote hash and returns everything known about it: the quote, the order if one exists, the deposit, and the fulfillment or refund.

const detail = await apsis.getOrder({ quoteHash });

detail.quote;         // always present
detail.order;         // present once the deposit is indexed
detail.deposit;       // the matched source-chain deposit
detail.fulfillment;   // present once a fulfillment is attempted
detail.refund;        // present once a refund is attempted

Between the deposit landing and the indexer seeing it, order is absent. That is normal for the first seconds and is not an error.

Polling

Poll every couple of seconds and stop on a terminal state.

import { isTerminalState, orderOutcome } from "<SDK_PACKAGE>";

const settle = async (quoteHash: string) => {
  for (;;) {
    const { order } = await apsis.getOrder({ quoteHash });
    if (order && isTerminalState(order.state)) {
      return orderOutcome(order.state);   // "fulfilled" | "refunded" | "failed"
    }
    await new Promise((r) => setTimeout(r, 2000));
  }
};

There is no webhook or stream. Polling is the supported pattern; keep the interval at a couple of seconds and it stays well inside rate limits.

What to render

Order state	Show
No order yet	Waiting for the deposit to be seen.
`awaiting_finality`	Confirmation progress, from `src_confirmations` of `required_confirmations`.
`ready_to_fulfill`, `fulfilling`	Settling on the destination chain.
`fulfilled`	Done, with `dst_tx_hash` linked.
`pending_refund`, `refunding`, `awaiting_refund_window`	Refund in progress.
`refunded`	Refunded, with the refund transaction linked.
`refund_skipped`, `deposit_missing`, `refund_failed`, `unsupported_deposit`	Needs support. Say so plainly and show the quote hash.

See Order lifecycle for what each state means.

dst_tx_hash is set when a transaction is submitted, not when it confirms. Only the order state tells you the funds arrived.

Explorer links

GetChains returns URL templates per chain. Substitute the hash or address rather than assembling explorer URLs yourself:

import { explorerTxUrl, explorerAddressUrl } from "<SDK_PACKAGE>";

const chain = chains.find((c) => c.chain === order.dstChain)!;
explorerTxUrl(chain.explorerTxUrl, order.dstTxHash);
explorerAddressUrl(chain.explorerAddressUrl, recipient);

The Apsis explorer page for an order is <EXPLORER_URL>/<quote_hash>.

Finding orders another way

RPC	Input	Returns
`Search`	A quote hash, a source transaction hash, or a destination transaction hash	The single matching order detail
`SearchAddress`	An address	Matching orders, with state and chains
`ListOrders`	An address	A page of full order summaries for that address
`ListRecentOrders`	Nothing	A page of recent protocol-wide orders

Search is what a support box should call: it accepts whichever hash the user has in hand.

const detail = await apsis.search({ query: userInput });

Pagination

Listing RPCs are cursor-paginated. Pass next_cursor from the previous page; an absent cursor means the end.

let cursor: string | undefined;
do {
  const page = await apsis.listOrders({ address, limit: 50n, cursor });
  render(page.items);
  cursor = page.nextCursor;
} while (cursor);

Default page size is and the maximum is ; larger values are clamped rather than rejected. Cursors are opaque — do not parse or construct them.

Get started

Build a swap

Extend

Track an order

Polling

What to render

Explorer links

Finding orders another way

​Polling

​What to render

​Explorer links

​Finding orders another way

​Pagination

Polling

What to render

Explorer links

Finding orders another way

Pagination