Void match prediction

Void a published match prediction. Refunds entry-cost coins per attempt via ledger; job runs asynchronously.

Auth: Bearer API key with matchPredictions permission.

Idempotency: Idempotency-Key header required. Same key + same body returns the original 202. Same key + different body returns 409 IDEMPOTENCY_KEY_CONFLICT.

Lifecycle: allowed only from scheduled | open | locked | void_failed. draft returns 409 INVALID_LIFECYCLE_TRANSITION. Already settled → 409 MATCH_ALREADY_SETTLED. Already voided → 409 MATCH_ALREADY_VOIDED. Another operation in flight → 409 OPERATION_IN_PROGRESS.

Race: settle + void on same match → exactly one 202 winner, one 409 OPERATION_IN_PROGRESS loser.

Retention: operation record retained 7 days after terminal state.

Rate limit: 429 RATE_LIMITED with Retry-After on breach.

Freeze: 503 MATCH_PREDICTION_FROZEN while ops has frozen the API.

Provide your bearer token in the

Authorization

header when making requests to protected resources.

Example:

Authorization: Bearer ********************

Responses

🟢202Accepted

application/json

Void accepted. Poll GET /results for terminal state (200 voided) or in-progress (202).

Bodyapplication/json

🟠400Validation failed

🟠401Unauthorized

🟠403Forbidden

🟠404Not found

🟠409Conflict

🟠429Rate limited

🔴503Void queue unavailable / Frozen

🔴500Internal error

curl --location 'https://adss-uat-integration.returning.ai/apis/v1/match-predictions/mp_01abc/void' \ --header 'Idempotency-Key: 01HXYZABCDEFG1234567890' \ --header 'Authorization: Bearer <token>' \ --header 'Content-Type: application/json' \ --data '{ "reason": "fixture_cancelled" }'

{ "meta": { "status": "success", "statusCode": 202, "code": "MATCH_PREDICTION_VOID_ACCEPTED", "requestId": "req_01abc", "timestamp": "2026-08-07T12:00:00.000Z" }, "message": "Void accepted.", "data": { "operationId": "mpv_01abc", "type": "void", "status": "void_in_progress", "submittedAt": "2026-08-08T10:00:00.000Z" } }

Request

Responses