Liquify API Docs
THORCHAIN / MAINNET

One endpoint.
Native cross-chain data.

Live THORChain quotes and network data, served through liquify.fyi. Original methods. Unmodified response bodies.

BASE URLhttps://liquify.fyi
Built on the public THORChain APIs

Queries go directly to the public upstream services. No added affiliate fees, quote markup, or response envelope.

Authentication

Send your API key on every API request using X-API-Key or Authorization: Bearer. Documentation is public. Never put your key in a URL or a public frontend bundle.

curl 'https://liquify.fyi/thorchain/pools' \
  -H "X-API-Key: $LIQUIFY_API_KEY"

Set LIQUIFY_API_KEY securely in your server environment. The interactive tools keep a key only in page memory, until the page is closed or reloaded.

Live quotes & memos

GET /thorchain/quote/swap

Load the current THORChain asset list, choose a pair, and enter your recipient address. The quote and memo come directly from THORNode. This tool does not sign or submit transactions.

Enter your key to discover supported assets.
Optional refund address

Use an address on the source chain. Adding it can exceed memo limits on UTXO chains; THORNode will reject an oversized memo.

No request sent
The exact upstream response will appear here.
Live chain and token availability

Status is checked before each quote. An available pool alone does not guarantee an active chain. Only assets with available liquidity and no reported trading halt are selectable.

Use GET /liquify/assets with your API key for the live asset catalog. Native RUNE is included. Original THORChain endpoints retain their upstream response format. View the live-test coverage report →

API reference

Explore the upstream specifications, request parameters, response schemas, and examples. Use Authorize in the explorer to call Liquify.

THORNode ↗

Quotes, pools, vaults, nodes, swaps and network state.

Midgard ↗

Historical data, volume, earnings, members and analytics.

Cosmos REST ↗

Accounts, balances, blocks, transactions and SDK queries.

CometBFT RPC ↗

Consensus, blocks, validators, ABCI and transaction submission.

Compatibility

Keep the original paths: /thorchain/…, /v2/…, and /cosmos/…. CometBFT supports /rpc for JSON-RPC POST, /rpc/status, and native paths such as /status.

Provider-style aliases are also supported: /chain/thorchain_api/…, /chain/thorchain_midgard/…, /chain/thorchain_rpc/…, and the thorchain_v1_api / thorchain_v1_rpc archive prefixes.

What stays the same

Method names, query strings, request bodies, upstream HTTP status, and response body bytes. Authentication and transport headers are managed by this gateway. Live prices, block heights and quote expiry will differ from documentation examples.

Availability follows the upstream node. Disabled methods, rate limits and provider errors are returned as received. Your Liquify key grants access to this gateway; it does not unlock private provider subscriptions. Native gRPC over HTTP/2 and P2P require their own endpoints; this gateway exposes HTTP REST and RPC. WebSocket forwarding is implemented for clients that send authentication headers, but upstream availability is not guaranteed.

This is an independent service, not affiliated with THORChain or the operator of liquify.com. Documentation styling incorporates the open-source THORChain documentation theme. Source credits and licenses.