KA BOT API

Start here

Connect your bot to KA BOT and redeem PUBG UC over HTTP. Get one successful test call before you wire customer checkout.

First successful request

  1. Key — in Telegram: /api_system → pick a plan → Generate key (shown once).
  2. Smoke test — call a free endpoint with X-API-Key: pk_…:
    GET /v1/me (plan + wallet) or GET /v1/stock (inventory counts).
  3. Lookup (recommended) — GET /v1/player/lookup?player_id=… before you charge your customer.
  4. Redeem — POST /v1/jobs/redeem with exactly one code source.
  5. Poll — GET /v1/jobs/{job_id} until done or failed. Store job_id as your receipt.
If /me or /stock fails, fix the key / plan first — do not debug redeem yet.

Pick a code source

A · Your database

You already hold codes in your bot DB. Send them in codes. You own mark-used / refund logic after every result.

B · KA BOT inventory

Codes sit in your KA BOT stock (/addcodes or buy). Send uc, categories, or packs. KA BOT reports whether a failed code returned to stock.

One source per request. Mixing codes with inventory fields → 400 ambiguous_source. Details and failure handling → Redeem.

Billing (short)

1 code attempted = 1 API request (success or fail).
Example: 240 UC with 4 codes → 4 requests.

Free: /health, /me, /quota, /stock, /player/lookup, job polling. Full rules → Limits.

Chat redeem inside KA BOT (active subscription) does not use API quota. Checker is priced separately.

Next Redeem →