SMM API for resellers: how to launch your own service store with TGLift

The TGLift API is designed for agencies, SMM panel owners, developers and entrepreneurs who want to sell promotion services through their own interface. Instead of transferring each order manually, your server can fetch the catalog, create orders, monitor progress and display results automatically.

In the public integration, TGLift is the service supplier for your account. Your customer uses your website, application or bot, while your backend communicates with TGLift. The API contract uses TGLift services, prices, order IDs and statuses; internal processing is outside the public contract.

Open the TGLift API →

What you can build with the SMM API

One API can power several types of products. You choose the format, target market and retail model:

• your own SMM store with catalog, search, filters, balance and order history;
• a Telegram bot or Mini App for ordering services inside Telegram;
• an agency panel for managers and recurring customers;
• an internal CRM integration for automated order transfer;
• a focused niche service for Telegram, TikTok, Instagram or another platform.

Two ways to launch

1. Build the integration yourself

If you have a developer, use the TGLift API documentation and the OpenAPI 3.1 specification. You create the interface, select categories, configure your markup and connect ordering methods to your backend.

2. Order a turnkey store from TGLift

If you do not have a development team, you can order a complete project. Based on an agreed specification, we can prepare a branded interface, catalog, customer accounts, balance, payment flow, order creation and tracking, administration, notifications and deployment.

The exact scope, design, payment methods, schedule and cost are agreed after reviewing your requirements. This option is suitable when you need a working store under your own brand, not only an API key.

What the TGLift API provides

The current REST contract covers the core reseller workflow:

• GET /api/v1/services returns available TGLift services, categories, public rates, currency, limits, descriptions and required order fields.
• GET /api/v1/balance returns the available account balance.
• POST /api/v1/orders validates parameters, charges the balance and creates an order.
• GET /api/v1/orders returns paginated order history.
• GET /api/v1/orders/{RQ-ID} returns status, remains, start count, charge and refunded amount for one order.
• POST /api/v1/orders/{RQ-ID}/cancel requests cancellation when the service supports it.
• POST /api/v1/orders/{RQ-ID}/refill requests a refill when the service includes refill support.

The catalog includes an orderRequirements object. It tells your application what a service requires: link, quantity, comments, keywords, poll option or other fields. Build order forms from this contract instead of using one fixed set of fields for every service.

A practical integration flow

1. Create a TGLift account and fund its balance.
2. Open the API section and issue a secret key.
3. Fetch the catalog and store selected service IDs, limits and requirements.
4. Display the services in your interface and apply your own retail markup.
5. Validate the link, quantity, additional fields and balance before ordering.
6. Send the order with the X-API-Key and Idempotency-Key headers.
7. Store the returned TGLift RQ order ID and update its status regularly.
8. Show the customer the remains, refund and final state returned by the API.

An idempotency key is especially important for order and payment operations. If the network fails and the request must be retried, the same key allows the API to return the original result without creating a duplicate.

Your markup and store economics

The API returns the public TGLift rate in the selected currency. Your store can add its own markup globally, by platform, category, cost range or individual service. Your project calculates the final price shown to the buyer.

When planning margins, include payment fees, refunds, taxes, support and advertising costs, not only the difference between wholesale and retail prices. Store the customer price, TGLift charge and currency at the time each order is created.

Statuses, cancellation and refunds

A successful creation response means that TGLift accepted the order; it does not mean the order is already completed. Your integration should handle pending, in-progress, partial, canceled, failed and under-review states.

For partial or canceled orders, use the refundedAmount returned by the API instead of estimating a refund. Cancellation and refill availability depends on the selected service and is included in the catalog.

API key security

Keep the secret key on your server only. Never place it in browser JavaScript, a mobile application, a public repository, a URL or screenshots. All TGLift requests should be performed by your backend.

• send the key only through the X-API-Key header;
• use a unique Idempotency-Key for each new order attempt;
• handle HTTP 400, 401, 402, 404, 409, 422, 429 and 5xx responses;
• store the error requestId for support diagnostics;
• revoke and replace the key if compromise is suspected.

Frequently asked questions

Will the buyer see TGLift?

With a proper server-side integration, the buyer interacts only with your project interface. The buyer never receives the API key or calls TGLift directly. Your TGLift account remains the supplier for your store.

Can I sell services with my own markup?

Yes. The API returns the TGLift rate, while your project determines the retail price and markup rules.

Do I need to update the catalog manually?

Synchronize it regularly. Rates, limits, descriptions and availability may change, so order creation should rely on current data.

Can I start without a developer?

Yes. You can begin with the regular TGLift dashboard and later order a turnkey store to move sales into your own interface.

Start your integration

Open the TGLift API documentation, register an account and issue your key. For a complete store, contact us through support and describe your project, target platforms, payment methods and required functionality.