V3 transaction quotes
POST /v3/transactions/quotes previews the amounts, exchange rate, and fees for a
deposit or withdrawal. A quote is read-only and non-binding: it does not reserve a
price, create a transaction, or return a quote ID. Creation recalculates the price.
Before integrating, confirm your account’s V3 access and available payment rails
with Adesic support. Use the api-key header for the
account making the transaction; see authentication and account scope.
Request a withdrawal quote
This example fixes the amount of USDC to send and calculates the USD to receive.
Amounts are positive decimal strings, with at most two decimal places. Supply
amount on exactly one side. Use uppercase assets and lowercase networks and rails.
curl --request POST 'https://api.adesic.com/v3/transactions/quotes' \
--header 'api-key: YOUR_API_KEY' \
--header 'Content-Type: application/json' \
--data '{
"type": "WITHDRAWAL",
"send": { "amount": "1000.00", "asset": "USDC", "network": "ethereum" },
"receive": { "asset": "USD", "rail": "wire" }
}'To fix the USD amount instead, put amount in receive and omit it from send.
Do not include wallet IDs, bank-account IDs, purpose, documents, or creation price
protection in a quote request.
Deposit quotes and supported routes
A deposit sends USD to receive crypto. For example, use this JSON body with the same quote endpoint:
{
"type": "DEPOSIT",
"send": { "amount": "1000.00", "asset": "USD", "rail": "wire" },
"receive": { "asset": "USDC", "network": "ethereum" }
}Both directions accept the following route vocabulary, subject to account and payment-rail eligibility:
| Asset | Networks |
|---|---|
| USDC | ethereum, polygon, solana, base |
| USDT | ethereum, polygon, solana, tron |
The USD rails are ach, wire, and rtp. A recognized rail is not a promise of
availability for your account. TRANSFER and TRADE are not supported quote or
creation types.
Use the result
A successful 200 OK response contains type, send, receive, exchangeRate,
and fees. Both sides now have an amount. exchangeRate contains from, to,
and a decimal-string value; fees contains asset: "USD" and decimal-string
total, transaction, paymentRail, and network amounts.
Show the returned economics to the customer, then build a creation request with the same fixed side and the customer’s resource IDs. Do not submit the quote response as a creation request: it contains both amounts and response-only fields. Use creation price protection if the customer requires a minimum receipt or maximum spend. See errors and retries when quoting or creating fails.
Migrating from V2
POST /v2/transactions/quote is retired. V3 uses the plural /quotes path and
type, send, and receive instead of sourceOrder and destinationOrder.
Continue with the V3 transaction lifecycle.