> ## 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 Details

> Retrieves market or group data using either an Ethereum address or a slug identifier

<Tip>
  This endpoint returns **venue data** (`venue.exchange` and `venue.adapter`) needed for [EIP-712 order signing](/developers/eip712-signing). Fetch once per market and cache — venue data is static.
</Tip>

<Info>
  **Outcome index convention.** On a resolved market the response carries `winningOutcomeIndex`, an index into the fixed `outcomeTokens: ['Yes', 'No']` array:

  * `winningOutcomeIndex: 0` — **YES** resolved
  * `winningOutcomeIndex: 1` — **NO** resolved
  * `null` — not yet resolved

  The same mapping applies anywhere this field appears (portfolio positions, feed events). For negrisk groups, the winning index lives on the individual sub-market that resolved YES, not on the group object.
</Info>

<Note>
  **Market volume.** The response includes lifetime trading volume in the `volume` field (raw, base units) and `volumeFormatted` (human-readable USDC). The API does not expose a rolling 24-hour volume field; for time-windowed activity, derive it client-side from [Get Feed Events](/api-reference/markets/feed-events) (filter trade events by timestamp).
</Note>

<Note>
  **Market `status` values.** The response's `status` field is one of:

  * `FUNDED` — the market is live and accepting trades. The default for active markets.
  * `LOCKED` — trading is paused on the market: orders cannot be placed or filled, but existing positions remain. A market typically enters `LOCKED` shortly before resolution (after the deadline, while the winning outcome is being determined) or when an operator manually halts it. The market resumes as `FUNDED` if unlocked, or transitions to `RESOLVED` once the outcome is set.
  * `RESOLVED` — the winning outcome is known. `winningOutcomeIndex` is populated and winners can redeem their CTF positions. See [Lifecycle after a trade](/developers/programmatic-api#lifecycle-after-a-trade).
  * `FUNDED_FLAGGED` — the market is live but flagged for review (for example, pending resolution clarification). Treat it as `FUNDED` for trading purposes unless your integration wants to surface the flag to users.
  * `DRAFT` — the market exists but has not been funded yet and is not tradeable.

  Treat any unrecognized future value defensively rather than assuming the market is tradeable.
</Note>

<Note>
  **Taker delay.** A CLOB market's `settings` object carries `takerDelayMs` — the market's taker delay in milliseconds (`0` = none, the default). When it is greater than `0`, marketable (taker) orders on this market are briefly held before the matching engine fills them and order submission becomes asynchronous (the create-order response returns `settlementStatus: "DELAYED"` with an `eligibleAt`; track the fill over [`subscribe_order_events`](/developers/websocket-events#subscribing-to-order-events)). Read `settings.takerDelayMs` to detect delay-enabled markets before placing taker orders. `postOnly` (maker) orders are never delayed.
</Note>


## OpenAPI

````yaml GET /markets/{addressOrSlug}
openapi: 3.0.0
info:
  title: Limitless Exchange API
  description: >-
    Production-ready REST API for prediction market trading, portfolio
    management, and market data on Limitless Exchange (Base L2).
  version: '1.0'
  contact:
    name: API Support
    url: https://limitless.exchange
    email: help@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: API Tokens
    description: Scoped API token management for partner integrations
  - name: Partner Accounts
    description: Sub-account creation and allowance recovery for partner integrations
  - name: System
    description: Public API state and availability information
paths:
  /markets/{addressOrSlug}:
    get:
      tags:
        - Markets
      summary: Get Market Details
      description: >-
        Retrieves market or group data using either an Ethereum address or a
        slug identifier
      operationId: MarketController_find
      parameters:
        - name: addressOrSlug
          required: true
          in: path
          description: Market/group address (0x...) or slug identifier (my-market-name)
          schema:
            example: crypto-predictions-2025
      responses:
        '200':
          description: Market or group details with pricing and volume data
          content:
            application/json:
              schema:
                oneOf:
                  - $ref: e1885eee-8b31-48fb-9ab9-7e3681826984
                    description: CLOB market with position IDs and trading data
                  - $ref: c83b7c68-4cc2-4cfe-bb87-d5b1681f9f2e
                    description: NegRisk group with nested markets array
                  - $ref: 46e63407-7731-4c42-8165-fb90ae84b228
                    description: AMM market with liquidity and volume data
        '404':
          description: Market or group not found
        '500':
          description: Server error when retrieving market/group data

````