API Playground: try social media API methods in the browser
The API Playground is an interactive workspace inside the socialift.uz dashboard. It brings together 191 methods across Facebook, Instagram, LinkedIn, TikTok, Telegram accounts and bots, CRM leads and connected accounts with their documentation, sends real requests and shows them as cURL and JavaScript plus the matching Python SDK call. In the “Kalitlar” (Keys) section you add the keys of your own developer apps.
Updated:
What is the API Playground and why use it?
The API Playground lets you call a social media API method straight from the browser without writing code. You pick a method, choose which connected account to act as, fill in the form and send a real request. The response shows the status, timing, headers and JSON, next to the same request as cURL and JavaScript plus the matching Python SDK example.
Requests are real: a post really gets published and a message really gets sent. That is why destructive and budget-affecting actions ask for explicit confirmation before they go out.
The Playground does not replace writing code. It is for exploring a method, checking that your permissions are sufficient and finding errors quickly; in production the same calls run through the Python SDK.
What's inside the Playground
191 documented methods
For each method: what it does, the pitfalls to watch for and which permissions or scopes it requires.
Schema-driven forms
Forms are generated from the real API schema; switch to a raw JSON editor or file upload when you need to.
Account picker
Choose which connected account the request is sent as.
Response viewer
Status, duration, headers and a readable JSON viewer.
Code in three flavours
cURL and JavaScript fetch reproduce the exact request you sent (to Socialift's server API, with your dashboard JWT); the Python tab shows the method's SDK equivalent (available for most methods).
Deep links and history
Deep links to a method and a recent-request history kept in this browser.
Which methods you can try
| Section | Method groups |
|---|---|
| Connection, Pages and webhooks, posts, stories, comments, Lead Ads, ads (targeting, campaigns, audiences and insights) | |
| Connection, profile and insights, posts, stories, comments, Direct | |
| Connection, profile, posts | |
| TikTok | Connection and profile, videos and insights, publishing, comments (Business) |
| Telegram account | Connection, messages, stories, groups and channels, members and moderation, contacts and sessions |
| Telegram bot | Connection, messages, chats and moderation, webhook and universal call |
| CRM and leads | Leads |
| Connected accounts | Accounts |
Notes and limits
191 methods in total. Destructive and budget-affecting actions ask for explicit confirmation before they are sent. Story endpoints are testable here too: POST and GET /instagram/media/stories for Instagram; POST /facebook/stories/photo, POST /facebook/stories/video and GET /facebook/stories for Facebook; and for Telegram accounts GET, POST and PATCH /telegram/stories, POST /telegram/stories/delete, plus GET /telegram/stories/can-send and GET /telegram/stories/targets, which check the conditions before you post.
Keys: bring your own developer apps
In the “Kalitlar” (Keys) section you add your own app keys for each platform. Secrets are stored encrypted and never shown back in full.
- Meta app
- App ID, app secret and an optional Facebook Login for Business configuration ID.
- Instagram Login app
- Instagram app ID and app secret — for connecting an Instagram account without a Facebook Page.
- LinkedIn app
- Client ID and client secret.
- TikTok app
- Client key and client secret.
- Telegram API
- api_id and api_hash — for connecting a Telegram account. Bots need no keys here: the bot token is enough.
What your own app gives you
Your brand on the login dialog
When granting access, users see the name of your app.
A dedicated webhook URL for your app
Meta, Instagram and TikTok events arrive at a Socialift URL dedicated to your app and are verified with your app secret. Currently only Lead Ads leads are exposed from them (GET /crm/leads); to receive other events yourself, point the callback URL at your own endpoint and use the SDK's verify_request / verify_tiktok_request helpers.
One-click verification
Keys are checked with the provider itself: a client-credentials request at Meta, Instagram Login, LinkedIn and TikTok, MTProto at Telegram. The result is “tekshirilgan” (verified), “rad etilgan” (rejected) or no definite answer (the real check happens at first login).
Console values ready to paste
The page shows the exact redirect URI for the provider console; once keys are saved, Meta, Instagram and TikTok also get a webhook URL and verify token, and Meta gets deauthorize and data-deletion URLs.
Works without keys too
Without your own keys, Socialift's shared app is used wherever one is available.
Connections and usage statistics
On the “Ulanishlar” (Connections) page, Facebook (together with your Pages and their linked Instagram accounts), Instagram without a Page, LinkedIn and TikTok connect via OAuth, a Telegram account through phone → code → 2FA, and a Telegram bot with its token. Tokens stay encrypted on the server and never reach the browser.
The “Statistika” (Statistics) page shows SDK token activations separately from Playground and API calls, with error counts. On the “Tokenlar” (Tokens) page, the “Tekshirish va muhitlar” (Check and environments) button shows the token status and which environments (seats) are in use — the check itself does not take a seat. Every section is covered in the dashboard guide.
Your first real request in four steps
Sign in to the dashboard
Sign in at socialift.uz with Google or email and open the dashboard.
Add your keys
Enter your app keys on the “Kalitlar” (Keys) page and verify them in one click — or skip this step where the shared app is available.
Connect an account
On the “Ulanishlar” (Connections) page connect Facebook, Instagram, LinkedIn, TikTok, a Telegram account or a bot.
Call a method
In the Playground pick a method and an account, fill in the form, send the request and copy the generated code.
Using the Playground well
- Requests are real — experiment on a separate Page, account or bot.
- Before confirming a delete or a budget change, double-check the parameters.
- Read the pitfalls and required permissions in each method's docs — they explain the cause of many errors.
- Share the exact request with a teammate through a deep link to the method.
- No definite answer from the key check does not mean the key is wrong — the provider does not confirm it up front, and the real check happens at first login.
- Use the Python SDK in production — that is what the Python tab is for; the cURL/JavaScript samples call Socialift's server API with your dashboard JWT.
Frequently asked questions
Are Playground requests real?
Yes. A post really gets published and a message really gets sent. That is why destructive and budget-affecting actions require explicit confirmation before they are sent.
Does the Playground replace writing code?
No. The Playground is for exploring and testing methods. Production uses the Python SDK — the Playground shows the method's SDK equivalent (where one exists) and your request as cURL/JavaScript.
Why would I add my own app keys?
With your own app, your brand appears on the login dialog, and Meta/TikTok webhooks arrive at a URL dedicated to your app and are verified with your secret. Without your keys, Socialift's shared app is used wherever one is available.
How are keys and tokens stored?
App secrets are stored encrypted and never shown back in full. Tokens for connected accounts also stay encrypted on the server and never reach the browser.
How does key verification work?
One click checks the keys with the provider itself: a client-credentials request at Meta, Instagram Login, LinkedIn and TikTok, MTProto at Telegram. The result is “tekshirilgan” (verified), “rad etilgan” (rejected) or no definite answer, in which case the real check happens at first login.
What do I need to start using the Playground?
Sign in at socialift.uz with Google or email and connect the account you need on the “Ulanishlar” (Connections) page. No SDK token is required: the Playground works regardless of the token's plan.
Sources
Related pages
Send your first request now
Sign in with Google or email, connect an account and try any method in the Playground.
Open the Playground →