Bid-Ask Spread Percent
Last updated
Was this helpful?
Last updated
Was this helpful?
Spread, one of the most common measures of liquidity and transaction costs, is the difference between the price that buyers are bidding at and the price that sellers are asking for. A large spread indicates disagreement between market participants on price and lends to inefficiencies in the market.
Spread is normally calculated using the prices listed at the top of the book— that is, comparing the highest bidding price and the lowest asking price. There are many variations on spread in the literature, such as an effective spread that only uses market candle data and taking into account a degree of orderbook depth. However, here we stick to the classical formulation of spread.
Spread, the difference between the quote asset’s ask and bid price, can be presented raw or as a percentage of a reference price. Typically this reference price is the midpoint between the bid and asking price. Here we represent it as a percentage of the mid price.
We offer the bid-ask spread over 1m, 1h, and 1d intervals. Each of these metrics represents the average bid-ask spread over the interval of time.
Liquidity bid-ask spread metrics can be accessed using the following endpoints:
timeseries/market-metrics
A sample of the daily bid-ask spread for the coinbase-btc-usd-spot
market is shown below:
market
: The IDs of the market.\
time
: The time in ISO 8601 date-time format.\
liquidity_bid_ask_spread_percent_1d
: The daily average spread between the bid-ask price, represented as a percentage of the mid price.
The values are in percent units. For example, if the value is 0.0076, it should be interpreted as 0.0076%.
Release Version. Market Data Feed v2.8 on May 2023.
Returns metrics for specified markets.<br/> Results are ordered by tuple (market, time)
.<br/> To fetch the next page of results use next_page_url
JSON response field.<br/>
/timeseries/market-metrics
Comma separated list of markets or market patterns like exchange-*
or exchange-*-spot
or *USDT-future
.<br/> Use the /catalog-all/markets endpoint for the full list of supported markets.
Comma separated metrics to request time series data for.<br/> Use the /catalog-all/market-metrics endpoint for the full list of supported metrics per exchange-asset combination.
["liquidations_reported_future_buy_units_1d","liquidations_reported_future_sell_units_1d"]
Frequency of the market metrics. Supported values are 1m
, 5m
, 1h
, 1d
.
Start of the time interval.<br/> This field refers to the time
field in the response.<br/> Multiple formats of ISO 8601 are supported: 2006-01-20T00:00:00Z
, 2006-01-20T00:00:00.000Z
, 2006-01-20T00:00:00.123456Z
, 2006-01-20T00:00:00.123456789Z
, 2006-01-20
, 20060120
.<br/> Inclusive by default.<br/> UTC timezone by default. Z
suffix is optional and timezone
parameter has a priority over it.<br/> If start_time
is omitted, response will include time series from the earliest time available.
End of the time interval.<br/> This field refers to the time
field in the response.<br/> Multiple formats of ISO 8601 are supported: 2006-01-20T00:00:00Z
, 2006-01-20T00:00:00.000Z
, 2006-01-20T00:00:00.123456Z
, 2006-01-20T00:00:00.123456789Z
, 2006-01-20
, 20060120
.<br/> Inclusive by default.<br/> UTC timezone by default. Z
suffix is optional and timezone
parameter has a priority over it.<br/> If end_time
is omitted, response will include time series up to the latest time available.
Inclusive or exclusive corresponding start_*
parameters.
Inclusive or exclusive corresponding end_*
parameters.
Timezone name for start_time
and end_time
timestamps.<br/> This parameter does not modify the output times, which are always UTC
.<br/> Format is defined by TZ database.
America/New_York
Number of items per single page of results.<br/> The value of this parameter is ignored if the endpoint supports the format
parameter and its value is set to json_stream
.
Where does the first page start, at the start of the interval or at the end.
start
, end
How results will be sorted. Metrics are sorted by (market, time)
by default. If you want to sort 1d
metrics by (time, market)
you should choose time
as value for the sort
parameter.<br/> Sorting by time
is useful if you request metrics for a set of markets.
market
, time
How many entries per market result should contain. It is useful when multiple markets are requested.
Human-readable formatting of JSON responses.
Format of the response.
json
, csv
Token for receiving the results from the next page of a query.<br/> Should not be used directly. To iterate through pages just use next_page_url
response field.