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

# Get Market Events

> Returns public, finalized MINED CLOB trades newest first. An exact market slug selects that market; if no market matches, an exact group slug combines all group markets. Stable-slug aliases are not resolved. No authentication is required.

Returns public, finalized CLOB trade activity. Each event represents a `MINED` trade; this endpoint does not report order placement, cancellation, or liquidity-change events. No authentication is required.

## Slug scope

The path accepts either an exact market slug or an exact market-group slug. Market lookup runs first. A market slug returns trades for that market; a group slug combines trades from all markets in the group. Stable-slug aliases are not resolved.

The feed is backed only by finalized CLOB trades. Resolving a market that has no such activity returns an empty page.

## Trade fields and units

Events are ordered newest first. `side` is the taker side and uses the numeric mapping `0 = BUY`, `1 = SELL`.

`matchedSize` is the taker's filled position-token amount in raw 6-decimal units. `makerAmount` and `takerAmount` currently both contain the trade's collateral cost in raw 6-decimal units. These three values are decimal strings; divide them by `1e6` for display amounts. `price` is the weighted average fill price as a JSON number.

When available, `profile` publicly attributes the taker by username, display name, profile-picture URL, social URL, and rank. The field is omitted when no public profile can be resolved.

## Pagination

`page` defaults to `1` and `limit` defaults to `100`. Both must be integers greater than or equal to `1`, and `limit` cannot exceed `100`.

A populated page returns `events`, `limit`, `page`, `totalPages`, and `totalRows`. The current runtime returns the reduced shape below whenever a page has no events, including an out-of-range page:

```json theme={null}
{
  "events": [],
  "totalPages": 0
}
```

The reduced empty-page shape intentionally omits `limit`, `page`, and `totalRows`.

## Freshness and caching

Successful responses use `Cache-Control: public, max-age=30, s-maxage=30, stale-while-revalidate=30`. Newly mined trades may therefore not appear immediately. A `404` response uses a 5-minute cache and a further 5-minute stale-while-revalidate window.

## Errors

| Status | Meaning                                                               |
| ------ | --------------------------------------------------------------------- |
| `400`  | `page` or `limit` is invalid, or an unknown query field was supplied. |
| `404`  | The slug matches neither an exact market nor an exact market group.   |
| `500`  | The trade activity lookup failed unexpectedly.                        |


## OpenAPI

````yaml GET /markets/{slug}/events
openapi: 3.0.0
info:
  title: Limitless Exchange API
  description: >-

    # Limitless Exchange Trading API


    *Production-ready API for prediction market trading, portfolio management,
    and market data*


    > 🎯 **Quick Navigation**: [Authentication](#tag/authentication) |
    [Markets](#tag/markets) | [Trading](#tag/trading) |
    [Portfolio](#tag/portfolio)


    ---
      


    ## 🚀 Quick Start


    Choose your preferred programming language for complete end-to-end
    implementation:


    ### Overview


    The Limitless Exchange API offers both REST and WebSocket integration:


    **REST API (Trading)**:

    1. **🔐 Authentication**: Use API key for all programmatic access

    2. **📊 Fetch Market Data**: Get market info including venue contract
    addresses (once per market)

    3. **📋 Order Creation**: Build and sign orders using EIP-712 structured
    data

    4. **🚀 Order Submission**: Submit signed orders and receive confirmations


    **WebSocket API (Real-Time Data)**:

    1. **🔌 Connection**: Connect to `/markets` namespace for real-time updates

    2. **📊 Subscriptions**: Subscribe to market prices and position changes

    3. **📡 Events**: Handle live market data and transaction updates


    ### 🔐 Authentication for API Users


    > **⚠️ DEPRECATION NOTICE**: Cookie-based session authentication is
    deprecated and will be removed within weeks. Please migrate to API keys
    immediately.


    | Method | Header | Status |

    |--------|--------|--------|

    | **API Key** | `X-API-Key: lmts_...` | ✅ Required for programmatic access |

    | Cookie Session | `Cookie: limitless_session=...` | ⚠️ Deprecated (removal
    imminent) |


    **Getting an API Key**


    API keys can only be created via the Limitless Exchange UI:

    1. Log in to [limitless.exchange](https://limitless.exchange) using your
    wallet

    2. Click your profile menu (top right)

    3. Select "Api keys"

    4. Generate a new key


    **Using Your API Key**


    Include in all requests via the `X-API-Key` header:


    ```bash

    # REST API

    curl -H "X-API-Key: lmts_your_key_here"
    https://api.limitless.exchange/markets


    # WebSocket - pass X-API-Key header during connection handshake

    ```


    ### Migration from Cookie to API Key


    If you're currently using cookie-based authentication, migrate by:


    1. **Generate an API key** via the UI (profile menu → Api keys)

    2. **Replace cookie header** with API key header:


    ```diff

    # Before (deprecated)

    - Cookie: limitless_session=your_session_token


    # After

    + X-API-Key: lmts_your_key_here

    ```


    3. **Remove session management code** - no more login flow or cookie
    handling needed


    ### Important: Venue System for CLOB Markets


    CLOB markets use a **venue system** where each market is associated with
    specific contract addresses. Before placing orders:


    1. **Fetch market data once**: `GET /markets/:slug` returns venue
    information

    2. **Use venue.exchange**: This is the `verifyingContract` for EIP-712 order
    signing

    3. **Cache the venue**: Venue data is static per market - fetch once and
    reuse


    **Sample venue response:**

    ```json

    {
      "venue": {
        "exchange": "0xA1b2C3...",
        "adapter": "0xD4e5F6..."
      }
    }

    ```


    ### Required Approvals


    Before trading, set up token approvals based on order type:


    | Order Type | Market Type | Approve To |

    |------------|-------------|------------|

    | BUY | All CLOB | USDC → `venue.exchange` |

    | SELL | Simple CLOB | CT → `venue.exchange` |

    | SELL | NegRisk/Grouped | CT → `venue.exchange` AND `venue.adapter` |


    ### Checksummed Addresses


    All addresses must use **checksummed format** (EIP-55 mixed-case):

    - Authentication: `x-account` header

    - Orders: `maker` and `signer` fields

    - Example: `0x5aAeb6053F3E94C9b9A09f33669435E7Ef1BeAed`


    ### Implementation Guides


    **[🐍 Python Quick Start](#description/-python-quick-start)**

    - REST API: eth-account, requests, and web3.py libraries

    - WebSocket: python-socketio, asyncio integration


    **[☕ Java Quick Start](#description/-java-quick-start)**  

    - REST API: Web3j, OkHttp3, and Jackson libraries


    **[📦 Node.js/TypeScript Quick
    Start](#description/-nodejs-typescript-quick-start)**

    - REST API: viem, ethers, and cross-fetch libraries

    - WebSocket: socket.io-client for real-time trading

    - Full TypeScript support with end-to-end examples


    **[🔌 WebSocket Integration](#description/-websocket-integration)**

    - Real-time market data and position updates

    - Production-ready Python client with authentication


    ---
      


    ## 🐍 Python Quick Start


    Complete end-to-end Python implementation for Limitless Exchange API
    integration.
      


    ### 🐍 Python E2E Order Creation Guide


    Complete Python implementation guide is being loaded from external
    documentation...


    **Guide Contents:**

    - 🔐 Complete authentication flow with eth-account

    - 📋 Order construction with Web3.py calculations

    - ✍️ EIP-712 structured data signing

    - 🚀 Order submission with requests library

    - ⚠️ Comprehensive error handling

    - 🛠️ Production deployment considerations


    *For the complete Python guide, ensure the file is available at
    docs/scripts-samples/python-e2e-order-creation.md*
        


    ## ☕ Java Quick Start


    Complete end-to-end Java implementation for Limitless Exchange API
    integration.
      


    ### ☕ Java E2E Order Creation Guide


    Complete Java enterprise implementation guide is being loaded from external
    documentation...


    **Guide Contents:**

    - 🔐 Complete authentication flow with Web3j

    - 📋 Order construction with BigInteger precision

    - ✍️ EIP-712 structured data signing

    - 🚀 Order submission with OkHttp3

    - ⚠️ Enterprise error handling patterns

    - 🏗️ Production Maven project structure


    *For the complete Java guide, ensure the file is available at
    docs/scripts-samples/java-e2e-order-creation.md*
        


    ## 📦 Node.js/TypeScript Quick Start


    Complete end-to-end Node.js/TypeScript implementation for trading and
    WebSocket subscriptions.
      


    ### 📦 Node.js/TypeScript Trading & WebSocket Guide


    Complete Node.js/TypeScript implementation guide is being loaded from
    external documentation...


    **Guide Contents:**

    - 🔐 **Authentication**: Wallet-based auth with ethers and viem

    - 📋 **Order Creation**: EIP-712 signing with viem WalletClient

    - 🚀 **Order Submission**: REST API integration with cross-fetch

    - 🔌 **WebSocket Subscriptions**: socket.io-client for real-time updates

    - 📊 **Market Data**: AMM prices and CLOB orderbook subscriptions

    - ⚠️ **Type Safety**: Full TypeScript support with proper types

    - 🛠️ **Production Ready**: Complete end-to-end working example


    **Key Features:**

    - **Combined Subscriptions**: Subscribe to both AMM and CLOB markets
    simultaneously

    - **Authentication Flow**: Complete wallet-based authentication with session
    management

    - **Trading Integration**: Place orders and receive real-time updates

    - **TypeScript First**: Type-safe implementation with proper interfaces


    *For the complete Node.js guide, ensure the file is available at
    docs/scripts-samples/node-socket-trading-and-subscribe.md*
        


    ## 🔌 WebSocket Integration


    Real-time market data and position updates using WebSocket connections.
      


    ### 🔌 WebSocket Real-Time Integration Guide


    Complete WebSocket implementation guide is being loaded from external
    documentation...


    **Guide Contents:**

    - 🔌 **WebSocket Connection**: python-socketio client with async support

    - 🔐 **Authentication**: JWT session cookie integration

    - 📊 **Market Subscriptions**: Real-time price updates and position changes

    - ⚡ **Event Handling**: Comprehensive event processing patterns

    - 🔄 **Auto-Reconnection**: Production-ready reconnection logic

    - 🛠️ **Error Recovery**: Robust error handling and fallback strategies


    **Key Features:**

    - **Public Mode**: Market price updates without authentication

    - **Authenticated Mode**: Full access to positions and transactions

    - **Multi-Market Support**: Subscribe to multiple markets simultaneously

    - **Production Ready**: Tested patterns for production deployment


    *For the complete WebSocket guide, ensure the file is available at
    docs/scripts-samples/python-socket-subscribe.md*
        
  version: '1.0'
  contact:
    name: API Support
    url: https://limitless.exchange
    email: hey@limitless.network
servers:
  - url: https://api.limitless.exchange
    description: Production API
security: []
tags:
  - name: Authentication
    description: User authentication and session management
  - name: Markets
    description: Browse, search, and analyze prediction markets
  - name: Market Navigation
    description: Navigation tree, market pages, and property filters
  - name: Trading
    description: Create, manage, and cancel orders
  - name: Portfolio
    description: Position tracking, trade history, and performance
  - name: Feed
    description: Public trading activity feeds
paths:
  /markets/{slug}/events:
    get:
      tags:
        - Trading
      summary: Get Finalized Market Trades
      description: >-
        Returns public, finalized MINED CLOB trades newest first. An exact
        market slug selects that market; if no market matches, an exact group
        slug combines all group markets. Stable-slug aliases are not resolved.
        No authentication is required.
      operationId: MarketOrderbookController_getMarketEvents
      parameters:
        - name: page
          required: false
          in: query
          description: One-based page number. Defaults to 1.
          schema:
            type: integer
            minimum: 1
            default: 1
            example: 1
        - name: limit
          required: false
          in: query
          description: Maximum trades per page. Defaults to 100.
          schema:
            type: integer
            minimum: 1
            maximum: 100
            default: 100
            example: 20
        - name: slug
          required: true
          in: path
          description: >-
            Exact market or market-group slug. Market lookup takes precedence;
            stable-slug aliases are not resolved.
          schema:
            type: string
            example: presidential-election-2024
      responses:
        '200':
          description: >-
            Finalized CLOB trade page. A page with no events currently returns
            only `events` and `totalPages`.
          content:
            application/json:
              schema:
                oneOf:
                  - $ref: '#/components/schemas/MarketEventsResponse'
                  - $ref: '#/components/schemas/EmptyMarketEventsResponse'
        '400':
          description: Invalid or unknown query parameter
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ValidationErrorResponse'
        '404':
          description: >-
            Slug matches neither an exact market nor an exact market group. This
            response is publicly cacheable for 5 minutes with a further 5-minute
            stale-while-revalidate window.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorMessageResponse'
        '500':
          description: Market trade activity lookup failed unexpectedly
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorMessageResponse'
      security: []
components:
  schemas:
    MarketEventsResponse:
      type: object
      properties:
        events:
          type: array
          items:
            $ref: '#/components/schemas/MarketEvent'
        limit:
          type: integer
          minimum: 1
          maximum: 100
        page:
          type: integer
          minimum: 1
        totalPages:
          type: integer
          minimum: 1
        totalRows:
          type: integer
          minimum: 1
      additionalProperties: false
      required:
        - events
        - limit
        - page
        - totalPages
        - totalRows
    EmptyMarketEventsResponse:
      type: object
      properties:
        events:
          maxItems: 0
          type: array
          items:
            $ref: '#/components/schemas/MarketEvent'
        totalPages:
          type: number
          enum:
            - 0
      additionalProperties: false
      description: Current reduced response for an empty or out-of-range event page.
      required:
        - events
        - totalPages
    ValidationErrorResponse:
      type: object
      properties:
        message:
          type: array
          items:
            $ref: '#/components/schemas/ValidationErrorItem'
        error:
          type: string
          enum:
            - Bad Request
        statusCode:
          type: number
          enum:
            - 400
      additionalProperties: false
      required:
        - message
        - error
        - statusCode
    ErrorMessageResponse:
      type: object
      properties:
        message:
          type: string
      additionalProperties: false
      required:
        - message
    MarketEvent:
      type: object
      properties:
        createdAt:
          type: string
          format: date-time
          description: Trade creation time.
        makerAmount:
          type: string
          pattern: ^[0-9]+$
          description: >-
            Trade collateral cost in raw 6-decimal units. Currently equal to
            takerAmount.
          example: '1000000'
        matchedSize:
          type: string
          pattern: ^[0-9]+$
          description: Taker fill size in raw 6-decimal position-token units.
          example: '2000000'
        price:
          type: number
          minimum: 0
          maximum: 1
          description: Weighted average fill price.
          example: 0.5
        profile:
          $ref: '#/components/schemas/MarketEventProfile'
        side:
          type: number
          enum:
            - 0
            - 1
          description: 'Taker side: 0 = BUY, 1 = SELL.'
          example: 0
        takerAmount:
          type: string
          pattern: ^[0-9]+$
          description: >-
            Trade collateral cost in raw 6-decimal units. Currently equal to
            makerAmount.
          example: '1000000'
        title:
          type: string
          description: Title of the market where the trade occurred.
        tokenId:
          type: string
          pattern: ^[0-9]+$
          description: Taker position-token ID.
        txHash:
          type: string
          description: Settlement transaction hash.
      additionalProperties: false
      description: >-
        One finalized MINED CLOB trade, attributed to its taker when a public
        profile is available.
      required:
        - createdAt
        - makerAmount
        - matchedSize
        - price
        - side
        - takerAmount
        - title
        - tokenId
        - txHash
    ValidationErrorItem:
      type: object
      properties:
        field:
          type: string
          example: orderIds
        message:
          type: string
          example: orderIds should not be empty
      additionalProperties: false
      required:
        - field
        - message
    MarketEventProfile:
      type: object
      properties:
        username:
          type: string
          description: Public username.
        displayName:
          type: string
          description: Public display name.
        pfpUrl:
          type: string
          nullable: true
          description: Public profile-picture URL.
        socialUrl:
          type: string
          nullable: true
          description: Public social-profile URL.
        rankName:
          type: string
          enum:
            - Bronze
            - Silver
            - Gold
            - Platinum
            - Diamond
          nullable: true
          description: Public rank, or null when no rank is assigned.
      description: >-
        Approved public taker attribution. Additional runtime properties are
        permitted for response compatibility.
      required:
        - username
        - displayName
        - pfpUrl
        - socialUrl
        - rankName

````