POST /orders endpoint; order type is inferred from the quote legs (fiat from → crypto to).
All write endpoints require a secret key (
sk_*) and HMAC request signing. Examples assume you have set CLIENT_ID, SECRET_KEY, ENC_KEY, and computed TIMESTAMP / SIGNATURE.Prerequisites
- KYB-approved partner account with API keys (
pk_*,sk_*,enc_*) - KYC completed on the end user, preferably via a KYC provider (required for onramp)
- A valid customer wallet address on the target network
- Authentication and signing implemented
End-to-end flow
1
Create a quote
Reserve an exchange rate for a fiat amount and target crypto currency/network.
2
Create the order
Submit the quote ID, recipient wallet, and customer details via
POST /orders.3
Collect fiat payment
Present
payin deposit instructions (bank account) from the order response to your customer.4
Wait for payment confirmation
Liquidramp auto-detects the transfer. Optionally call
POST /orders/:reference/fulfill with the bank reference if confirmation is delayed.5
Track settlement
Poll
GET /orders/:reference or subscribe to webhooks for order.settled.1. Create a quote
data.quote_id from the response. Quotes expire — create the order promptly. See Quotes.
2. Create the order
reference, type, from, to, pricing, optional fee, status, and payin.
There is no wallet-management API. Pass the customer’s destination as recipient.address. The network is taken from the quote’s to.network leg. Validate address format and chain before creating the order — sending to the wrong network is irreversible.
Present payin deposit instructions to the customer:
3. Confirm pay-in (optional)
Liquidramp auto-detects and confirms the customer’s bank transfer. Call fulfill only if confirmation is delayed:institution is optional. After confirmation, crypto is released to recipient.address.