0x Swap API: Price for browsing, quote for trading
0x Swap API price vs quote endpoint difference: use /price while users edit and /quote at confirmation for firm, executable transaction data.
By Crypto Docket Newsroom#1817364 min read

For an app deciding which 0x Swap API endpoint to call, use /price while a user browses or edits an amount, then /quote when they are ready to review and submit; /price is indicative, while /quote returns firm transaction data for the taker.
- Use /price to refresh the displayed amount and route as inputs change.
- Use /quote at confirmation, check its issues and transaction fields, then submit promptly.
Price is for the changing screen; quote is for the submitted trade
Take a user entering a sell amount for a token pair. While they type, call /price with chainId, sellToken, buyToken, sellAmount and the taker address. Send the required 0x-api-key and 0x-version: v2 headers. The v2 endpoints sit under either /swap/allowance-holder/ or /swap/permit2/, depending on the approval flow.
The /price response is indicative: it can include buyAmount, minBuyAmount, a route and a gas estimate, but it has no transaction object to sign and send. That makes it useful for showing a changing estimate. It is not the executable instruction for the swap. The [0x getPrice documentation](https://docs.0x.org/docs/0x-swap-api/api-references/get-swap-price) describes this endpoint.
Debounce /price calls as the user edits, so a burst of keystrokes does not trigger a request for every intermediate amount. Refresh the displayed estimate after the latest input settles. This keeps the screen responsive while limiting repeated requests for information the user may immediately change.
At Review, fetch /quote for the current inputs and taker. This is the firm step: the request can ask market makers through RFQ to reserve liquidity for the trade. The response includes transaction fields such as to, data, value and gas. A Permit2 quote also includes an EIP-712 object the user must sign; AllowanceHolder uses its own approval flow. The [0x getQuote documentation](https://docs.0x.org/docs/0x-swap-api/api-references/get-swap-quote) covers the firm response.
That commitment is useful when a user intends to trade, but wasteful on a live price display: requesting firm quotes while amounts are still changing uses rate limit and can make fills worse by repeatedly asking market makers to reserve liquidity. Matcha swap faces the same product choice when showing a token exchange estimate versus preparing a specific trade. A user considering a separate order type may also find matcha limit orders relevant to that distinction.
Read the quote’s issues before enabling Swap. In particular, handle liquidityAvailable: false as no available route for the requested trade; the response may omit the other quote fields. Check allowance and balance issues too. An allowance issue means the user may need to approve the returned spender, while a balance issue means the taker may not hold enough of the sell token. Do not treat the presence of transaction data alone as a green light.
A quote can go stale between Review and submission as liquidity or market conditions change. Submit promptly; if the quote fails or reverts, request a fresh /quote using the user’s current inputs rather than replaying old transaction data. The price-versus-quote rule still holds if the user changes the amount after Review: refresh /price while they edit, then get a new /quote for the amount they confirm.
Related questions
Permit2 or AllowanceHolder: which 0x flow should an app use?
Both flows offer /price and /quote. Choose the path that matches the app’s token approval design: AllowanceHolder is the simpler standard approval route for many integrations, while Permit2 quotes add an EIP-712 signature step. Keep the selected path consistent between price, quote and the eventual transaction. See [0x’s Permit2 and AllowanceHolder comparison](https://docs.0x.org/docs/0x-swap-api/advanced-topics/permit2).
How is an integrator fee added with the 0x Swap API?
Fee configuration affects the trade being priced, so include it consistently when requesting /price and /quote. The user’s final review should reflect the quote produced with that configuration, not an earlier estimate made without it.
What is the difference between buyAmount and minBuyAmount in a 0x response?
buyAmount is the quoted output amount; minBuyAmount is the minimum output threshold used to protect execution against adverse price movement. Show the quoted amount as an estimate of what the user receives, and treat the minimum as the boundary the trade must satisfy.
Map the calls to the user’s state: debounce /price during browsing and editing, then fetch /quote on Review and submit promptly. That gives the screen a responsive estimate and gives the transaction stage the firm data it needs.