Market detail

GET/api/v1/markets/{marketId}Public

Trading APIprice E4 · size E2 · amount E6 (integers)YES | NO

The path parameter accepts either the engine marketId or the slug. Includes the four resolution fields (winningOutcome / resolvedAtS / disputeWindowEndsAt / engineState): "resolved" is defined as winningOutcome != null, not tradeable == false; whether the dispute window has closed is derived from time and is deliberately not materialised server-side.

Path parameters

marketIdstringpathrequired
Engine market id or slug
Example"mkt-0001"

Response

200Market summary

marketIdstring
Engine market id
Example"mkt-0001"
slugstring
URL slug
Example"btc-above-120k-2026-12-31"
questionstring
Question text
Example"Will BTC clos…c 31, 2026?"
tickE4integer
Price tick (1e-4 USD), configurable per market
Example100
tradeableboolean
Whether the market currently accepts orders
Exampletrue
resolutionSourcestringnullable
Resolution data source
Example"pyth:BTC/USD"
cutoffTsint64
Matching cutoff (epoch seconds)
Example1760832000
underlyingCoinstringnullable
Underlying asset (BTC, for example)
Example"BTC"
winningOutcomeYES | NOnullable
Winning outcome; null = not resolved. "Resolved" is defined as this field being non-null
Example"YES"
resolvedAtSint64nullable
Unix seconds recorded by the resolution command (not the time the projection was written)
Example1760832060
disputeWindowEndsAtint64nullable
Dispute window end (epoch seconds); whether it has closed is for the client to derive against the current time
Example1760918400
engineStateREADY | OPEN | PAUSED | CLOSEDnullable
Engine-side lifecycle state; null = the record predates this field, so treat it as unknown
Example"READY"
onChainCutoffMsint64nullable
On-chain matching window (epoch milliseconds)
Example1760832000000
clarificationsobject[]
Clarifications
seriesIdstringnullable
The recurring event series this market belongs to

Switch status codes in the response example to view errors. For all codes, see the Errors page.

Request

curl -X GET "$BASE_URL/api/v1/markets/mkt-0001"

Response

Market summary

{
  "marketId": "mkt-0001",
  "slug": "btc-above-120k-2026-12-31",
  "question": "Will BTC close above $120,000 on Dec 31, 2026?",
  "tickE4": 100,
  "tradeable": true,
  "resolutionSource": "pyth:BTC/USD",
  "cutoffTs": 1760832000,
  "underlyingCoin": "BTC",
  "winningOutcome": "YES",
  "resolvedAtS": 1760832060,
  "disputeWindowEndsAt": 1760918400,
  "engineState": "READY",
  "onChainCutoffMs": 1760832000000,
  "clarifications": [],
  "seriesId": null
}

Path parameters

marketIdstringpathrequired
Engine market id or slug
Example"mkt-0001"

Response

200Market summary

marketIdstring
Engine market id
Example"mkt-0001"
slugstring
URL slug
Example"btc-above-120k-2026-12-31"
questionstring
Question text
Example"Will BTC clos…c 31, 2026?"
tickE4integer
Price tick (1e-4 USD), configurable per market
Example100
tradeableboolean
Whether the market currently accepts orders
Exampletrue
resolutionSourcestringnullable
Resolution data source
Example"pyth:BTC/USD"
cutoffTsint64
Matching cutoff (epoch seconds)
Example1760832000
underlyingCoinstringnullable
Underlying asset (BTC, for example)
Example"BTC"
winningOutcomeYES | NOnullable
Winning outcome; null = not resolved. "Resolved" is defined as this field being non-null
Example"YES"
resolvedAtSint64nullable
Unix seconds recorded by the resolution command (not the time the projection was written)
Example1760832060
disputeWindowEndsAtint64nullable
Dispute window end (epoch seconds); whether it has closed is for the client to derive against the current time
Example1760918400
engineStateREADY | OPEN | PAUSED | CLOSEDnullable
Engine-side lifecycle state; null = the record predates this field, so treat it as unknown
Example"READY"
onChainCutoffMsint64nullable
On-chain matching window (epoch milliseconds)
Example1760832000000
clarificationsobject[]
Clarifications
seriesIdstringnullable
The recurring event series this market belongs to

Switch status codes in the response example to view errors. For all codes, see the Errors page.