Authentication
Open the bot and tap API Key on the main menu — that first tap is what creates it. Revoke API Key in the same panel kills it instantly.
X-API-Key: WAR_example_not_a_real_key
The key can spend your balance, so treat it like a password. It reaches nobody else’s wallet, stock or orders.
Your bot wallet pays. Top up in Telegram; spend anywhere.
Errors & limits
3 requests per second per key. Bursts are not queued. Click any code to fire it in the console:
| Code | Meaning | What to do |
|---|---|---|
400 | Bad parameters, out of stock, or insufficient balance | Read error; do not retry blindly |
401 | Key missing or unknown | Check the header |
403 | Key revoked | Issue a new one in the bot |
404 | No such order or endpoint | Check the id |
405 | Wrong method for that path | Check the verb; the path itself exists |
429 | Rate limited | Back off, then retry |
Every failure returns the same shape, so you parse one thing:
{"error": "..."}
An order either completes or changes nothing.
A 400 never debits your balance and never consumes stock.
Code examples
The snippets below follow whichever endpoint is selected in the console
above. Replace $KEY with your own.
Reads — five endpoints, none of them can change anything
Your account
/api/v1/mecurl "$BASE/api/v1/me" -H "X-API-Key: $KEY"
{
"chat_id": 1000000000,
"first_name": "Alex",
"wallet_balance": 42.75
}
{
"error": "Missing X-API-Key header"
}
Products & stock
/api/v1/productsStock moves constantly and pricing is tiered by quantity, so read this before ordering.
curl "$BASE/api/v1/products" -H "X-API-Key: $KEY"
{
"services": [
{
"service_id": "S_01",
"name": "Gemini AI Pro 18Months - 15hour Hold warranty",
"price": 0.60,
"stock": 4552,
"price_tiers": [
{ "min_qty": 1, "max_qty": 10, "unit_price": 0.60 },
{ "min_qty": 11, "max_qty": 49, "unit_price": 0.55 },
{ "min_qty": 50, "max_qty": 10000, "unit_price": 0.50 }
]
}
]
}
price is what your key
pays at quantity 1, and pricing tells you which regime you
are on. Under "tiered" a bulk total is lower than
price × quantity; step the quantity in the console to
watch it cross a boundary.
On a negotiated flat rate,
pricing is "custom" and
price_tiers is null. That one price
applies at every quantity — 1 and 5000 cost the same each —
so total = price × quantity exactly. Never bill from a
tier table you were not given; read price. Switch the
console to Live and paste your key — it reads
your own regime from /products and states it above the
request.
Spends — one endpoint, and it moves real money
Place an order
/api/v1/orderBuys immediately and returns the activation links inline. There is no
second call to fetch them — store products
when you receive it.
| Field | Type | Notes | |
|---|---|---|---|
service_id | string | required | From /products, e.g. S_01 |
quantity | number | required | Whole number, 1 to 10000 |
curl -X POST "$BASE/api/v1/order" \ -H "X-API-Key: $KEY" \ -H "Content-Type: application/json" \ -d '{"service_id":"S_01","quantity":2}'
{
"success": true,
"order_id": "ORD-04621-9a84",
"service_id": "S_01",
"quantity": 2,
"unit_price": 0.60,
"total_cost": 1.20,
"new_balance": 41.55,
"products": [
"https://serviceactivation.google.com/subscription/new/AQC1x…",
"https://serviceactivation.google.com/subscription/new/AQC2y…"
]
}
{
"error": "Only 3 accounts available. Requested 10."
}
{
"error": "Insufficient Wallet Balance! You need $6.05 but have $2.10."
}
Order history
/api/v1/ordersNewest first, with the links that were delivered. Use it to re-fetch anything you failed to store.
| Query | Type | Notes | |
|---|---|---|---|
page | number | optional | Defaults to 1 |
limit | number | optional | Defaults to 50, maximum 200 |
curl "$BASE/api/v1/orders?page=1&limit=50" \ -H "X-API-Key: $KEY"
{
"success": true,
"page": 1,
"limit": 50,
"total_orders": 137,
"total_pages": 3,
"orders": [
{
"order_id": "ORD-04621-9a84",
"service_id": "S_01",
"quantity": 11,
"unit_price": 0.55,
"amount": 6.05,
"status": "success",
"delivered_products": ["https://…"],
"created_at": "2026-08-20T14:02:11Z"
}
]
}
One order
/api/v1/order/{id}Only orders placed by your own key are visible.
curl "$BASE/api/v1/order/ORD-04621-9a84" \ -H "X-API-Key: $KEY"
Order ids are
ORD-<5 digits>-<4 hex>. Place an order in the
console first, then run this with the id it returns.
{
"success": true,
"order": {
"order_id": "ORD-04621-9a84",
"service_id": "S_01",
"quantity": 11,
"unit_price": 0.55,
"amount": 6.05,
"status": "success",
"delivered_products": ["https://…"]
}
}
{
"error": "No such order"
}
Statistics
/api/v1/statsDeposits and spending over time, plus a per-product breakdown. Omit the dates for lifetime totals.
| Query | Type | Notes | |
|---|---|---|---|
start | string | optional | YYYY-MM-DD-HH:MM-AM/PM |
end | string | optional | Same format |
curl "$BASE/api/v1/stats" -H "X-API-Key: $KEY"
{
"success": true,
"deposits": { "today": 20, "7d": 140,
"30d": 610, "all_time": 4820 },
"sales": { "today": 12.5, "7d": 96,
"30d": 430, "all_time": 3910 },
"products_breakdown": [
{
"service_id": "S_01",
"name": "Gemini AI Pro 18Months",
"quantity_sold": 318,
"revenue": 174.90
}
]
}