# Compute market quote

Calculate a quote preview for an asset using current visible order book depth. Supports both base quantity and quote (notional) quantity via the required qty_unit parameter.
In schema , successful responses contain only  and .
For , the exchange computes the largest executable base quantity that fits within the requested quote amount while respecting the instrument's base increment at the final consumed price level. As a result, in schema  the returned  may be slightly less than the requested quote amount and the difference is reported in .


Endpoint: POST /api/v1/markets/quote
Version: v1.0.4

## Request fields (application/json):

  - `qty` (string, required)
    The quantity to quote. Interpretation depends on qty_unit: for BASE this is the base asset amount, for QUOTE this is the notional (e.g. USD) amount.
    Example: "1.5"

  - `instrument_id` (string, required)
    The instrument ID for which to calculate the quote. Must be a valid non-zero numeric ID.
    Example: "1"

  - `side` (string, required)
    The side of the quote request. BUY calculates the price to buy the base asset, SELL calculates the price to sell.
    Enum: "BUY", "SELL"

  - `qty_unit` (string, required)
    Unit of the qty field. BASE means qty is in base asset units, QUOTE means qty is in quote asset (notional) units. Required — no default.
    Enum: "BASE", "QUOTE"

## Response 200 fields (application/json):

  - `qty` (string)
    The base quantity. For qty_unit=QUOTE, this is the computed base amount. For qty_unit=BASE, this echoes back the requested base quantity.
    Example: "1.5"

  - `price` (string)
    The calculated VWAP (Volume-Weighted Average Price) across consumed order book levels.
    Example: "50025.50"

  - `notional` (string)
    Schema  only. The expected quote amount consumed from visible order book liquidity.
    Example: "75038.25"

  - `notional_residual` (string)
    Schema  only. The unfilled portion of the requested quote amount. This is typically zero, but for qty_unit=QUOTE it can be positive when the remaining amount is smaller than one base increment at the final consumed price level.
    Example: "0.10"

## Response 400 fields (application/problem+json):

  - `type` (string, required)
    A URI reference that identifies the problem type.
    Example: "about:blank"

  - `title` (string, required)
    A short, human-readable summary of the problem type.
    Example: "An Error Occured"

  - `status` (integer, required)
    The HTTP status code generated by the origin server.
    Example: 400

  - `detail` (string)
    A human-readable explanation specific to this occurrence of the problem.
    Example: "A more detailed sentence about the error"

  - `instance` (string)
    A URI reference that identifies the specific occurrence of the problem.
    Example: "/api/v1/endpoint"

  - `extensions` (object)
    A map for extension members (custom fields not defined by the RFC).

## Response 404 fields (application/problem+json):

  - `type` (string, required)
    A URI reference that identifies the problem type.
    Example: "about:blank"

  - `title` (string, required)
    A short, human-readable summary of the problem type.
    Example: "An Error Occured"

  - `status` (integer, required)
    The HTTP status code generated by the origin server.
    Example: 400

  - `detail` (string)
    A human-readable explanation specific to this occurrence of the problem.
    Example: "A more detailed sentence about the error"

  - `instance` (string)
    A URI reference that identifies the specific occurrence of the problem.
    Example: "/api/v1/endpoint"

  - `extensions` (object)
    A map for extension members (custom fields not defined by the RFC).

## Response 500 fields (application/problem+json):

  - `type` (string, required)
    A URI reference that identifies the problem type.
    Example: "about:blank"

  - `title` (string, required)
    A short, human-readable summary of the problem type.
    Example: "An Error Occured"

  - `status` (integer, required)
    The HTTP status code generated by the origin server.
    Example: 400

  - `detail` (string)
    A human-readable explanation specific to this occurrence of the problem.
    Example: "A more detailed sentence about the error"

  - `instance` (string)
    A URI reference that identifies the specific occurrence of the problem.
    Example: "/api/v1/endpoint"

  - `extensions` (object)
    A map for extension members (custom fields not defined by the RFC).

## Response 503 fields (application/problem+json):

  - `type` (string, required)
    A URI reference that identifies the problem type.
    Example: "about:blank"

  - `title` (string, required)
    A short, human-readable summary of the problem type.
    Example: "An Error Occured"

  - `status` (integer, required)
    The HTTP status code generated by the origin server.
    Example: 400

  - `detail` (string)
    A human-readable explanation specific to this occurrence of the problem.
    Example: "A more detailed sentence about the error"

  - `instance` (string)
    A URI reference that identifies the specific occurrence of the problem.
    Example: "/api/v1/endpoint"

  - `extensions` (object)
    A map for extension members (custom fields not defined by the RFC).