# Get markets

Query for the exchange best bid/offer (EBBO) by instrument ID. If no query parameters are supplied then ALL available EBBOs will be returned.

Endpoint: GET /api/v1/market/quote
Version: v1.0.3

## Query parameters:

  - `instrument_id` (string)
    Instrument ID of the market to query for.

## Response 200 fields (application/json):

  - `id` (string)
    Exchange assigned ID of the market data.
    Example: "78901949723181070"

  - `symbol` (string)
    Human readable representation of the instrument.
    Example: "BTC-PYUSD"

  - `info` (object)

  - `info.last_trade` (object)

  - `info.last_trade.price` (string)
    Price of the last trade.
    Example: "110868"

  - `info.last_trade.qty` (string)
    Quantity of the last trade.
    Example: "0.00901"

  - `info.last_trade.timestamp` (string)
    The Unix UTC timestamp (in nanoseconds) when the trade was executed.
    Example: "1752156263825281640"

  - `info.best_bid` (object)

  - `info.best_bid.price` (string)
    Price at this level.
    Example: "110865.50"

  - `info.best_bid.qty` (string)
    Aggregate quantity resting at this level.
    Example: "0.00018"

  - `info.best_bid.order_count` (string)
    Number of orders resting at this level.
    Example: "10"

  - `info.best_ask` (object)

  - `info.last_update` (string)
    A UTC Unix epoch in nanoseconds indicating when the book was last updated.
    Example: "1752156513225654386"

## 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 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).