Skip to main content
Liquidramp is a non-custodial liquidity aggregator. Your application talks to a single API; Liquidramp routes each order to liquidity providers who hold inventory and settle against banking rails and blockchain networks. Liquidramp does not take custody of customer funds. Providers settle on their own infrastructure while the platform coordinates quoting, routing, and settlement. This documentation is for API consumers who embed onramp, offramp, and swap, and for liquidity providers who run a provision node. If you supply inventory, start with Provision node setup.

Quickstart

Create an account, get keys, and start integrating.

Authentication

API keys, HMAC signing, and request headers.

API Reference

Interactive reference powered by OpenAPI.

Onramp

Fiat to crypto — quote, order, pay-in, settlement.

Offramp

Crypto to fiat — deposit, payout to bank.

Swap

Crypto-to-crypto on the same network.

​
What you can build

Each flow follows the same pattern: preview a rate, create an order, collect payment, then track settlement via the API or webhooks.

​
How a trade works

  1. Preview a rate (GET /v1/exchange-rate) or reserve a quote (POST /v1/orders/quote).
  2. Create an order (POST /v1/orders) with from and to legs (or a quote_id).
  3. The response includes pay-in instructions for your customer.
  4. After the customer pays, Liquidramp auto-detects and confirms the payment. POST /v1/orders/:reference/fulfill is optional — use it when confirmation is delayed.
  5. Order status advances until completed, failed, cancelled, or refunded. Webhooks notify you along the way.
See Order lifecycle for partner-visible statuses.

​
Getting access

  1. Create an account in the partner portal.
  2. Complete KYB. Quote and order writes require an approved account.
  3. Generate API keys (pk_*, sk_*, enc_*) in the portal.
  4. For onramp and offramp, complete KYC on your end users — preferably through a KYC provider. This is not required for swap.
  5. Call the Partner API with those keys. See Authentication.
Reference and rate-preview endpoints work with a public key (pk_*) or a secret key (sk_*). Creating quotes and orders requires a secret key used from your backend, HMAC signing with enc_*, and an approved KYB status.

​
Credentials

​
Partner API surface

Quickstarts: Onramp · Offramp · Swap Test environments return test networks; production returns mainnet. See Sandbox vs production.

​
Integration path

1

Create account

Sign up and complete KYB in the partner portal. Create account
2

Get API keys

Generate pk_*, sk_*, and enc_* keys in the portal. Authentication
3

Implement signing

HMAC-sign sk_* requests with enc_* from your backend. Authentication
4

Ship

Use quickstarts and the going-live checklist.