Market Listings

Prediction Market Listings

FinFeedAPI provides a standardized API for discovering prediction markets available on supported exchanges through a consistent market discovery interface.

Retrieve market identifiers, titles, descriptions, outcomes, prices, statuses, and exchange metadata before accessing latest market activity, historical datasets, OHLCV data, or order books. Market listings are available through REST, MCP, and JSON-RPC, providing a unified integration layer across multiple prediction market exchanges.

Start with Free CreditsRead the Documentation

What Are Prediction Market Listings?

Prediction market listings describe the individual contracts available for trading on a prediction market exchange.

Each listing represents a specific market outcome and includes the metadata required to identify, display, and query that market. Depending on the exchange, listings may represent binary outcomes, multi-outcome markets, or other supported contract structures.

Applications use market listings as the entry point into prediction market data. Before retrieving trades, quotes, order books, or OHLCV data, developers first discover the available markets on an exchange and obtain their canonical market_id values.

FinFeedAPI provides a unified market discovery API that standardizes this process across supported prediction market exchanges. Developers can enumerate available markets, retrieve descriptive metadata, and use the returned identifiers consistently throughout the Prediction Markets API.

Why Use Prediction Market Listings?

Market discovery is the foundation of every prediction market integration. Applications need reliable market identifiers before requesting market activity, historical trades, order book snapshots, or OHLCV timeseries.

Since exchanges continuously introduce new markets while existing contracts resolve or become inactive, maintaining local market catalogs manually quickly becomes difficult.

Developers commonly use market listings to:

  • discover prediction markets available on a specific exchange
  • retrieve canonical market identifiers
  • display market titles and descriptions
  • organize markets by exchange
  • synchronize newly available markets
  • identify active prediction markets
  • prepare downstream requests for activity, OHLCV, and order book data

Using a centralized market discovery API allows applications to keep market catalogs synchronized without relying on manually maintained datasets.

What's Included in Prediction Market Listings?

Every market object returned by the Prediction Markets API contains the metadata required to identify and describe a prediction market outcome.

FieldDescription
market_idCanonical market identifier used throughout the Prediction Markets API.
titleHuman-readable market title.
descriptionDescription explaining the market and its resolution criteria.
outcome_nameOutcome represented by the market entry.
priceCurrent market price for the outcome.
statusCurrent market status.
exchange_idExchange where the market is listed.
outcome_typeType of market outcome, such as binary or other supported formats.

Together, these fields provide the metadata needed to identify prediction markets, present them to users, and continue into market-level datasets throughout the FinFeedAPI ecosystem.

Related Endpoints

Market listings are one component of the FinFeedAPI Prediction Markets API. Once a market is identified, developers can use related endpoints to retrieve the surrounding data. Related endpoints include:

  • Market Activity
  • Order Book Data
  • OHLCV Data

Together, these endpoints create a complete workflow for working with normalized prediction market data.

Applications can begin with exchange discovery, move into market discovery through market listings, and then extend into current activity, order book snapshots, and historical OHLCV data. This structure makes it easier to build prediction market dashboards, trading systems, quantitative research tools, AI agents, and market monitoring applications without integrating each prediction market venue separately.

Available REST Endpoints

The Prediction Markets API provides two complementary endpoints for market discovery: complete market objects for browsing and catalogs, and a lightweight list of currently active market identifiers.

List Prediction Market Listings

Returns complete market objects for a selected prediction market exchange. This endpoint returns descriptive market metadata suitable for applications that need to browse markets, build searchable directories, synchronize catalogs, or display prediction market information to users. Results support pagination through limit and page parameters.

Response includes
  • market identifier
  • title
  • description
  • outcome name
  • current price
  • market status
  • exchange identifier
  • outcome type
Parameters:exchange_id • limit • page

List Active Prediction Market IDs

Returns the identifiers of currently active markets for a selected exchange. Unlike the market history endpoint, this endpoint returns only market identifiers derived from recent quotes and transactions rather than complete market objects. It provides a lightweight discovery mechanism when applications only require valid market identifiers before requesting additional datasets.

Response includes
  • active market_id values
Parameters:exchange_id • limit • page

How Market Listings Fit Into the FinFeedAPI Ecosystem

Market discovery follows exchange discovery within the Prediction Markets API workflow. Applications first identify a supported exchange, retrieve available market listings, and then use the returned market_id values to access market activity, historical datasets, OHLCV candles, and order book data.

Typical integration workflow

  1. 1Retrieve supported exchanges
  2. 2Select a prediction market exchange
  3. 3Retrieve market listings
  4. 4Select a market_id
  5. 5Retrieve activity, OHLCV, or order book data

This workflow separates exchange discovery from market discovery while providing stable identifiers for every downstream API request.

Example API Request

Retrieve market listings for a supported prediction market exchange.

bash
curl -X GET \
  "https://api.prediction-markets.finfeedapi.com/v1/markets/POLYMARKET/history" \
  -H "Authorization: YOUR_API_KEY"
json
[
  {
    "market_id": "WILL-TRUMP-SELL-10K-25K-GOLD-CARDS-IN-2025_YES",
    "title": "Will Trump sell 10k-25k Gold Cards in 2025?",
    "description": "Resolves based on official reporting by the Trump Administration.",
    "outcome_name": "Yes",
    "price": 0.12,
    "status": "Open",
    "exchange_id": "POLYMARKET",
    "outcome_type": "Binary"
  }
]

The response provides the market metadata required to identify prediction markets and continue into additional market-level datasets.

REST, MCP, and JSON-RPC Access

Prediction market listings are available through every FinFeedAPI interface. Regardless of the interface, applications receive the same standardized market metadata.

MCP Server

The hosted Prediction Markets MCP server exposes market discovery through the markets_get_history and markets_get_active tools, using the X-APIKey header. Developers can enumerate active markets or retrieve complete market metadata without custom integrations.

json
{
  "mcpServers": {
    "FinFeedAPI-Prediction-Markets": {
      "url": "https://api.prediction-markets.finfeedapi.com/mcp",
      "headers": {
        "X-APIKey": "YOUR_API_KEY_HERE"
      }
    }
  }
}

Compatible with Cursor, Claude Desktop, and other MCP-enabled AI applications.

JSON-RPC

Developers using JSON-RPC can access market listings through the production proxy at https://api.prediction-markets.finfeedapi.com/jsonrpc.

JSON-RPC acts as a thin transport wrapper over the REST API. Set method to v1/markets/{exchange_id}/history for complete market objects, or v1/markets/{exchange_id}/active for active market identifiers, and pass parameters through params. Authentication, identifiers, and response structure stay identical to REST.

Common Integration Patterns

Prediction market listings are typically retrieved immediately after exchange discovery and before requesting market-level datasets.

WorkflowHow market listings are used
Market DirectoriesBuild searchable catalogs of prediction markets available on each supported exchange.
Market SelectionPopulate user interfaces that allow browsing available prediction markets before retrieving latest data.
Market SynchronizationRefresh local market catalogs as exchanges introduce new contracts or existing markets resolve.
Market ValidationVerify market_id values before requesting market activity, OHLCV data, or order books.
Analytics PipelinesBuild internal datasets of available prediction markets for downstream processing.
Trading & Monitoring SystemsDiscover active markets before requesting market activity or monitoring liquidity.
Market Listings

Start Building with Prediction Market Listings

Discover prediction markets across supported exchanges through one standardized API.

Retrieve market identifiers, synchronize market catalogs, and use consistent market metadata as the foundation for integrating market activity, OHLCV, order books, and other prediction market datasets through REST, MCP, or JSON-RPC.

Start with Free CreditsRead the Documentation