WYNBOOKPARTNER NETWORK
Checking API Request access

RESULTS API CONTRACT 2026-08-05

Settlement truth,
ready to consume.

One authenticated feed for every Bookmaker, Mini Bookmaker, and Fancy result Wynbook declares—complete with immutable corrections, retractions, and deterministic pagination.

Start integrating Read the contract
03
result classes
500
records per page
∞
revision history
GET/api/partner/v1/results200
{
  "apiVersion": "2026-08-05",
  "results": [{
    "resultId": "bookmaker:evt_48291",
    "revision": 2,
    "current": true,
    "marketClass": "bookmaker",
    "status": "completed",
    "winner": "India",
    "supersedesRevision": 1
  }]
}
APPEND-ONLY PUBLICATIONETAG ENABLED
01 / OVERVIEW

A SINGLE RESULT SURFACE

Built for settlement engines,
not screen scraping.

Each result has a stable logical ID. Every material change creates a numbered successor. Nothing already delivered to a partner is silently rewritten.

01Server declaredOnly audited Wynbook settlement declarations enter the feed.

02Correction visibleSuccessor revisions point to the exact revision they replace.

03Consumer safeReopened matches publish a retracted status before being resolved again.

02 / QUICKSTART

AUTHENTICATION

Your first request.

Use a key carrying the results scope. Send it as a Bearer token or in X-API-Key. Keys are shown once when issued and stored by Wynbook only as a SHA-256 hash.

curl --request GET \
  --url 'https://partners.wynbook.com/api/partner/v1/results?marketClass=bookmaker&limit=100' \
  --header 'Authorization: Bearer wb_live_REPLACE_ME' \
  --header 'Accept: application/json'
Keep keys server-side.

Do not ship a partner key inside a mobile app or public browser bundle. The explorer below holds a pasted key in memory only and never writes it to storage.

03 / RESULT CLASSES

ONE ENVELOPE, THREE CONTRACTS

Ask for exactly what you settle.

01
EVENT WINNER

Bookmaker

Final fixture winner or void status. Uses the same audited event decision as Wynbook’s money engine.

marketClass=bookmaker
02
EVENT WINNER

Mini Bookmaker

A distinct consumer record with the fixture’s audited winner.

marketClass=mini_bookmaker
03
MARKET VALUE

Fancy

One immutable numeric result per declared session market, including provider market ID and innings identity when available.

Quoted line→Final value→Result / void
marketClass=fancy
04 / API REFERENCE

GET /RESULTS

Filter a snapshot. Page a stream.

All filters are optional. The default response returns only the current revision of every logical result, newest publication first.

GEThttps://partners.wynbook.com/api/partner/v1/results/{eventId?}
ParameterTypeMeaning
eventIdstring

Exact match ID. May be supplied in the path or query, but not with conflicting values.

marketClassenum

bookmaker, mini_bookmaker, or fancy.

statusenum

completed, void, or retracted.

sportIdinteger

Positive Wynbook sport ID; cricket is 4.

from / toRFC 3339

Half-open settlement time range: from ≤ settledAt < to.

publishedSinceRFC 3339

Return publications created at or after this time. Legacy since remains accepted.

includeHistoryboolean

When true, includes superseded revisions and retractions.

limit1—500

Page size. Default 100.

cursoropaque

Use nextCursor unchanged. Cursors are bound to the active filters.

05 / CORRECTIONS

IMMUTABLE BY DESIGN

Corrections arrive as facts,
not surprises.

Revision 1

completed · Winner: India

Initial declaration
Revision 2

retracted · No winner

Match reopened · supersedes revision 1
Revision 3

completed · Winner: Australia

Reviewed correction · supersedes revision 2
CONSUMER RULE

Upsert on resultId. Apply a record only when its revision is greater than the revision you hold. A retracted record withdraws the prior declaration; do not grade it as a void unless a later revision explicitly says void.

06 / OPERATIONS

ERRORS & CACHING

Predictable under load.

RFC 9457 errors

Validation failures return application/problem+json with status, detail, and instance.

Conditional polling

Responses include ETag. Send If-None-Match and accept 304 Not Modified with no response body.

Rate limits

Limits are applied per API key. A 429 response includes Retry-After: 60.

Pagination

The Link header and nextCursor identify the next page. Never construct or modify a cursor.

07 / EXPLORER

RESULT DESK

Find, inspect, verify.

Search the settlement archive without constructing URLs or handling cursors. Open any result to inspect its fields and complete revision chain. Your key remains only in this tab’s memory.

GET/api/partner/v1/results?limit=25
SAMPLE RESULTS
0 results
SETTLEMENT RECORD

Result detail

READY WHEN YOU ARE

Integrate with the result,
not the uncertainty.

Request partner access