Conversion history

How to list conversion history with filters

Use GET /v1/history to list only the caller's conversion rows with limit, offset, bookmaker, target, status, and date filters. History costs 0 API credits, rows stay readable for 90 days, and batch conversions write one row per code sharing the same batch_id.

GET /v1/history?limit=20&offset=0&bookmaker=&target=&status=&from=&to=

{
  "items": [
    {"id": 123,
     "source": {"key": "sportybet", "name": "SportyBet", "code": "7B9A2F"},
     "target": {"key": "onexbet", "name": "1xBet", "code": "R9QF0U"},
     "success": true, "counts": {"original": 13, "converted": 12},
     "credits": 2, "created_at": "...", "batch_id": "b_8f3c1d"}
  ],
  "total": 100, "limit": 20, "offset": 0
}

What each history filter controls

How long history lasts and who can read each row

A Manage Bet Codes history row belongs to the API key that created it, costs 0 API credits to read, and stays readable for 90 days. Read one row with GET /v1/history/{id}: a row outside the caller's account returns 404 history_not_found.

• The route returns only the caller's rows.
• History costs 0 credits.
• Rows are kept for 90 days.
• GET /v1/history/{id} reads one row. A row outside your account returns 404 history_not_found.

Batch history writes one row for each code. All rows share the batch_id.