> ## Documentation Index
> Fetch the complete documentation index at: https://docs.whitebit.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Recent trades

> Get the most recent trades executed on a specific market on WhiteBIT via the V4 API.

* [Orderbook](/api-reference/market-data/orderbook) — current order book with configurable depth and aggregation.
* [Market activity](/api-reference/market-data/market-activity) — 24-hour pricing and volume summary per market.


## OpenAPI

````yaml /openapi/public/http-v4.yaml GET /api/v4/public/trades/{market}
openapi: 3.0.3
info:
  title: Public HTTP API V4
  description: >
    WhiteBIT Public HTTP API V4 for market data and trading information.

    Base URL: https://whitebit.com

    All endpoints return time in Unix-time format.

    All endpoints return either a JSON object or array.

    Use HTTP method GET for API calls.

    Send parameters as query string when an endpoint requires them.


    <Warning>

    Rate limit: 2000 requests/10 sec for most endpoints (specific limits noted
    per endpoint).

    </Warning>


    ## Caching and data freshness


    Most public endpoints serve cached data. The cache is **shared across all
    callers** — values are keyed by the resource (market, currency), never by
    account — and invalidates on a **time basis only**: an upstream change
    becomes visible after the next refresh, not immediately.


    Two refresh tiers apply:


    - **Reference data** (`markets`, `assets`, `fee`, `collateral/markets`,
    `futures`) refreshes from the database on a fixed interval, ranging from
    about 10 seconds to about 1 minute depending on the endpoint.

    - **Market data** (`trades`, `orderbook`, `orderbook/depth`, `ticker`) uses
    a short-lived cache, about 1 second by default.


    `time` and `ping` are computed per request and are not cached. Each endpoint
    states its own refresh interval. Polling faster than that interval returns
    identical data and consumes rate-limit budget without producing fresher
    results.


    ## Error responses


    Public V4 endpoints do not share a single error schema. Depending on the
    endpoint, an error arrives in one of three shapes (there is no `params`
    field on any public error):


    - **Flat validation bag (HTTP 422)** — `{ "<field>": ["<message>"] }`. No
    envelope. Used by the market endpoints (`orderbook`, `orderbook/depth`,
    `trades`). Example: `{ "market": ["Market is not available."] }`. On
    `funding-history` the values are single strings rather than arrays.

    - **Wrapped, HTTP 200 even on validation errors** — `{ "success": false,
    "message": { "<field>": ["<message>"] }, "result": null }`. Used by the V4
    `kline` endpoint (not part of this portal — the documented Kline endpoint is
    V1).

    - **Wrapped string message (HTTP 4xx)** — `{ "success": false, "message":
    "<string>", "errors": [] }`. Used by the margin/futures collateral subset of
    endpoints. Parameterless endpoints (`markets`, `ticker`, `assets`, `fee`)
    take no input and so produce no validation errors — they fail only at the
    infrastructure level below.


    Common failures are produced at the infrastructure layer, not by the
    application, and do not follow these shapes:


    - **Maintenance** — every endpoint returns **HTTP 503** with a non-JSON body
    served by the gateway.

    - **Rate limit exceeded** — **HTTP 429** with a non-JSON body served by the
    gateway/CDN.

    - **Internal server error** — **HTTP 500** with a flat body `{ "error":
    ["Internal server error."] }`.

    - **Unknown route** — **HTTP 404** with an empty body.
  version: 4.0.0
servers:
  - url: https://whitebit.com
    description: WhiteBIT Global Server
  - url: https://whitebit.eu
    description: WhiteBIT EU Server
security: []
tags:
  - name: Public API V4
    description: Public endpoints for market data, trading information, and platform status
paths:
  /api/v4/public/trades/{market}:
    get:
      tags:
        - Public API V4
      summary: Recent Trades
      description: >
        The endpoint retrieves the [trades](/glossary#deal-trade) that have been
        executed recently on the requested [market](/glossary#market).


        <Note>

        The API caches the response for 1 second

        </Note>


        <Note>
          Public trade data can include executions that originate from RPI orders. Public order book feeds (`depth`, `bookTicker`) exclude RPI orders. RPI orders appear only in private active orders and in the exchange UI order book (web and mobile).
        </Note>



        <Warning>

        Rate limit 2000 requests/10 sec.

        </Warning>
      parameters:
        - name: market
          in: path
          required: true
          description: Market pair name
          schema:
            type: string
            example: BTC_USDT
        - name: type
          in: query
          required: false
          description: Filter by trade side. Omit to return both buy and sell trades.
          schema:
            type: string
            enum:
              - buy
              - sell
            example: sell
      responses:
        '200':
          description: Successful response
          content:
            application/json:
              schema:
                type: array
                items:
                  type: object
                  required:
                    - tradeID
                    - price
                    - quote_volume
                    - base_volume
                    - trade_timestamp
                    - type
                  properties:
                    tradeID:
                      type: integer
                      description: >-
                        A unique ID associated with the trade for the currency
                        pair transaction Note: Unix timestamp does not qualify
                        as trade_id.
                      example: 158056419
                    price:
                      type: string
                      description: Transaction price in quote pair volume.
                      example: '9186.13'
                    quote_volume:
                      type: string
                      description: >-
                        Transaction amount in the quote (stock) currency. In a
                        BTC_USDT market, the value is the BTC amount. Note:
                        WhiteBIT uses a reversed naming convention compared to
                        standard exchange terminology — the stock/asset currency
                        is called 'quote' here.
                      example: '0.0021'
                    base_volume:
                      type: string
                      description: >-
                        Transaction amount in the base (money) currency. In a
                        BTC_USDT market, the value is the USDT amount. Note:
                        WhiteBIT uses a reversed naming convention compared to
                        standard exchange terminology — the settlement/pricing
                        currency is called 'base' here.
                      example: '9186.13'
                    trade_timestamp:
                      type: integer
                      description: >-
                        Unix timestamp in seconds (UTC). Identifies when the
                        transaction occurred.
                      example: 1594391747
                    type:
                      type: string
                      description: >-
                        Used to determine whether or not the transaction
                        originated as a buy or sell. Buy – Identifies an ask
                        that was removed from the order book. Sell – Identifies
                        a bid that was removed from the order book.
                      enum:
                        - buy
                        - sell
                      example: sell
                    rpi:
                      type: boolean
                      description: >-
                        Indicates that the trade originates from a Retail Price
                        Improvement (RPI) order.
                      example: true
              example:
                - tradeID: 158056419
                  price: '9186.13'
                  quote_volume: '0.0021'
                  base_volume: '0.0021'
                  trade_timestamp: 1594391747
                  type: sell
                  rpi: true
                - tradeID: 158056416
                  price: '9186.13'
                  quote_volume: '0.002751'
                  base_volume: '0.002751'
                  trade_timestamp: 1594391746
                  type: sell
                  rpi: false
        '422':
          description: >-
            Validation error. Returned when the `market` path parameter is
            unknown or not enabled for trading.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/PublicValidationError'
              example:
                market:
                  - Market is not available.
components:
  schemas:
    PublicValidationError:
      type: object
      description: >-
        Flat field-keyed validation error (HTTP 422) returned by the market-data
        endpoints. Each key is the offending request field and the value is an
        array of human-readable messages. There is no success/message envelope
        and no `params` field.
      additionalProperties:
        type: array
        items:
          type: string
      example:
        market:
          - Market is not available.

````