Reseller API

One endpoint, a form with the key and action fields. Compatible with the standard SMM panel API v2 — ready-made shop and billing modules connect without changes.

Quick start

Address: https://telegos.app/api/v2
Method: POST
Body format: application/x-www-form-urlencoded
Response: JSON, always with status 200

The key is passed in the key field of the request body — the Authorization header is not used here. Your account works on a separate token, so resetting the key does not end your browser session.

Service list

Returns the whole price list: the service id for action=add, the price per 1000 and the volume limits.

Field	Value
`key`	Your key
`action`	services

Request

curl -X POST https://telegos.app/api/v2 \
  -d key=YOUR_KEY \
  -d action=services

Response

[
  {
    "service": 101,
    "name": "Telegram Members · CIS",
    "type": "Default",
    "category": "Telegram Members",
    "rate": "0.90",
    "min": "50",
    "max": "10000",
    "refill": true,
    "cancel": true
  }
]

Create an order

Charges the balance right away and returns the order number.

Field	Value
`key`	Your key
`action`	add
`service`	service id from action=services
`link`	Link to a channel, post or profile
`quantity`	Order volume within min…max

Request

curl -X POST https://telegos.app/api/v2 \
  -d key=YOUR_KEY \
  -d action=add \
  -d service=101 \
  -d link=https://t.me/example \
  -d quantity=500

Response

{
  "order": 23501
}

Drip-feed order

The same fields plus two: how many runs to make and the pause between them. Here quantity is the volume of a single run, and the total for all runs is charged.

Field	Value
`runs`	Number of runs
`interval`	Pause between runs in minutes

Request

curl -X POST https://telegos.app/api/v2 \
  -d key=YOUR_KEY \
  -d action=add \
  -d service=101 \
  -d link=https://t.me/example \
  -d quantity=100 \
  -d runs=5 \
  -d interval=60

Response

{
  "order": 23502
}

Order status

start_count is the counter at the start, remains is how much is still undelivered.

Field	Value
`key`	Your key
`action`	status
`order`	Order number

Request

curl -X POST https://telegos.app/api/v2 \
  -d key=YOUR_KEY \
  -d action=status \
  -d order=23501

Response

{
  "charge": "0.4500",
  "start_count": "3572",
  "status": "In progress",
  "remains": "157",
  "currency": "USD"
}

Status of several orders

Up to 100 numbers per request. The response is an object keyed by order number: a missing one comes with error and does not break the rest.

Field	Value
`key`	Your key
`action`	status
`orders`	Numbers separated by commas

Request

curl -X POST https://telegos.app/api/v2 \
  -d key=YOUR_KEY \
  -d action=status \
  -d orders=23501,23502,999999

Response

{
  "23501": {
    "charge": "0.4500",
    "start_count": "3572",
    "status": "Completed",
    "remains": "0",
    "currency": "USD"
  },
  "23502": {
    "charge": "0.9000",
    "start_count": "1204",
    "status": "In progress",
    "remains": "300",
    "currency": "USD"
  },
  "999999": {
    "error": "Incorrect order ID"
  }
}

Refill

Available where the service returns refill: true. The refill progress is checked by a separate refill_status action using its number.

Field	Value
`key`	Your key
`action`	refill / refill_status
`order`	Order number — for refill
`refill`	Refill number — for refill_status

Request

curl -X POST https://telegos.app/api/v2 \
  -d key=YOUR_KEY \
  -d action=refill \
  -d order=23501

Response

{
  "refill": 412
}

Cancellation

Available where the service returns cancel: true. The money for canceled orders returns to the balance.

Field	Value
`key`	Your key
`action`	cancel
`orders`	Numbers separated by commas

Request

curl -X POST https://telegos.app/api/v2 \
  -d key=YOUR_KEY \
  -d action=cancel \
  -d orders=23501,23502

Response

[
  { "order": 23501, "cancel": 1 },
  { "order": 23502, "cancel": { "error": "Incorrect order ID" } }
]

Balance

Field	Value
`key`	Your key
`action`	balance

Request

curl -X POST https://telegos.app/api/v2 \
  -d key=YOUR_KEY \
  -d action=balance

Response

{
  "balance": "19.61",
  "currency": "USD"
}

Order statuses

Status	What it means
`Pending`	The order is accepted and waiting to be sent to the provider
`In progress`	Delivery is running
`Processing`	The order is being processed on the provider side
`Completed`	The volume is delivered in full
`Partial`	Part of the volume is delivered, the rest is returned to the balance
`Canceled`	The order is canceled, the charge is returned

Errors

An error arrives with the same 200 code and differs by the presence of the error field: check the body, not the response status. In batch actions the error sits inside its own element and does not cancel the rest.

Response

{
  "error": "Incorrect request"
}