> ## Documentation Index > Fetch the complete documentation index at: https://docs.hypedexer.com/llms.txt > Use this file to discover all available pages before exploring further. # Recent trades > Alias of `trades`. Recent taker-side trades (one per tid) from the live allFills snapshot (~200 fills sliding window). Optional `coin`, `startTime`, `endTime`, `limit`. ## OpenAPI ````yaml /live-data/openapi-rest.json post /info#recentTrades openapi: 3.0.3 info: title: Hypedexer Live Data — REST API version: 0.1.0 description: >- REST API for real-time Hyperliquid market data served from a local fullnode. All data is accessed through a single unified endpoint `POST /info` that dispatches based on the `type` field in the JSON body. ## Request types | Type | Description | Handled | |------|-------------|----------| | `metaAndAssetCtxs` | Asset context (funding, OI, prices) | Locally (Redis cache) | | `allMids` | Mid prices for all coins | Locally (Redis cache) | | `userFills` / `userFillsByTime` | Fills for a specific user | Locally (volume files) | | `allFills` | All fills globally | Locally (volume files) | | `trades` | Trade data | Locally (volume files) | | `l2Book` / `l2Books` | L2 order book snapshot | Locally | | `availableDates` | Available data dates | Locally | | `clearinghouseState` | Clearinghouse state (single/multi-user) | Locally with upstream proxy per user | | `meta`, `spotMeta`, `openOrders`, ... | Proxied to local Hyperliquid node | Proxied to upstream | ## Authentication Optional. When `API_KEY` is configured on the server, all requests must include: ``` Authorization: Bearer ``` ## Response format Most types return: ```json { "result": , "cursor": null } ``` `allMids` returns the result directly (not wrapped): ```json { "BTC": "66764.5", "ETH": "3421.2" } ``` Proxied types return the upstream response as-is. contact: name: Hypedexer servers: - url: https://api.hypedexer.com description: Production — Live fullnode data security: - BearerAuth: [] tags: - name: Health description: Service health and info. - name: Asset Context description: >- Real-time asset context data: funding, open interest, oracle/mark/mid prices, volumes. Sourced from Redis cache populated by the asset context worker. - name: Mid Prices description: Mid prices for all coins, optionally filtered by DEX. - name: Fills description: >- Executed fills from the Hyperliquid fullnode volumes. Supports user-specific and global queries. - name: Trades description: Trade data from the fullnode volumes. - name: Order Book description: L2 order book snapshots. - name: Metadata description: Volume availability and data metadata. - name: Clearinghouse description: >- Clearinghouse state with multi-user support. Each user is fetched individually from the upstream Hyperliquid node. - name: Proxied — Perpetuals description: >- Perpetual market metadata, margin, OI caps, DEX configs. Proxied to upstream Hyperliquid node. - name: Proxied — Spot description: >- Spot market metadata, balances, and deploy state. Proxied to upstream Hyperliquid node. - name: Proxied — Trading description: >- Orders, positions, and active asset data. Proxied to upstream Hyperliquid node. - name: Proxied — Account description: >- User account info: fees, rate limits, sub-accounts, agents, roles. Proxied to upstream Hyperliquid node. - name: Proxied — Vaults description: >- Vault summaries, equities, and leaderboards. Proxied to upstream Hyperliquid node. - name: Proxied — Staking description: >- Delegations, staking summaries, and validator votes. Proxied to upstream Hyperliquid node. - name: Proxied — Exchange description: >- Exchange status, liquidatable positions, web data. Proxied to upstream Hyperliquid node. paths: /info#recentTrades: post: tags: - Trades summary: Recent trades description: >- Alias of `trades`. Recent taker-side trades (one per tid) from the live allFills snapshot (~200 fills sliding window). Optional `coin`, `startTime`, `endTime`, `limit`. operationId: recentTrades requestBody: required: true content: application/json: schema: type: object required: - type properties: type: type: string enum: - recentTrades coin: type: string description: Coin symbol example: BTC startTime: type: integer endTime: type: integer limit: type: integer default: 100 example: type: recentTrades coin: BTC limit: 50 responses: '200': description: List of trades content: application/json: schema: type: object properties: result: type: array items: $ref: '#/components/schemas/Trade' '401': $ref: '#/components/responses/Unauthorized' security: - BearerAuth: [] components: schemas: Trade: type: object description: A trade record from the fullnode volumes properties: coin: type: string example: BTC px: type: string description: Trade price example: '65000.5' sz: type: string description: Trade size example: '0.1' time: type: integer description: Timestamp in milliseconds example: 1700000050000 side: type: string enum: - A - B description: A = ask (sell), B = bid (buy) ErrorResponse: type: object required: - error properties: error: type: string description: Error message responses: Unauthorized: description: >- Invalid or missing API key (only when `API_KEY` is configured on the server) content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' example: error: Invalid API key securitySchemes: BearerAuth: type: http scheme: bearer description: >- Optional. API key passed via `Authorization: Bearer `. Required only when `API_KEY` is configured on the server. ````