How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Pred Market Discovery API

Market information and discovery (public; no auth). Use this section to understand **parent_market_id** and **market_id** and to list all markets.## What are parent_market_id and market_id?- **parent_market_id:** Identifies a parent market (e.g. a fixture or event). It groups one or more child markets. Order and orderbook paths are scoped by parent (e.g. `GET /api/v1/order/{parentMarketID}/orderbook/{marketID}`). Cancel and open-orders endpoints are also per parent.- **market_id:** Identifies a specific (child) market within a parent (e.g. one outcome: Team A, Team B, or Draw). Used in place order body (`market_id`), orderbook path (`marketID`), and cancel body. Each parent can have multiple child markets; each child has its own `market_id`.You need both when placing orders (parent in the path, market_id in the body) and when fetching orderbooks (parent and market in the path).## Getting parent_market_id and market_id**Get all markets:** Call `GET /api/v1/market-discovery/discover?verbose=true&limit=50&offset=0`, then continue paging with `offset += limit` until all `data.total` rows are consumed. `verbose=true` is required for the trading-critical fields that non-verbose responses can omit: `parent_market_data.parent_market_id`, `parent_market_data.contract_address`, `parent_market_data.parent_market_type`, `parent_market_data.parent_market_family`, and fixture fields such as `fixture.fixture_id` and `fixture.game_start_time`. The response shape is `data.parent_markets_list[]`, where each entry has `parent_market_data`, optional `fixture`, optional `team_data`, and child `markets[]`.**Runtime eligibility used by market-maker style clients:** first filter your own configured markets to `active`; then require the discovered parent row to have `parent_market_data.status == "active"`; then require the specific child row in `markets[]` to have `status == "active"`. Child statuses such as `resolved` or `redeemed` are terminal and should be treated as not quote/trade eligible. For market makers, also validate the Polymarket/PRED orderbook or external liquidity source for the child before enabling quoting.**Important field mapping:** use `parent_market_data.parent_market_id` as the parent path parameter, `markets[].market_id` as the child `market_id`, `parent_market_data.contract_address` as the EIP-712 `verifyingContract`, `parent_market_data.parent_market_family` for family-level config, `parent_market_data.parent_market_type` to distinguish fixtures from generic/futures markets, and `fixture.game_start_time` for fixture/live-window logic.To get details for a single parent (including its child market IDs and statuses), call `GET /api/v1/market-discovery/parents/{parentMarketID}`.## Endpoints- `GET /api/v1/market-discovery/discover?verbose=true&limit=50&offset=0` — paginated discovery feed for parent markets, child markets, contract addresses, market family/type, and fixture context.- `GET /api/v1/market-discovery/parents/{parentMarketID}` — details for one parent, including child markets.

Pred Market Discovery API is one of 7 APIs that Pred publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Market Discovery. The published artifact set on APIs.io includes an OpenAPI specification, an API reference, and authentication docs.

This API exposes 2 operations across 2 paths, and defines 5 schemas. It is described by OpenAPI 3.2.0, at version 1.0.0.

Requests are made against 2 base URLs: https://testnet.pred.app, https://www.pred.app.

2 operations 2 paths 5 schemas 2 GET

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0.0
Base URL
https://www.pred.app
Authentication
HTTP Bearer
Resource Areas
1

Authentication & Security 1

Pred Market Discovery API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (JWT) (BearerAuth).

  • BearerAuth — JWT access token from login endpoint

Paths & Operations 2

Across 2 paths, the API surfaces 2 operations — 2 GET. Each is listed below with its method, path, parameters, and response codes.

Market Discovery 2

Market information and discovery (public; no auth). Use this section to understand parentmarketid and marketid and to list all markets. What are parentmarketid and marketid? - par…

GET
/api/v1/market-discovery/discover
Get market discovery feed
getAllParentMarkets 3 params → 200500
GET
/api/v1/market-discovery/parents/{parentMarketID}
Get parent market details
getParentMarketDetails 1 param → 200404

Schemas 5

The contract defines 5 schemas that model the data the API accepts and returns. The most detailed are MarketDiscoveryDiscoverItem (5 properties), Error (3 properties), ErrorResponse (3 properties), MarketDiscoveryDiscoverResponse (1 property). Each schema is shown below with its type and property counts.

MarketDiscoveryDiscoverItem
object
5 properties
ParentMarketDetailsResponse
object
1 property
MarketDiscoveryDiscoverResponse
object
1 property
ErrorResponse
object
3 properties
Error
object
3 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

pred-market-discovery-api-openapi.yml Raw ↑

Other APIs Pred publishes across the network.

Pred Authentication API
Pred Orders API
Pred Overview API
Pred Portfolio API
Pred User API
Pred WebSocket API
Where this information came from

This is an independent, third-party profile of Pred Market Discovery API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.