---
title: Orders
description: Reading order state, searching by hash or address, and paging through history.
---

import { DEFAULT_PAGE_LIMIT, MAX_PAGE_LIMIT } from "/snippets/vars.mdx";

Five methods read order state. All are unary; poll rather than subscribe.

## GetOrder

```
rpc GetOrder(GetOrderRequest) returns (OrderDetail)
```

Everything known about one quote hash.

<ParamField body="quote_hash" type="string" required>
  Hash returned by `GetQuote`.
</ParamField>

<ResponseField name="quote" type="QuoteView">
  The stored quote: hash, order parameters, fee breakdown, trade type, creation time, deposit deadline. Always present.
</ResponseField>

<ResponseField name="order" type="Order">
  Carries `state`, confirmations, and transaction hashes. A successful response always includes it; before the deposit is indexed the call returns `NOT_FOUND` instead.
</ResponseField>

<ResponseField name="deposit" type="Deposit">
  The matched source-chain deposit.
</ResponseField>

<ResponseField name="fulfillment" type="Fulfillment">
  Present once a fulfillment is attempted. Includes attempts, last error, and realized gas cost.
</ResponseField>

<ResponseField name="refund" type="Refund">
  Present once a refund is attempted.
</ResponseField>

Returns `NOT_FOUND` with `quote not found` if the hash is unknown, and `NOT_FOUND` with `order not found` if the quote exists but no deposit has been indexed yet. Poll until the order appears after depositing.

## Search

```
rpc Search(SearchRequest) returns (SearchResponse)
```

Resolves orders from whichever hash the user has: the quote hash, the source transaction hash, or the destination transaction hash. A transaction that batches several deposits matches one order per deposit.

<ParamField body="query" type="string" required>
  A quote hash or transaction hash. Empty input returns `INVALID_ARGUMENT`.
</ParamField>

Returns `orders`, a list of the same `OrderSummary` rows as `ListOrders`, in deposit order within the transaction. Call `GetOrder` with a row's `quote_hash` for the full detail. Returns `NOT_FOUND` with `no order matched` when nothing resolves. This is the right call to put behind a support search box.

## SearchAddress

```
rpc SearchAddress(SearchAddressRequest) returns (SearchAddressResponse)
```

Orders touching an address, as lightweight matches rather than full detail.

<ParamField body="address" type="string" required>
  Address to look up.
</ParamField>

<ResponseField name="matches" type="AddressMatch[]">
  Each carries `quote_hash`, `state`, `src_chain`, `dst_chain`, and `created_at`.
</ResponseField>

Use it for an autocomplete or a compact history strip; fetch full detail per hash when the user picks one.

## ListOrders

```
rpc ListOrders(ListOrdersRequest) returns (OrdersPage)
```

Paged order summaries for one address.

<ParamField body="address" type="string" required>
  Address the orders belong to.
</ParamField>

<ParamField body="limit" type="int64">
  Page size. Defaults to {DEFAULT_PAGE_LIMIT}, clamped to {MAX_PAGE_LIMIT}.
</ParamField>

<ParamField body="cursor" type="string">
  Opaque cursor from the previous page's `next_cursor`.
</ParamField>

<ResponseField name="items" type="OrderSummary[]">
  Each carries the quote hash, the order, the deposit, both token addresses and amounts, the recipient, a `gasless` flag, and `settled_at` once the fulfillment or refund confirmed.
</ResponseField>

<ResponseField name="next_cursor" type="string">
  Absent on the last page.
</ResponseField>

## ListRecentOrders

```
rpc ListRecentOrders(ListRecentOrdersRequest) returns (OrdersPage)
```

The same page shape, protocol-wide and newest first. Takes `limit` and `cursor` only. This is what the public explorer feed reads.

## Notes

Order state is the only authority on settlement. `dst_tx_hash` is populated at submission, before confirmation. See [Order lifecycle](/concepts/order-lifecycle) for the state list and [types](/api-reference/types#order) for full field definitions.