Skip to main content
POST
Resolve markets
See the integration guide for the workflow and interpretation of this response.

Authorizations

Authorization
string
header
required

Proposed server-to-server API key. No client request HMAC signing scheme is specified.

Headers

X-Client-Request-Id
string

Caller correlation reference; not an idempotency guarantee.

Body

application/json
inputs
object[]
required

One or more native identifier tuples; unique client_reference per tuple. Each returns a status-bearing mapping result.

Minimum array length: 1

Supply venue and at least one exact native identity form. A venue_market_id alone resolves the whole market; add venue_outcome_id to select a side. Token, ticker+outcome and slug+outcome forms select an individual listing. If multiple forms are provided they must identify the same source record or fail validation. Unknown/ambiguous mappings are not guessed. Event IDs belong in /events?venue=...&venue_event_id=..., never venue_market_id.

Response

200 - application/json

Success.

items
object[]
required
as_of
string<date-time>
required