> ## Documentation Index > Fetch the complete documentation index at: https://docs.predictamarkets.com/llms.txt > Use this file to discover all available pages before exploring further. # Get Trade Data > Returns trade data aggregated by time window (OHLCV candles) suitable for price charts. ## OpenAPI ````yaml GET /v1/markets/{market_id}/trades/aggregated openapi: 3.0.3 info: title: Predicta Markets API description: >- The Predicta Markets REST API lets you build on top of a continuous double-auction prediction market platform. Users buy and sell shares in YES/NO outcomes of real-world events. When a market resolves, holders of the winning side receive payouts; holders of the losing side lose their stake. Data model hierarchy: Market → MarketAsset → MarketAssetOption (prediction key) → Order. A Market is a question about a real-world event (e.g. 'Will Arsenal win the Premier League?'). Each Market contains one or more MarketAssets — the tradeable outcomes. Simple binary markets have a single asset; multi-player markets (e.g. Player of the Match) have one asset per candidate. Each MarketAsset exposes two options, YES and NO, each carrying a prediction_key — the unique hash you pass when placing an order to identify exactly which outcome you are trading. Trading flow: (1) call GET /v1/markets to find a market; (2) inspect market_assets and their options to get the prediction_key for the outcome you want; (3) call POST /v1/markets/{market_id}/orders with that prediction_key, your price, and quantity. Orders match immediately when a counterparty exists, otherwise they rest as open limit orders in the order book. Price system: all prices are integers in the range 1–99, representing cents. Price equals implied probability in percent — a YES price of 65 means the market implies a 65% chance the event will occur. YES and NO prices for the same asset always sum to approximately 100. Currency: the platform's internal unit is PT (Predicta Token). Balances, prices, and payout amounts are expressed in PT unless the market was created with a real-currency denomination. QID system: many resources expose a human-readable qualified ID (qid) alongside the numeric id. QIDs are computed, not stored as database columns. Prefix conventions — MA: market, MAA: market asset, AP: account payout. Most path parameters accept either the numeric id or the qid interchangeably. Authentication: include your API key in the X-Api-Key request header. All account-scoped endpoints require authentication. Market listing and detail endpoints are public. version: 1.0.0 contact: email: api-support@predictamarkets.com servers: - url: https://api.predictamarkets.com description: Production security: [] paths: /v1/markets/{market_id}/trades/aggregated: get: tags: - Market summary: Get Trade Prices description: >- Returns trade data aggregated by time window (OHLCV candles) suitable for price charts. operationId: >- get_market_trades_aggregated_v1_markets__market_id__trades_aggregated_get parameters: - name: market_id in: path required: true schema: $ref: '#/components/schemas/TQID' - name: interval in: query required: false schema: type: string pattern: ^(?:\d+)?\s*(second|minute|hour|day|week|month|year|all)s?$ description: >- Time interval to aggregate (e.g., 1 hour, 1 day, 1 week, 1 month, 1 year) default: 1 month title: Interval description: >- Time interval to aggregate (e.g., 1 hour, 1 day, 1 week, 1 month, 1 year) responses: '200': description: List of trades content: application/json: schema: type: array items: type: object properties: yes_trade_price: type: number description: Last traded price for the YES side (1–99) trade_timestamp: type: string format: date-time description: UTC timestamp of the trade market_asset_id: type: integer description: ID of the market asset (outcome) this trade belongs to required: - yes_trade_price - trade_timestamp - market_asset_id example: - yes_trade_price: 86 trade_timestamp: '2026-05-16T00:00:00' market_asset_id: 199651 - yes_trade_price: 10 trade_timestamp: '2026-05-16T00:00:00' market_asset_id: 199652 - yes_trade_price: 4 trade_timestamp: '2026-05-16T00:00:00' market_asset_id: 199653 '404': description: Not found content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' example: detail: Market not found '422': description: Validation Error content: application/json: schema: $ref: '#/components/schemas/HTTPValidationError' '500': $ref: '#/components/responses/InternalServerError' components: schemas: TQID: anyOf: - type: string - type: integer description: >- Flexible identifier type that accepts either a numeric integer ID or a human-readable qualified ID string (QID). QIDs follow a prefix convention: MA for markets, MAA for market assets, AP for account payouts. Most path parameters that accept an ID use this type so callers can use whichever form is more convenient. ErrorResponse: type: object properties: detail: type: string description: Human-readable error message required: - detail title: ErrorResponse HTTPValidationError: properties: detail: items: $ref: '#/components/schemas/ValidationError' type: array title: Detail type: object title: HTTPValidationError description: >- Returned by FastAPI when request validation fails (HTTP 422). Contains one or more ValidationError entries describing each invalid field. ValidationError: properties: loc: items: anyOf: - type: string - type: integer type: array title: Location description: >- Path to the invalid field as a list of keys and/or array indices. For example, ['body', 'price'] indicates the price field in the request body failed validation. msg: type: string title: Message description: Human-readable explanation of what validation rule was violated. type: type: string title: Error Type description: >- Machine-readable Pydantic error type (e.g. 'value_error.missing', 'type_error.integer'). type: object required: - loc - msg - type title: ValidationError description: >- A single field validation failure within an HTTP 422 response. The loc array traces the path to the invalid field (e.g. ['body', 'price']). responses: InternalServerError: description: Internal Server Error content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' example: detail: An unexpected error occurred. Please try again later. ````