Partner documentation

How to use the partner cabinet, API, and BOT-T shop integration. Share this link with your partner.

What you need to start
Partner cabinet
REST API
BOT-T integration
Go-live checklist

1. What you need to start

Cabinet login and password Issued by an admin. Login: /partner

API key (pk_…) Shown once when created. Keep it secret.

Account balance Shared with the account wallet: top up in the user cabinet or Telegram bot; an admin can also credit it. Partner price is charged from it.

Missing something? Contact the HiddifySales admin.

Open cabinet Login page

2. Partner cabinet

In the cabinet you monitor balance, key issuances, and API settings.

Dashboard: balance, quotas, issuances — https://adminka1.space/partner
Issuances: stock status (available / reserved / sold), links, BOT-T orders.
Balance history: top-ups and key charges.
API section: request examples and BOT-T webhook URLs.

Partner balance is the same as the linked user’s account wallet. Top up in the /partner Balance section with the same methods as regular clients (card, FPS, crypto, etc.), or via the account cabinet / Telegram bot. An admin can also credit manually.

3. REST API

Use the REST API for your own bot or to stock BOT-T warehouse lines.

Base URL: https://adminka1.space/api/v1/partner

Auth: X-API-KEY: pk_... or Authorization: Bearer pk_...

Endpoints

Method	Path	Purpose
GET	`/tariffs`	Tariff catalog with your discounted price
GET	`/servers`	Servers and countries (id, country_code)
GET	`/balance`	Shared wallet (same as user account) and quotas
POST	`/keys`	Issue a trial or paid key (optional country)
GET	`/keys/{id}`	Get issuance by id
GET	`/keys/by-order?external_order_id=...`	Find by external_order_id

Stock for BOT-T (billing=on_sale)

Create a key without charging immediately and paste subscription_url into a BOT-T unique product line.

POST https://adminka1.space/api/v1/partner/keys
X-API-KEY: pk_YOUR_TOKEN
Content-Type: application/json

{
  "package": "tariff",
  "tariff_id": 12,
  "billing": "on_sale",
  "external_order_id": "stock-1"
}

billing=immediate — charge now (your bot). billing=on_sale — charge after BOT-T payment.

REST errors

error	HTTP
unauthorized	401
forbidden	403
insufficient_balance	402
quota_exceeded	429
validation_error	422
provisioning_failed	503

4. BOT-T integration

BOT-T shop does not use your REST catalog; it uses two webhooks on a unique product card.

Create keys via POST /keys with billing=on_sale.
Paste subscription_url values into unique product warehouse lines.
Set check and notify URLs in the product API settings (below).
After payment BOT-T calls notify — we charge balance and mark the key sold.

URLs for the product card

Pre-payment check
https://adminka1.space/api/v1/partner/bot-t/check?api_key=pk_YOUR_TOKEN

Post-payment notify
https://adminka1.space/api/v1/partner/bot-t/notify?api_key=pk_YOUR_TOKEN

Check response

HTTP 200 and JSON only:

{"success": true}

{"success": false}

true — line goes to the order; false — next line. Non-JSON / non-200 — order is not created. Limit: up to 20 lines per order.

After payment (status=1)

The buyer already got the link from BOT-T stock. We accept form-urlencoded (id, status, user[telegram_id], product[data]) and respond with any 2xx.

Up to 3 retries are handled idempotently by BOT-T order id.

5. Go-live checklist

Received cabinet login and API key
Shared wallet topped up (cabinet/bot or admin)
GET /tariffs shows the needed tariffs and partner price
Test POST /keys returns a working subscription_url
For BOT-T: check → success true, notify → balance charged, key sold
Cabinet shows the issuance and balance transaction