🛍️ Products & prices :- https://msconfirmationid.com/buy-api/products?limit=20&token=your_api_key_here

Example · Browser URL · GET

https://msconfirmationid.com/buy-api/products?limit=20&token=YOUR_TOKEN

Products grouped by category, account prices, quantity tiers and stock. Use next_after_id as after_id for the next page.

Example · REST · GET

curl "https://msconfirmationid.com/wp-json/tgbt-api/v1/buy/products?limit=20" \
  -H "X-API-Key: YOUR_TOKEN"

🛒 Buy keys :- https://msconfirmationid.com/buy-api/buy?code=Product_ID&quantity=Quantity&orderId=Your_unique_order_reference&token=your_api_key_here

Example · Browser URL · GET

https://msconfirmationid.com/buy-api/buy?code=123&quantity=1&orderId=order-001&token=YOUR_TOKEN

Buy 1–100 keys using code (product ID) and quantity. Instant keys are returned; manual products stay processing. Use order to retrieve delivery.

Example · REST · POST

curl -X POST "https://msconfirmationid.com/wp-json/tgbt-api/v1/buy/buy" \
  -H "X-API-Key: YOUR_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"code":123,"quantity":1,"orderId":"order-001"}'

📦 Order details & keys :- https://msconfirmationid.com/buy-api/order?order_number=Order_number&token=your_api_key_here

Example · Browser URL · GET

https://msconfirmationid.com/buy-api/order?order_number=ORDER_NUMBER&token=YOUR_TOKEN

Read your latest order state, keys and messages. Use order_id or order_number; your original purchase orderId is also accepted. Includes Telegram orders.

Example · REST · GET

curl "https://msconfirmationid.com/wp-json/tgbt-api/v1/buy/order?order_number=ORDER_NUMBER" \
  -H "X-API-Key: YOUR_TOKEN"

📜 Orders History :- https://msconfirmationid.com/buy-api/orders?token=your_api_key_here

Example · Browser URL · GET

https://msconfirmationid.com/buy-api/orders?token=YOUR_TOKEN

Latest 50 orders and failed purchase attempts, newest first. Use an order ID or number for delivery details.

Example · REST · GET

curl "https://msconfirmationid.com/wp-json/tgbt-api/v1/buy/orders" \
  -H "X-API-Key: YOUR_TOKEN"

Success: {"success":true,"data":{...}}. Failure: {"success":false,"error":{"code":"...","message":"..."}}. For history lookups, inspect the nested saved response too. Times are UTC; money uses decimal USD strings.

Use a new request_id/orderId for each new action (1–64 letters, digits, dot, colon, underscore or hyphen). Repeat the same action with the same ID and fields to replay its result. After a timeout, find the matching reference in history. Processing/review: wait or contact support; do not submit another ID.

200: read/success · 202: still processing/review · 400: input or service error · 401/403: key/access · 404: missing record/endpoint · 409: account busy or action conflict · 429: limit · 503: temporarily unavailable. A saved failed action may be returned inside a successful history lookup.

Limit: 30 requests/minute per account. OCR: 100/day. PID shares the bot’s daily quota. Purchases and deposit actions may return account_busy; retry those using the same ID.

🔢 GetCID :- https://msconfirmationid.com/getcid-api/generate?iid=Your_IID_here&token=your_api_key_here

Example · Browser URL · GET · IID with hyphens

https://msconfirmationid.com/getcid-api/generate?iid=6407142-1898830-5913156-7151185-2805065-1745860-9354801-9089053-2803922&token=YOUR_TOKEN

Send a 54- or 63-digit IID and API key. No client reference is needed in Browser or REST calls. No charges for old/public CIDs or failed/blocked requests.

Example · REST · POST

curl -X POST "https://msconfirmationid.com/wp-json/tgbt-api/v1/getcid/generate" \
  -H "X-API-Key: YOUR_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"iid":"6407142-1898830-5913156-7151185-2805065-1745860-9354801-9089053-2803922"}'

Browser URL · GET

https://msconfirmationid.com/getcid-api/generate?iid=640714218988305913156715118528050651745860935480190890532803922&token=YOUR_TOKEN

REST · POST

curl -X POST "https://msconfirmationid.com/wp-json/tgbt-api/v1/getcid/generate" -H "X-API-Key: YOUR_TOKEN" -H "Content-Type: application/json" -d '{"iid":"640714218988305913156715118528050651745860935480190890532803922"}'

Both IID formats work: with hyphens, as shown above, or digits only. No request reference is needed.

💰 GetCID balance :- https://msconfirmationid.com/getcid-api/balance?token=your_api_key_here

Example · Browser URL · GET

https://msconfirmationid.com/getcid-api/balance?token=YOUR_TOKEN

Shows your USD wallet balance and GetCID credits.

Example · REST · GET

curl "https://msconfirmationid.com/wp-json/tgbt-api/v1/getcid/balance" \
  -H "X-API-Key: YOUR_TOKEN"

🕘 GetCID history :- https://msconfirmationid.com/getcid-api/history?token=your_api_key_here

Example · Browser URL · GET

https://msconfirmationid.com/getcid-api/history?token=YOUR_TOKEN

Shows your last 50 CID requests, newest first.

Example · REST · GET

curl "https://msconfirmationid.com/wp-json/tgbt-api/v1/getcid/history" \
  -H "X-API-Key: YOUR_TOKEN"

Success: {"success":true,"data":{...}}. Failure: {"success":false,"error":{"code":"...","message":"..."}}. For history lookups, inspect the nested saved response too. Times are UTC; money uses decimal USD strings.

GetCID generation needs IID and API key, with optional entitlement_id; no client reference in Browser or REST calls. History shows your latest 50 requests.

200: read/success · 202: still processing/review · 400: input or service error · 401/403: key/access · 404: missing record/endpoint · 409: account busy or action conflict · 429: limit · 503: temporarily unavailable. A saved failed action may be returned inside a successful history lookup.

Limit: 30 requests/minute per account. OCR: 100/day. PID shares the bot’s daily quota. Purchases and deposit actions may return account_busy; retry those using the same ID.

📷 Read Installation ID :- https://msconfirmationid.com/ocr-api/recognize?image_url=Your_image_URL_here&token=your_api_key_here

Example · Browser URL · GET

https://msconfirmationid.com/ocr-api/recognize?image_url=https://msconfirmationid.com/wp-content/plugins/telegram-commerce-0.16.5/assets/ocr-sample.png&token=YOUR_TOKEN

Read an IID from a JPEG/PNG/WebP image, max 5 MB and 25 megapixels. Browser: image_url. REST also accepts image_base64 or multipart image. No client reference is needed. Each call runs OCR and uses daily allowance. Result: data.iid; no CID is generated.

Example · REST · POST

curl -X POST "https://msconfirmationid.com/wp-json/tgbt-api/v1/ocr/recognize" \
  -H "X-API-Key: YOUR_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"image_url":"https://msconfirmationid.com/wp-content/plugins/telegram-commerce-0.16.5/assets/ocr-sample.png"}'

🕘 OCR history :- https://msconfirmationid.com/ocr-api/history?token=your_api_key_here

Example · Browser URL · GET

https://msconfirmationid.com/ocr-api/history?token=YOUR_TOKEN

Shows your last 30 OCR requests, newest first.

Example · REST · GET

curl "https://msconfirmationid.com/wp-json/tgbt-api/v1/ocr/history" \
  -H "X-API-Key: YOUR_TOKEN"

Success: {"success":true,"data":{...}}. Failure: {"success":false,"error":{"code":"...","message":"..."}}. For history lookups, inspect the nested saved response too. Times are UTC; money uses decimal USD strings.

OCR needs only an image and API key. Each call runs OCR and consumes daily allowance; results are not replayed. After a timeout, inspect history before retrying.

200: read/success · 202: still processing/review · 400: input or service error · 401/403: key/access · 404: missing record/endpoint · 409: account busy or action conflict · 429: limit · 503: temporarily unavailable. A saved failed action may be returned inside a successful history lookup.

Limit: 30 requests/minute per account. OCR: 100/day. PID shares the bot’s daily quota.

🔍 PID key check :- https://msconfirmationid.com/pid-api/check?key=Your_key_here&token=your_api_key_here

Example · Browser URL · GET

https://msconfirmationid.com/pid-api/check?key=N3B73-7TG3P-XJX6X-33M3M-HT9TT&token=YOUR_TOKEN

Check up to 100 keys using key (one) or keys (array, comma or newline-separated) and API key. No client reference is needed in Browser or REST calls. Each unique key uses one shared daily PID check.

Example · REST · POST

curl -X POST "https://msconfirmationid.com/wp-json/tgbt-api/v1/pid/check" \
  -H "X-API-Key: YOUR_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"key":"N3B73-7TG3P-XJX6X-33M3M-HT9TT"}'

Browser URL

https://msconfirmationid.com/pid-api/check?keys=N3B73-7TG3P-XJX6X-33M3M-HT9TT,B8N2B-G68RJ-HGJC4-GXWDT-2BCBV&token=YOUR_TOKEN

REST API · POST

curl -X POST "https://msconfirmationid.com/wp-json/tgbt-api/v1/pid/check" -H "X-API-Key: YOUR_TOKEN" -H "Content-Type: application/json" -d '{"keys":["N3B73-7TG3P-XJX6X-33M3M-HT9TT","B8N2B-G68RJ-HGJC4-GXWDT-2BCBV"]}'

Send up to 100 keys per request. Duplicate keys count once. Inspect each result; a completed HTTP request can include failed checks.

🕘 PID Key Checker history :- https://msconfirmationid.com/pid-api/history?token=your_api_key_here

Example · Browser URL · GET

https://msconfirmationid.com/pid-api/history?token=YOUR_TOKEN

Shows your last 30 key checks, newest first.

Example · REST · GET

curl "https://msconfirmationid.com/wp-json/tgbt-api/v1/pid/history" \
  -H "X-API-Key: YOUR_TOKEN"

Success: {"success":true,"data":{...}}. Failure: {"success":false,"error":{"code":"...","message":"..."}}. For history lookups, inspect the nested saved response too. Times are UTC; money uses decimal USD strings.

PID checks need key or keys and API key; no client reference in Browser or REST calls. Checks run on each call and consume daily allowance. After a timeout, inspect history before checking again.

200: read/success · 202: still processing/review · 400: input or service error · 401/403: key/access · 404: missing record/endpoint · 409: account busy or action conflict · 429: limit · 503: temporarily unavailable. A saved failed action may be returned inside a successful history lookup.

Limit: 30 requests/minute per account. OCR: 100/day. PID shares the bot’s daily quota.