The Socialift dashboard: what each section does
The Socialift dashboard (socialift.uz/dashboard) has seven sections: “Tokenlar” (Tokens) for SDK license keys, “Playground” for trying 191 methods without code, “Ulanishlar” (Connections) for accounts and bots, “Kalitlar” (Keys) for your own developer app keys, “Statistika” (Usage) for SDK activations and API requests, “Hisob” (Billing) for balance and payments, and “Qo'llanma” (Guide) for getting started.
Updated:
What is the dashboard for?
Two jobs. First, getting a license key for the SDK and tracking its state (“Tokenlar”, “Statistika”, “Hisob”). Second, trying methods on real accounts without writing code (“Ulanishlar”, “Kalitlar”, “Playground”). Accounts and keys connected in the dashboard stay on the Socialift server: the SDK in your own app does not use them and works with your own keys and tokens.
The dashboard interface is in Uzbek, so menu items and buttons below are named exactly as they appear on screen, with a translation in parentheses.
Sections at a glance
| Section | Path | What it does |
|---|---|---|
| “Tokenlar” (Tokens) | /dashboard | Get, reveal, extend and check license keys |
| “Playground” | /dashboard/playground | Docs, a form and a live request for 191 methods |
| “Ulanishlar” (Connections) | /dashboard/connections | Connect Facebook, Instagram, LinkedIn, TikTok, a Telegram account and a bot |
| “Kalitlar” (Keys) | /dashboard/apps | Store and verify your own developer app keys |
| “Statistika” (Usage) | /dashboard/usage | SDK activations and Playground/API requests, with errors |
| “Hisob” (Billing) | /dashboard/billing | Balance and top-ups |
| “Qo'llanma” (Guide) | /dashboard/guide | Install, key setup and first-call examples |
“Tokenlar” (Tokens): license keys
“Yangi token” (New token) creates a license key: the first month is free with every SDK feature unlocked, and the token comes with 1 seat. You can have up to 5 active tokens at a time. Each card shows the key_id, plan, status, a “bepul sinov” (free trial) badge and the days left.
“Kalitni ko'rsatish” (Show key) reveals the full slk_... key and “Nusxa” (Copy) copies it. “30 kunga uzaytirish” (Extend for 30 days) charges your balance and adds 30 days — on top of the remaining term if it has not expired, or from today if it has (the button then reads “Qayta faollashtirish”, Reactivate). If the balance is too low you get a message, and the “Hisobni to'ldirish” (Top up) link is right there. A renewed token's features depend on its plan, and the key is re-signed with the same key_id: SDK 1.3+ picks up the new expiry from the server automatically, while with the 1.2.x release on PyPI or SOCIALIFT_LICENSE_OFFLINE=1 you replace SOCIALIFT_LICENSE_KEY with the new key from “Kalitni ko'rsatish” (Show key).
“Tekshirish va muhitlar” (Check and environments) does not use a seat. It shows whether the key works with the SDK, the plan, seats in use, the lease length, the last activation, open features and a table of the environments holding seats. When every seat is taken, it warns that a new server or container will be refused.
“Playground”: 191 methods without code
On the left is the method list: search, a platform filter (Facebook, Instagram, LinkedIn, TikTok, Telegram account, Telegram bot, CRM and leads, connected accounts) and groups. A selected method shows its HTTP method and path, action type, required permissions (scopes), documentation and notes.
In the “So'rov” (Request) panel, the “Qaysi akkaunt nomidan” (On behalf of which account) list shows matching connected accounts; if none match, a link to “Ulanishlar” (Connections) appears. Fill parameters in a form or as JSON. “Yuborish” (Send) sends the request through the Socialift server to the real platform on behalf of your account.
The “Javob” (Response) panel shows the status code, time (ms), size, body and headers; file responses such as images are previewed and downloadable. The “Kod” (Code) panel has three tabs: “Python SDK” — SDK code that calls the platform directly (keys and tokens live in your app); “cURL” and “JavaScript” — the exact Socialift server API request the Playground sends, with the dashboard session JWT. Some actions exist only in the server API, and the Python tab says so.
The recent request history and the account chosen for each method are stored only in your browser (localStorage).
Playground action types and confirmations
| Label | Meaning | Before sending |
|---|---|---|
| “Faqat o'qiydi” (Read only) | Changes nothing | No confirmation |
| “O'zgartiradi” (Modifies) | A real change on the platform: a post, a message, a setting | No confirmation — but the request is real |
| “O'chiradi” (Deletes) | Irreversible; red dot in the list | “Yuborish” stays disabled until “Tushundim, yuborilsin.” (I understand, send it) is ticked |
| “Byudjetga ta'sir” (Affects budget) | May spend ad budget; amber dot in the list | “Yuborish” stays disabled until “Tushundim, yuborilsin.” is ticked |
| “Ulanish” (Connection) | Works with a connection or token | No confirmation |
Notes and limits
The confirmation resets after every send. Other sections are guarded too: “Uzish” (Disconnect) in “Ulanishlar” opens a browser confirmation dialog, and in “Kalitlar” deleting a key that has connected accounts stops with a list of those accounts and continues only via “Baribir o'chirish va uzish” (Delete anyway and disconnect).
“Ulanishlar” (Connections): how do you connect accounts?
Facebook, “Instagram (Page'siz)” (Instagram without a Page), LinkedIn and TikTok connect through OAuth with the “Ulash” (Connect) button. After connecting Facebook, press “Page'larni sinxronlash” (Sync Pages) to add your Pages and the Instagram accounts linked to them. “Instagram (Page'siz)” connects a professional (Business or Creator) account through Instagram Login.
“Telegram akkaunt” (Telegram account): phone number → confirmation code (usually delivered inside the Telegram app, not by SMS) → your password if two-step verification is on. “Telegram bot”: the token from @BotFather, no app key needed. If the bot only sees messages addressed to it in groups, the dashboard suggests turning off Group Privacy in BotFather.
Tokens are stored encrypted on the server and never sent to the browser. Each account row shows the token expiry date (or “muddatsiz”, no expiry), a “qayta ulash kerak” (reconnect required) badge, “Token'ni yangilash” (Refresh token — for Instagram without a Page, LinkedIn and TikTok), a shortcut to the Playground and “Uzish” (Disconnect). Disconnecting a Telegram account also ends the Telegram session; for a personal Facebook account and TikTok, the granted access is revoked.
When a platform has both your own app and the Socialift app available, the card shows a “Qaysi kalit bilan” (Which key) choice: “O'z app'im” (My app) or “Socialift app'i” (Socialift app).
“Kalitlar” (Keys): your own developer app or Socialift's shared app?
“Kalitlar” stores your own keys for five providers: “Meta (Facebook) app”, “Instagram Login app”, “LinkedIn app”, “TikTok app” and “Telegram API (my.telegram.org)”. With your own app, the login dialog shows your app's name, webhooks are signed with your secret and the rate limits are yours. Without a key, Socialift's shared key is used (when available).
Fields: client ID, secret, optionally config_id and scopes, a name and an “Faol” (Active) checkbox. The secret is stored encrypted and is never returned in full — only its last characters are shown; leave the field empty to keep it unchanged.
“Saqlash va tekshirish” (Save and verify) checks the key with the provider itself. There are three outcomes: verified, rejected, or cannot be checked in advance (a network error, for example) — the last is never presented as either valid or broken. The status label reads “O'z kalitingiz ishlatiladi” (Your key is used), “Socialift kaliti ishlatiladi” (Socialift key is used) or “Sozlanmagan” (Not configured).
The right-hand panel has “Qanday olinadi” (How to get it — steps with a console link) and “Konsolga ko'chiring” (Copy to the console): depending on the provider, the Redirect URI, Webhook URL, Webhook verify token, Deauthorize callback and Data deletion callback. The Webhook URL and verify token appear after the key is saved.
Which key does a new connection use?
1. Your key
If “Kalitlar” has an active key for the provider, that key is used.
2. Socialift's key
If you have no key or it is inactive, Socialift's shared key is used (when available).
If both exist
You pick “O'z app'im” or “Socialift app'i” on the card in “Ulanishlar”.
If neither exists
The card says “Kalit sozlanmagan” (Key not configured) and links to “Kalitlar”.
After connecting
An account stays bound to the app it was connected through: Meta's
appsecret_proofand TikTok and LinkedIn token refresh all need that exact app's secret. Making your key inactive keeps existing accounts working while new connections switch to Socialift's key. Deleting a key that has connected accounts disconnects them, and their tokens stop working.
“Statistika” (Usage): what is counted and what is not?
| Source | Counted | How |
|---|---|---|
| SDK license activations | Yes | At startup and on every lease renewal (12 hours by default), per token; rejected activations of a correctly signed key count as errors |
| Playground and the server API with the dashboard JWT | Yes | Platform endpoints only (Facebook, Instagram, LinkedIn, TikTok, Telegram, CRM), per user |
| Every SDK call to the platforms | No | The SDK does not go through the Socialift server — only activations are visible |
| The dashboard's own requests | No | Profile, tokens, billing, usage, keys and the Playground catalog |
| Webhooks and anonymous requests | No | They are made by the platforms or unknown clients |
Notes and limits
An error is a request that ended with HTTP 4xx or 5xx. Endpoints are stored as route templates, not with IDs (for example /facebook/posts/{post_id}); requests with no matching route are grouped into a single “(noma'lum endpoint)” (unknown endpoint) row.
What does the “Statistika” page show?
Period: 7, 30 or 90 days. Four tiles at the top: total requests, errors (with a percentage), “SDK aktivatsiyalari” (SDK activations) and “Playground / API”. The “Kunlik so'rovlar” (Daily requests) chart shows SDK and Playground/API in different colours and switches to a “Jadval” (Table) view.
The “Kalitlar bo'yicha” (By key) table lists requests, errors and the last active day for each source (a token or a user); “Eng ko'p ishlatilgan endpoint'lar” (Most used endpoints) lists method, endpoint, requests and errors.
“Hisob” (Billing) and “Qo'llanma” (Guide)
“Hisob” shows your current balance. To top up, enter an amount in Uzbek sum, choose the card type (Humo or Uzcard) and press “Davom etish” (Continue). The dashboard shows a card number and an exact amount — transfer exactly that amount, because the system matches the payment by amount — then press “To'ladim — tekshirish” (I've paid — check). If the chosen amount is already taken, the dashboard suggests nearby alternatives. The balance pays for “30 kunga uzaytirish” (Extend for 30 days).
“Qo'llanma” has a Playground link, a token check that uses no seat (plan, seats, days left, features), install commands, SOCIALIFT_LICENSE_KEY and SOCIALIFT_INSTANCE_ID setup, first-call examples for Facebook/Instagram, TikTok, Telegram and ads, an error-handling example and the support address hello@socialift.uz.
How do you move code from the Playground into your app?
The code on the “Python SDK” tab calls the platform directly. When you copy it into your app, move keys and tokens out of the code into environment variables.
import asyncio
import os
from socialift import Telegram
async def main():
# In the Playground: bot = Telegram(token="123456:AA...") and me = await bot.get_me()
async with Telegram(token=os.environ["TELEGRAM_BOT_TOKEN"]) as bot:
me = await bot.get_me()
print(me["username"])
asyncio.run(main())Your app also needs SOCIALIFT_LICENSE_KEY — get it under “Tokenlar” (Tokens). A bot or account connected in the dashboard is not passed to the SDK: you need to hold the token yourself.
Dashboard safety notes
- Do not paste a revealed
slk_...key into chats or repositories; if it leaks, email hello@socialift.uz. - Playground requests are real: methods labelled “O'zgartiradi” (Modifies) also publish posts and send messages.
- For “O'chiradi” (Deletes) and “Byudjetga ta'sir” (Affects budget), tick the confirmation only after checking the request body.
- Platform tokens and app secrets are encrypted on the server: tokens never reach the browser and secrets are never shown in full.
- Disconnect accounts you no longer need with “Uzish” (Disconnect) — for a Telegram account this also ends the session.
Frequently asked questions
Can I use a token from an account connected in the dashboard in my own code?
No. Dashboard tokens are stored encrypted on the server and are not even sent to the browser. In your own app you obtain tokens through OAuth (login_url() → exchange_code()) and keep them in your database.
Does “Tekshirish va muhitlar” (Check and environments) use a seat?
No. It does not call the SDK activation and only reads the stored state, so you can press it as often as you like. Only a real SDK activation in a new environment takes a seat.
Are Playground requests real or sandboxed?
Real: the request goes through the Socialift server to the platform on behalf of the account you connected — posts get published and messages get sent. That is why deleting and budget-affecting actions require a separate confirmation.
What happens to already connected accounts when I add my own app key?
They keep working, bound to the app they were connected through. The new key is used for later connections; to move an account to your own app, reconnect it.
Why does “Statistika” (Usage) show so few SDK calls?
The SDK calls Instagram, TikTok and the other platforms directly, not through the Socialift server. Only license activations are counted — at startup and on every lease renewal (12 hours by default). Per-method statistics exist only for the Playground and the server API.
I topped up, but my balance did not change. What should I do?
Check that you transferred exactly the amount the dashboard showed to the card it displayed — the system matches payments by amount. Then press “To'ladim — tekshirish” (I've paid — check); if the payment is not found yet, the dashboard tells you. If the problem persists, email hello@socialift.uz.