Jobs

When should I use an async job instead of a sync call

Use a Manage Bet Codes async job when the work exceeds the synchronous limits: more than 6 targets, more than one source code, a split onto many targets, or a merge onto many targets. Starter, Pro, and Tipster keys get no jobs but still call the same API with regular daily credits, so the synchronous batch still applies there, while adding an API plan unlocks jobs with higher limits.

• More than 6 targets.
• More than one source code.
• A split onto many targets.
• A merge onto many targets.

Starter, Pro, and Tipster keys get no jobs but still call the same API with regular daily credits. The synchronous batch still works. Adding an API plan unlocks jobs and higher limits.

How to create an async conversion or booking job

Create a Manage Bet Codes job with POST /v1/jobs by naming the kind (convert or book), the source codes, and up to 15 targets. The API returns 202 with a job id, an estimated_credits quote, and a queued status, then charges each item when that item starts.

POST /v1/jobs
{
  "kind": "convert",
  "code": "7B9A2F",
  "from": "sportybet",
  "to": ["1xng", "msport", "bet9ja", "melbet", "megapari",
         "22bet", "helabet", "paripesa"]
}

{
  "kind": "convert",
  "codes": [
    {"code": "7B9A2F", "from": "sportybet"},
    {"code": "ABC123", "from": "bet9ja"}
  ],
  "to": ["1xng", "msport"]
}

{"id": "job_...", "status": "queued", "kind": "convert",
 "estimated_credits": 30, "created_at": "..."}

How to read job progress and cancel a job

GET /v1/jobs/{id}

{
  "id": "job_...", "status": "done", "kind": "convert",
  "progress": {"done": 15, "total": 15},
  "results": [...],
  "billing": {"credits_used": 30},
  "created_at": "...", "finished_at": "..."
}

• GET /v1/jobs lists recent jobs.
• DELETE /v1/jobs/{id} cancels a queued or running job.
• A running job stops after the current item.

What are the job limits and how does job billing work

A Manage Bet Codes job accepts 20 source codes, 15 targets, and 100 code-target pairs per job, or 20 picks, 10 targets, and 50 pick-target pairs for a book job. Each job item is charged like the same synchronous action when the item starts, failed items are refunded, unstarted items are never charged, and finished jobs stay readable for 7 days.

An item is charged when it starts. A failed item is refunded. An unstarted item is not charged.

Your plan sets the concurrent job limit. See limits.