Fixtures (browsing markets)

Before you can submit an order, you need a contractId. The three endpoints in this doc walk you down the fixtures hierarchy until you have one.

Auth: ISV-only JWT (see Authentication). These aren't user-scoped, so no sub or subsig needed.


1. The hierarchy

Tournament  (e.g. "NBA")   — also carries its sport in tournament.sport
   └─ Sport event  (e.g. "Detroit Pistons at Cleveland Cavaliers")
       └─ Market   (e.g. "Moneyline")
           └─ Selection (= outcome) — each has a contractId

A contract is the unique combination of (event, market, outcome, strike). Its contractId is the hash you'll pass to the order endpoints. See Market Orders (single-contract trades) and Parlays (2–12 leg trades).

The usual drill-down: pick a tournament, list its events, list the markets on an event, pick a selection, grab the contractId.

A few mapping notes if you're coming from another platform's vocabulary:

  • There is no GET /sports endpoint. Tournaments are the top of the API hierarchy. Sport is an attribute on the tournament (tournament.sport: { id, name }), not a separate resource. If you want a "browse by sport" view, build the sport list client-side by deduplicating tournament.sport.id across the /tournaments response.
  • Mapping to a Plaee-style schema: ProphetX tournament.sport ≈ Plaee's category; ProphetX tournament ≈ Plaee's sub-category. ProphetX sport event ≈ Plaee's event. Markets and outcomes line up directly.
  • Each outcome is its own contract. For binary markets, the "yes" side and the "no" side have different contractIds. You pick which side the user is taking when you submit the order; there's no side flag on the order body.

2. GET /private/v1/tournaments

QueryDefaultEffect
hasActiveEventsunsetSet to true to filter to tournaments that have at least one currently-active event.

Response (TournamentsResponse): the response is { "tournaments": [...] }. A trimmed sandbox example showing the first three entries from a hasActiveEvents=true query (the full list returned ten):

{
  "tournaments": [
    {
      "id": 31,
      "name": "NFL",
      "sport": { "id": 16, "name": "American Football" },
      "category": { "id": 0, "name": "N/A", "countryCode": "N/A" },
      "updatedAt": "2024-07-12T02:00:27.859Z"
    },
    {
      "id": 53,
      "name": "FIFA World Cup",
      "sport": { "id": 1, "name": "Soccer" },
      "category": { "id": 0, "name": "N/A", "countryCode": "N/A" },
      "updatedAt": "2026-05-11T15:15:19.506Z"
    },
    {
      "id": 109,
      "name": "MLB",
      "sport": { "id": 2, "name": "Basketball" },
      "category": { "id": 0, "name": "N/A", "countryCode": "N/A" },
      "updatedAt": "2024-07-12T02:00:27.296Z"
    }
  ]
}

Sandbox frequently returns category as the N/A placeholder; production data is more populated. Don't rely on category for routing — use sport.name and name.


3. GET /private/v1/sport-events

QueryRequiredEffect
tournamentIdone of theseFilter to a single tournament.
eventIdsone of theseComma-separated list of event IDs.

You typically call this after picking a tournament. The full response is { "sportEvents": [...] }. Per-event shape (SportEvent) — a real sandbox row for an NBA matchup from ?tournamentId=132:

{
  "eventId": 20023797,
  "name": "Detroit Pistons at Cleveland Cavaliers",
  "displayName": "Detroit Pistons at Cleveland Cavaliers",
  "liveDisabled": false,
  "status": "not_started",
  "type": "",
  "subType": "",
  "scheduled": "2026-05-15T23:00:00Z",
  "updatedAt": "2026-05-14T03:29:13.952Z",
  "sportName": "Basketball",
  "tournamentId": 132,
  "tournamentName": "NBA",
  "competitors": [
    { "id": 20000012, "name": "Cleveland Cavaliers", "displayName": "Cleveland Cavaliers", "abbreviation": "CLE", "country": "", "side": "home" },
    { "id": 20000014, "name": "Detroit Pistons", "displayName": "Detroit Pistons", "abbreviation": "DET", "country": "", "side": "away" }
  ]
}

Things to notice from real data: type and subType are often empty strings rather than null; country may be empty.

status is one of not_started, live, suspended, ended, closed, cancelled, interrupted, postponed, abandoned, delayed — that's the full list, not an abbreviated sample. If you're filtering which events to show or trade on, build a deny-list of terminal/non-tradeable statuses, not an allow-list of the ones you expect — a partner that allow-listed only not_started/live silently dropped every event that went interrupted or suspended, which are both still-live, still-relevant states, not something to filter out.

This endpoint returns a deliberately filtered subset, not a mirror of prophetx.co. An event visible to consumers on the main platform can be absent here for any of: it isn't yet flagged "booked" for partner/trading purposes (a separate state from being scheduled or live on the consumer site); it's a live event explicitly flagged not available for partner trading; or your ISV account has a competitor-level exclusion applied. If you see an event on prophetx.co that doesn't show up here, that's most likely one of these — not a sync delay or a bug — and worth checking with your ProphetX contact if it's unexpected.

3.1 Which events are listed

This endpoint is a tradable-now view, not a catalog of every event we know about. An event is included only while all of these hold:

  • status is not_started or live
  • the event is booked by our data feed (we have markets for it)
  • if live, in-play trading is enabled for it (liveDisabled is false)

An event leaves the list as soon as any of those stop being true. Some of those exits are permanent (ended, closed, cancelled, abandoned) and some are temporary (suspended, postponed, delayed, interrupted, the feed un-booking it, or a live event having in-play trading switched off). Temporary exits reverse, which is why an event can disappear from one call and be back on the next.

Don't treat absence as closed. The listing tells you only that the event is not tradable at this moment. If you are mirroring the catalog, keep your last known record for an event that goes missing and mark it "not tradable" rather than deleting it. The authoritative close signal is the SportEventEvent webhook with status of ended, closed, cancelled or abandoned (see Webhooks (push events) section 4.6). Only that webhook, or a GET /sport-events?eventIds= call that returns the event in a terminal status, confirms it is over.

Closed and settled events are not retained in the listing for any grace period today. If your reconciliation needs that, tell us; it is on the backlog but not scheduled.


4. GET /private/v1/markets

QueryRequiredEffect
eventIdsyesComma-separated event IDs.
typesnoComma-separated market types, e.g. moneyline,total.
subTypesnoComma-separated market sub-types.

Response (MarketsResponse): the response is { "markets": [{ "eventId": ..., "markets": [...] }, ...] } — one entry per event you queried, each carrying its own markets array. Below is a real moneyline market returned from a live ATP Monte Carlo singles match, showing the typical shape of a market with partial liquidity (one side has a resting price, the other side is empty):

{
  "id": 186,
  "name": "Moneyline",
  "type": "moneyline",
  "subType": "moneyline",
  "status": "active",
  "favorite": false,
  "categoryName": "Game Lines",
  "groupName": "",
  "strike": 0,
  "totalQuantity": 10,
  "totalFilled": 0,
  "playerId": 0,
  "updatedAt": "2026-04-03T19:32:34.503Z",
  "selections": [
    [
      {
        "outcomeId": 4,
        "contractId": "2d179d1578e669e97a2e57735f0cbef8",
        "name": "Alexander Shevchenko",
        "displayName": "Alexander Shevchenko",
        "displayPrice": "",
        "displayStrike": "",
        "price": 0,
        "quantity": 0,
        "strike": 0,
        "marketId": 0,
        "competitorId": 1700000826,
        "value": 0,
        "updatedAt": "1970-01-01T00:00:00Z"
      }
    ],
    [
      {
        "outcomeId": 5,
        "contractId": "05d1b7df6b4a41016d545c3944e754e0",
        "name": "Andrea Pellegrino",
        "displayName": "Andrea Pellegrino +100",
        "displayPrice": "+100",
        "displayStrike": "",
        "price": 100,
        "quantity": 10,
        "strike": 0,
        "marketId": 186,
        "competitorId": 1700000749,
        "value": 10,
        "updatedAt": "2026-04-29T07:39:08.945Z"
      }
    ]
  ]
}

Fields worth knowing:

  • selections is a list of lists — each inner array holds the variants for one outcome. Most simple markets give you one entry per outcome, but you should iterate the outer list and then the inner list rather than assuming a flat array.
  • contractId is the thing you trade — pass it to /market-orders or /parlays.
  • displayPrice and displayStrike are strings (e.g. "+100", "-110", or "" when no price exists). price is a number for the same value.
  • price is the raw American price of the best resting order on that side, before the ISV fee. adjustedPrice is currently always null on this endpoint in every environment, so don't depend on it here. For a fee-adjusted price use POST /market-orders/estimate (expectedAveragePriceAdjusted) at quote time, or the per-ISV adjusted price carried on the ContractEvent and MarketSelectionEvent webhooks. Populating adjustedPrice on this endpoint is tracked internally; the field will stay in the schema.
  • quantity and value are not the same thing. quantity is the resting stake on the other side of this selection — 0 means no resting orders on that side yet. value is that same liquidity scaled by odds, and is the number that actually reflects what you can take at this price — prefer value over quantity when sizing against available liquidity. See the Selection field table.
  • strike is the handicap/spread value (0 for moneyline).
  • An unpriced selection shows displayPrice: "", price: 0, quantity: 0, marketId: 0, and updatedAt: "1970-01-01T00:00:00Z" — i.e. the contract exists but has no resting liquidity. Don't show 0 as -0/+0 prices to your user; treat the empty displayPrice as "no price yet".
  • Pre-game events (e.g. an NBA game scheduled for tomorrow) often return the full markets catalog with every selection in this unpriced state. As the event approaches start time, sides get populated.

Pushable vs Not Pushable markets

From November 30, 2026 every market falls into one of two settlement classes, which decides what a user gets back on a tie or a void:

ClassWhich marketsTieCancellation / void
Not Pushablemoneyline, spread, total on any period (full game, halves, quarters, innings, team totals) and game props (both teams to score, game to go to overtime, etc.)Settles at $0.50 per contractSettles at Fair Market Value when the disruption became known
PushablePlayer props — markets on one player's performance in a single game or event, including golf player propsCost returned (traditional push)Cost returned

Both classes post to the ledger as PUSH / VOID, so the class only changes the amount — see Wallets. Pushable markets are the platform's high-risk markets, which is why a cash-out on them locks the profit portion until settlement (highRisk / lockedAmount on the Positions responses).

There is no pushable or highRisk flag on the Market object yet. The practical rule is the market subType: a subType beginning with player_ is a player prop and therefore Pushable; anything else is Not Pushable. The only place the platform states the designation explicitly today is the highRisk field on POST /positions/quote and POST /positions/close. ProphetX will publish the official market list before the change takes effect; if your UI needs the designation on the market payload, ask your integration contact and it can be prioritised.

For markets composed of sub-markets, expect a sibling marketContracts array on the parent market carrying nested Market objects with the same shape (e.g. spread levels stacked under a parent handicap market). Same shape as Market, so recurse or flatten as needed.

Markets follow the event. Markets are only returned for events that GET /sport-events would list right now (see 3.1). When an event leaves that list, all of its markets leave this response together, whether or not the individual markets are settled. A market that is still listed carries its own status (active, suspended, settled, ...), so use that field, and the MarketEvent webhook, to track market state rather than the market's presence in the response.

Field-rename heads-up. The Market object was recently renamed on the backend: totalMatched → totalFilled and marketLines → marketContracts. If you're upgrading from an older client that used the pre-rename names, update your model definitions to match.


5. GET /private/v1/sport-events/{eventId}/settlements

Returns every contract on the event that has been settled, with its full settlement history. Use it to reconcile after a webhook gap rather than to poll for results.

{
  "eventId": 1704702441,
  "contracts": [
    {
      "contractId": "8ceba8c6c5c4d3133ed9e178afd6d8d4",
      "marketId": 1700087997,
      "outcomeId": 12,
      "strike": 19.5,
      "settlements": [
        { "result": "push", "timestamp": "2026-10-29T02:12:45Z" }
      ]
    }
  ]
}
  • settlements is oldest first. The last entry is the current result. A resettled contract lists every result it has had.
  • strike is null for markets without a line, such as moneyline.
  • Contracts with no settlement are omitted. An empty list means nothing on the event has needed grading, not that the event is unfinished. See Webhooks (push events) section 4.2 for which contracts never get a settlement.
  • contractId is the same value as GET /private/v1/markets returns and the contract_settlement webhook carries.
  • Rate limited to 10 requests per minute per ISV, and an NBA game returns several thousand rows. Call it per event after a known gap, not on a schedule.
  • Upcoming: the same settled-price field being added to ContractSettlementEvent will appear on each settlements[] entry, carrying the $0.50 or Fair Market Value settlement on Not Pushable markets. Name to be published once live in sandbox; see Webhooks.

6. A typical drill-down

BASE="https://isv-api.sandbox.prophetx.dev/private/v1"

# 1. Find live tournaments (sandbox returned ~10 with hasActiveEvents=true)
curl "$BASE/tournaments?hasActiveEvents=true" -H "Authorization: Bearer $JWT_ISV"

# 2. Enumerate events in one of them — e.g. NBA (tournamentId=132)
curl "$BASE/sport-events?tournamentId=132" -H "Authorization: Bearer $JWT_ISV"

# 3. Pull the markets for an event — e.g. Detroit Pistons @ Cleveland Cavaliers
curl "$BASE/markets?eventIds=20023797&types=moneyline,total" \
  -H "Authorization: Bearer $JWT_ISV"
# Pick a selections[].contractId — now you're ready to submit an order.

7. Pagination

GET /tournaments, GET /sport-events, and GET /markets do not paginate — each call returns the full filtered set in a single response. Filter aggressively (hasActiveEvents=true on tournaments, tournamentId / eventIds on the others, types / subTypes on markets) to keep payloads bounded.


8. Keeping data fresh

These endpoints return snapshots. Don't poll them in a tight loop — the recommended pattern is:

  • Hydrate from the fixtures API at service start, and resync every 5–10 minutes as a safety net.

  • Apply real-time changes from the webhooks: SportEventEvent, TournamentEvent, MarketEvent, and MarketSelectionEvent (the liquidity feed — the orderbook, in other words). See Webhooks (push events).

  • Never infer closure from a resync. An event or market missing from a snapshot means "not tradable right now", not "closed" (see 3.1). Close your records on the SportEventEvent / MarketEvent webhook with a terminal status, or on a GET /sport-events?eventIds= lookup that returns the event in one.

Use the fixtures API for discovery and the periodic backstop, and the webhook for live updates. ProphetX prefers ISVs lean on webhooks instead of polling.


9. Sandbox vs production

The sandbox environment has trading bots posting liquidity, so you can exercise the full order/parlay lifecycle without needing real users on both sides of the book. The catalog itself (sports, tournaments, market types) is similar to production — fixtures you can browse and trade against in sandbox will look very close to what you'll see live.


Did this page help you?