TelePilot Pro
Customer API — automate wallet balance, marketplace orders, growth services, SMS verification, deposits, and licenses.
Your API Key
Loading…
Test API
Select an action, fill in parameters, and send a request. When logged in, your API key is loaded automatically.
curl -X POST "https://telepilotpro.com/api/v1" \ --data-urlencode "key=YOUR_API_KEY" \ --data-urlencode "action=balance"
API Endpoint
https://telepilotpro.com/api/v1
All API requests should be sent via HTTP POST to this endpoint with your key and action parameters. You may also send Authorization: Bearer YOUR_KEY instead of the key field.
curl -X POST "https://telepilotpro.com/api/v1" \ --data-urlencode "key=YOUR_API_KEY" \ --data-urlencode "action=balance"
Authentication
Every request requires your API key. Pass it as key in the POST body, or use Authorization: Bearer YOUR_KEY. Rate limit: 120 requests/minute per key.
| Parameter | Description | Required |
|---|---|---|
key | Your API key | Yes |
action | API action name (see each section below) | Yes |
Response format
Every response uses { success, … }. Errors return success: false and an error message.
Example Response
{
"success": true,
"balance": "125.5000",
"currency": "USD"
}Wallet balance
Returns the authenticated user wallet balance in USD. Use this before placing orders to confirm sufficient funds.
| Parameter | Description | Required |
|---|---|---|
key | Your API key | Yes |
action | Must be `balance` | Yes |
Example Request
curl -X POST "https://telepilotpro.com/api/v1" \ --data-urlencode "key=YOUR_API_KEY" \ --data-urlencode "action=balance"
Example Response
{
"success": true,
"balance": "125.5000",
"currency": "USD"
}REST alternative (GET /api/v1/balance)
Modern integrations can call the dedicated REST route with Bearer auth instead of the action gateway.
curl -X GET "https://telepilotpro.com/api/v1/balance" \ -H "Authorization: Bearer YOUR_API_KEY"
Account info
Returns account profile, wallet balance, and API key metadata (prefix only — the full key is never returned after generation).
| Parameter | Description | Required |
|---|---|---|
key | Your API key | Yes |
action | Must be `me` | Yes |
Example Request
curl -X POST "https://telepilotpro.com/api/v1" \ --data-urlencode "key=YOUR_API_KEY" \ --data-urlencode "action=me"
Example Response
{
"success": true,
"id": "usr_abc123",
"email": "you@example.com",
"balance": "125.5000",
"currency": "USD",
"apiKey": {
"hasKey": true,
"prefix": "tp_a1b2c3d4…",
"enabled": true
}
}REST alternative (GET /api/v1/me)
Modern integrations can call the dedicated REST route with Bearer auth instead of the action gateway.
curl -X GET "https://telepilotpro.com/api/v1/me" \ -H "Authorization: Bearer YOUR_API_KEY"
Growth services (paginated)
List growth / SMM services with pagination and filters. Each row includes service ID, rate per 1k, min/max quantity, and entityType `smm`. Use the service ID when placing orders.
| Parameter | Description | Required |
|---|---|---|
key | Your API key | Yes |
action | Must be `growth_services` | Yes |
page | Page number (default 1) | No |
limit | Items per page, max 100 (default 50) | No |
category | Filter by category name | No |
platform | Filter by platform (e.g. instagram, telegram) | No |
search | Search by name, category, or service ID | No |
Example Request
curl -X POST "https://telepilotpro.com/api/v1" \ --data-urlencode "key=YOUR_API_KEY" \ --data-urlencode "action=growth_services"
Example Response
{
"success": true,
"services": [
{
"service": "42",
"name": "Instagram Followers",
"type": "Default",
"category": "Instagram",
"rate": "0.85",
"min": "100",
"max": "50000",
"refill": true,
"cancel": false,
"entityType": "smm"
}
],
"pagination": { "page": 1, "limit": 50, "total": 1240, "totalPages": 25 }
}REST alternative (GET /api/v1/growth/services)
Modern integrations can call the dedicated REST route with Bearer auth instead of the action gateway.
curl -X GET "https://telepilotpro.com/api/v1/growth/services?page=1&limit=50" \ -H "Authorization: Bearer YOUR_API_KEY"
Marketplace products
List marketplace catalog products (accounts, tools, etc.) with optional pagination. Rows include stock, rate, and entityType `product`. Marketplace orders support cancellation when allowed.
| Parameter | Description | Required |
|---|---|---|
key | Your API key | Yes |
action | Must be `products` | Yes |
page | Page number (default 1) | No |
limit | Items per page, max 100 (default 50) | No |
category | Filter by category | No |
search | Search by name or ID | No |
Example Request
curl -X POST "https://telepilotpro.com/api/v1" \ --data-urlencode "key=YOUR_API_KEY" \ --data-urlencode "action=products"
Example Response
{
"success": true,
"products": [
{
"service": "15",
"name": "Gmail Account",
"type": "Auto",
"category": "Accounts",
"rate": "2.50",
"min": "1",
"max": "10",
"stock": 48,
"refill": false,
"cancel": true,
"entityType": "product"
}
],
"pagination": { "page": 1, "limit": 50, "total": 320, "totalPages": 7 }
}REST alternative (GET /api/v1/products)
Modern integrations can call the dedicated REST route with Bearer auth instead of the action gateway.
curl -X GET "https://telepilotpro.com/api/v1/products?page=1&limit=50&category=Accounts" \ -H "Authorization: Bearer YOUR_API_KEY"
All services (combined, legacy)
Returns marketplace products and growth services in one list. Prefer `/api/v1/growth/services` and `/api/v1/products` for paginated catalogs. Unpaginated responses include a deprecation warning in `meta`.
| Parameter | Description | Required |
|---|---|---|
key | Your API key | Yes |
action | Must be `services` | Yes |
page | Optional — when set, returns paginated growth + marketplace rows | No |
limit | Items per page when paginating | No |
category | Category filter | No |
platform | Platform filter (growth only) | No |
search | Search filter | No |
Example Request
curl -X POST "https://telepilotpro.com/api/v1" \ --data-urlencode "key=YOUR_API_KEY" \ --data-urlencode "action=services"
Example Response
{
"success": true,
"services": [ "...product and smm rows..." ],
"meta": {
"warning": "Unpaginated catalog is deprecated. Use /api/v1/growth/services or /api/v1/products."
}
}REST alternative (GET /api/v1/services)
Modern integrations can call the dedicated REST route with Bearer auth instead of the action gateway.
curl -X GET "https://telepilotpro.com/api/v1/services" \ -H "Authorization: Bearer YOUR_API_KEY"
Inventory check
Check real-time stock and availability for a marketplace product or growth service ID before ordering.
| Parameter | Description | Required |
|---|---|---|
key | Your API key | Yes |
action | Must be `inventory` | Yes |
service | Service / product ID | Yes |
Example Request
curl -X POST "https://telepilotpro.com/api/v1" \ --data-urlencode "key=YOUR_API_KEY" \ --data-urlencode "action=inventory"
Example Response
{
"success": true,
"service": 15,
"stock": 48,
"available": true,
"rate": "2.50",
"min": 1,
"max": 10,
"entityType": "product"
}REST alternative (GET /api/v1/inventory)
Modern integrations can call the dedicated REST route with Bearer auth instead of the action gateway.
curl -X GET "https://telepilotpro.com/api/v1/inventory?service=15" \ -H "Authorization: Bearer YOUR_API_KEY"
Order history
Unified order history across growth, marketplace, and SMS verification. Sorted newest first. Provider status is not auto-refreshed on this endpoint — poll order status separately.
| Parameter | Description | Required |
|---|---|---|
key | Your API key | Yes |
action | Must be `orders` | Yes |
type | Filter: all, smm, growth, marketplace, sms | No |
page | Page number (default 1) | No |
limit | Items per page, max 100 (default 20) | No |
Example Request
curl -X POST "https://telepilotpro.com/api/v1" \ --data-urlencode "key=YOUR_API_KEY" \ --data-urlencode "action=orders"
Example Response
{
"success": true,
"orders": [
{
"id": 1042,
"type": "marketplace",
"order_number": "MKT-482910",
"service_name": "Gmail Account",
"status": "completed",
"charge": 2.5,
"created_at": "2026-07-11T14:22:00.000Z"
}
],
"pagination": { "page": 1, "limit": 20, "total": 87, "totalPages": 5 }
}REST alternative (GET /api/v1/orders)
Modern integrations can call the dedicated REST route with Bearer auth instead of the action gateway.
curl -X GET "https://telepilotpro.com/api/v1/orders?type=all&page=1&limit=20" \ -H "Authorization: Bearer YOUR_API_KEY"
Place order
Place a growth or marketplace order. Deducts wallet balance atomically. Growth orders require a target link; marketplace digital products may use your account email when link is omitted.
| Parameter | Description | Required |
|---|---|---|
key | Your API key | Yes |
action | Must be `add` | Yes |
service | Service / product ID from catalog | Yes |
quantity | Order quantity | Yes |
link | Target URL or delivery email | No |
Example Request
curl -X POST "https://telepilotpro.com/api/v1" \ --data-urlencode "key=YOUR_API_KEY" \ --data-urlencode "action=add"
Example Response
{
"success": true,
"order": "1042",
"providerOrderId": 99887766
}REST alternative (POST /api/v1/order)
Modern integrations can call the dedicated REST route with Bearer auth instead of the action gateway.
curl -X POST "https://telepilotpro.com/api/v1/order" \
-H "Authorization: Bearer YOUR_API_KEY" \
-H "Content-Type: application/json" \
-d '{"service":"42","quantity":"1000","link":"https://instagram.com/username"}'Order status
Get live order status. Pass optional `type` to disambiguate when the same numeric ID could exist in different order tables (sms, growth, marketplace, smm).
| Parameter | Description | Required |
|---|---|---|
key | Your API key | Yes |
action | Must be `status` | Yes |
id | Local order ID | Yes |
type | Optional: sms, growth, marketplace, smm | No |
Example Request
curl -X POST "https://telepilotpro.com/api/v1" \ --data-urlencode "key=YOUR_API_KEY" \ --data-urlencode "action=status"
Example Response
{
"success": true,
"order": "1042",
"status": "COMPLETED",
"type": "marketplace",
"charge": "2.5000",
"remains": "0",
"start_count": 0,
"currency": "USD",
"accounts": []
}REST alternative (GET /api/v1/order)
Modern integrations can call the dedicated REST route with Bearer auth instead of the action gateway.
curl -X GET "https://telepilotpro.com/api/v1/order?id=1042&type=marketplace" \ -H "Authorization: Bearer YOUR_API_KEY"
Cancel order
Cancel an eligible marketplace order and receive a wallet refund when the provider allows cancellation.
| Parameter | Description | Required |
|---|---|---|
key | Your API key | Yes |
action | Must be `cancel` | Yes |
id | Local order ID | Yes |
Example Request
curl -X POST "https://telepilotpro.com/api/v1" \ --data-urlencode "key=YOUR_API_KEY" \ --data-urlencode "action=cancel"
Example Response
{
"success": true,
"status": "Canceled",
"refundAmount": 2.5
}REST alternative (POST /api/v1/order/cancel)
Modern integrations can call the dedicated REST route with Bearer auth instead of the action gateway.
curl -X POST "https://telepilotpro.com/api/v1/order/cancel" \
-H "Authorization: Bearer YOUR_API_KEY" \
-H "Content-Type: application/json" \
-d '{"id":"1042"}'SMS projects
List available SMS verification projects with retail prices. Use project_id when placing an SMS order.
| Parameter | Description | Required |
|---|---|---|
key | Your API key | Yes |
action | Must be `sms_projects` | Yes |
Example Request
curl -X POST "https://telepilotpro.com/api/v1" \ --data-urlencode "key=YOUR_API_KEY" \ --data-urlencode "action=sms_projects"
Example Response
{
"success": true,
"projects": [
{
"project_id": "tg",
"name": "Telegram",
"price": "0.4500",
"country_id": null,
"country_title": null
}
]
}REST alternative (GET /api/v1/sms/projects)
Modern integrations can call the dedicated REST route with Bearer auth instead of the action gateway.
curl -X GET "https://telepilotpro.com/api/v1/sms/projects" \ -H "Authorization: Bearer YOUR_API_KEY"
SMS countries
List supported countries for SMS verification. Includes a `random` option for lowest-price routing.
| Parameter | Description | Required |
|---|---|---|
key | Your API key | Yes |
action | Must be `sms_countries` | Yes |
Example Request
curl -X POST "https://telepilotpro.com/api/v1" \ --data-urlencode "key=YOUR_API_KEY" \ --data-urlencode "action=sms_countries"
Example Response
{
"success": true,
"countries": [
{ "country_code": "random", "country_name": "Random" },
{ "country_code": "us", "country_name": "United States" }
]
}REST alternative (GET /api/v1/sms/countries)
Modern integrations can call the dedicated REST route with Bearer auth instead of the action gateway.
curl -X GET "https://telepilotpro.com/api/v1/sms/countries" \ -H "Authorization: Bearer YOUR_API_KEY"
Place SMS order
Purchase a phone number for SMS verification. Poll order status or use Get SMS code until the code arrives.
| Parameter | Description | Required |
|---|---|---|
key | Your API key | Yes |
action | Must be `add_sms` | Yes |
projectId | Project ID from SMS projects | Yes |
country | Country code or random (optional) | No |
Example Request
curl -X POST "https://telepilotpro.com/api/v1" \ --data-urlencode "key=YOUR_API_KEY" \ --data-urlencode "action=add_sms"
Example Response
{
"success": true,
"order": "205",
"phone": "+15551234567",
"status": "active",
"charge": "0.4500",
"currency": "USD"
}REST alternative (POST /api/v1/sms/order)
Modern integrations can call the dedicated REST route with Bearer auth instead of the action gateway.
curl -X POST "https://telepilotpro.com/api/v1/sms/order" \
-H "Authorization: Bearer YOUR_API_KEY" \
-H "Content-Type: application/json" \
-d '{"projectId":"tg","country":"us"}'SMS verification code
Poll for the SMS verification code on an active SMS order.
| Parameter | Description | Required |
|---|---|---|
key | Your API key | Yes |
action | Must be `sms_code` | Yes |
order | SMS order ID | Yes |
Example Request
curl -X POST "https://telepilotpro.com/api/v1" \ --data-urlencode "key=YOUR_API_KEY" \ --data-urlencode "action=sms_code"
Example Response
{
"success": true,
"order": "205",
"status": "completed",
"code": "12345",
"smsContent": "Your code is 12345",
"phone": "+15551234567"
}REST alternative (GET /api/v1/sms/code)
Modern integrations can call the dedicated REST route with Bearer auth instead of the action gateway.
curl -X GET "https://telepilotpro.com/api/v1/sms/code?order=205" \ -H "Authorization: Bearer YOUR_API_KEY"
Deposit history
List wallet top-up requests submitted by the authenticated user.
| Parameter | Description | Required |
|---|---|---|
key | Your API key | Yes |
action | Must be `deposits` | Yes |
Example Request
curl -X POST "https://telepilotpro.com/api/v1" \ --data-urlencode "key=YOUR_API_KEY" \ --data-urlencode "action=deposits"
Example Response
{
"success": true,
"deposits": [
{
"deposit_number": "DEP-482910",
"method": "USDT",
"amount": 50,
"status": "pending",
"transaction_id": "0xabc…",
"created_at": "2026-07-11T12:00:00.000Z"
}
],
"balance": "125.5000"
}REST alternative (GET /api/v1/deposits)
Modern integrations can call the dedicated REST route with Bearer auth instead of the action gateway.
curl -X GET "https://telepilotpro.com/api/v1/deposits" \ -H "Authorization: Bearer YOUR_API_KEY"
Submit deposit proof
Submit a wallet top-up proof for manual verification. Minimum $5.00, maximum $100,000. Funds are credited after admin approval.
| Parameter | Description | Required |
|---|---|---|
key | Your API key | Yes |
action | Must be `deposits` | Yes |
method | Payment method (e.g. USDT, BTC) | Yes |
amount | Amount in USD | Yes |
transactionId | Transaction hash or proof ID | Yes |
note | Optional note | No |
Example Request
curl -X POST "https://telepilotpro.com/api/v1" \ --data-urlencode "key=YOUR_API_KEY" \ --data-urlencode "action=deposits"
Example Response
{
"success": true,
"deposit_number": "DEP-482910",
"message": "Deposit proof submitted. Funds will be added after verification."
}REST alternative (POST /api/v1/deposits)
Modern integrations can call the dedicated REST route with Bearer auth instead of the action gateway.
curl -X POST "https://telepilotpro.com/api/v1/deposits" \
-H "Authorization: Bearer YOUR_API_KEY" \
-H "Content-Type: application/json" \
-d '{"method":"USDT","amount":"50","transactionId":"0xabc123…","note":"TRC20 transfer"}'Software licenses
List software product licenses purchased on TelePilot Pro.
| Parameter | Description | Required |
|---|---|---|
key | Your API key | Yes |
action | Must be `licenses` | Yes |
Example Request
curl -X POST "https://telepilotpro.com/api/v1" \ --data-urlencode "key=YOUR_API_KEY" \ --data-urlencode "action=licenses"
Example Response
{
"success": true,
"licenses": [
{
"license_key": "TP-XXXX-XXXX",
"status": "active",
"product_name": "TelePilot Pro",
"plan_type": "lifetime",
"expires_at": null,
"order_number": "ORD-123456"
}
]
}REST alternative (GET /api/v1/licenses)
Modern integrations can call the dedicated REST route with Bearer auth instead of the action gateway.
curl -X GET "https://telepilotpro.com/api/v1/licenses" \ -H "Authorization: Bearer YOUR_API_KEY"