UC UcBot PUBG redeem API

Midasbuy voucher codes

Hand a UID and a crate code. Get UC on the player.

Public HTTP API for PUBG Mobile UC redeem. You send the player ID and unused codes; we return a per-code batch with success, fail, and credits used.

Packing slip · live request
Build a call, then copy it.
UC

      
Test with your token — response lands here.
POST /redeem

Authentication

Same UUID in any one of these places. Master key (Telegram bot) also works as a raw string.

Header

Authorization: Bearer <uuid>
X-Api-Key: <uuid>

Query

?token=<uuid>

JSON body

{"token":"<uuid>"}

Reference

Paths are relative to the host. playerid is an alias of uid. A single code string or a codes array both work.

POST/redeem

Sync UC redeem. Instant batch result.

POST/topup-sync

Alias of /redeem (FF-API compatible).

POST/topup

Async redeem. Requires callback url. Returns 202, then POSTs the result.

POST/check

Validate a code only. Does not pay.

GET/nickname?uid=

Look up the in-game name.

GET/status/{apikey}

Credits left, expiry, token state.

GET/health

Engine workers. No token required.

Request body

{
  "orderid": "ORD-1001",
  "uid": "5164170732",
  "codes": ["CODE1", "CODE2"],
  "url": "https://yoursite.com/callback"
}

Sync response

{
  "status": "success",
  "orderid": "ORD-1001",
  "player_id": "5164170732",
  "player_name": "Player",
  "success": 1,
  "failed": 0,
  "total": 1,
  "duration_ms": 2100,
  "credits_used": 1,
  "batch": [
    {"code": "CODE1", "ok": true, "msg": "Redeemed successfully", "uc_amount": 60}
  ]
}

HTTP status

CodeMeaning
200Sync result ready
202Async accepted; callback follows
400Missing uid or codes
401Token missing, invalid, or disabled
402Expired, or out of credits
503Engine warming up or busy