Frequently asked questions

Instagram, Facebook, LinkedIn, TikTok and Telegram (account and bot), plus Facebook and Instagram ads through the Meta Marketing API. Capabilities differ by platform — for example, chat exists on Instagram Direct and Telegram but not on LinkedIn.

Yes, but the connection runs in your backend: Socialift has no ready-made CRM connector. Your server receives Meta webhooks (verify with verify_request, split with parse_events), reads messages, comments or leads through the SDK and writes them to the CRM's API. Direct and comments work with Instagram Login or a Page-linked account; Lead Ads need a Facebook Page. For accounts you don't own, Meta requires Advanced Access (App Review and Business Verification).

There is no universal answer — what matters is that the CRM has an open API (or accepts inbound webhooks). Your backend then uses the Socialift SDK to read Direct, comments and Lead Ads and writes them to that API. A CRM with neither an API nor webhook intake cannot be integrated.

There are three sources: Lead Ads forms (the leadgen webhook carries only IDs, so you fetch the lead with fb.lead), questions in Direct and comments under posts (the messages and comments webhooks). Your backend turns each event into a lead or deal through the CRM's API.

Meta sends a messages webhook to your server. Your code verifies it with verify_request, splits it with parse_events, can fetch the sender's profile with ig.contact(igsid, token) and writes a contact and conversation to the CRM's API. Socialift does not forward messages to your endpoint itself.

No. The Instagram API works only with professional accounts (Business or Creator). A Facebook Page is required only with Facebook Login; Instagram Login (Instagram(app_id, app_secret) in the SDK) works without a Page but cannot access ads.

Yes, within 24 hours of the user's last message, and only in conversations the user started. A human agent can reply for up to 7 days with the HUMAN_AGENT tag (requires App Review), and a comment can get one private reply within 7 days — automated messages outside these windows are not allowed.

A webhook is a POST request the platform sends to your HTTPS address the moment an event occurs. The body carries the payload and the header carries a signature. You verify the signature and return 200.

Most often the signature is computed over re-serialised JSON rather than the raw body. Other causes: the wrong app secret, or a proxy modifying the request body.

Yes. Meta retries failed deliveries for up to 36 hours, so the same event can arrive more than once. Deduplicate by a stable key from the payload (e.g. leadgen_id, message mid, comment ID) — socialift.webhooks.dedupe_key() builds it.

Not always. With Facebook Login for Business one OAuth flow covers Pages and the Instagram accounts linked to them (Instagram.via_facebook in the SDK). Instagram accounts without a Page connect through the separate Instagram Login, which cannot access ads.

No. LinkedIn's Messages API is restricted to approved partners, so Socialift does not offer it. For LinkedIn, OAuth, profile data and content publishing are available.

Yes. Videos go by URL (the domain must be verified) or by file upload; photo carousels and drafts are supported. Your app must call creator_info() before posting, and until TikTok audits it, posts are SELF_ONLY, limited to 5 users per 24 hours and to private accounts. Comments and insights require a Business account.

An account connects with a phone number, code and 2FA: it reads the full history of chats it belongs to and member lists where admins haven't hidden them, creates groups and channels, moderates members, and sends scheduled messages and polls. A bot connects with its BotFather token: messages, files, moderation and webhooks with a per-bot secret — but bots cannot see full history or member lists. Using an account from the SDK requires pip install "socialift[telegram]".

Yes, through the Meta Marketing API for Facebook and Instagram: targeting search by interest, location and language, reach estimates without spending, campaigns, ad sets, ads and creatives (created PAUSED), one-call Instagram post boosts, and custom and lookalike audiences.

A test environment inside the dashboard: for each of 191 methods you get docs (what it does, pitfalls, required permissions), a form generated from the real API schema, a choice of which connected account to act as, a real request with a response viewer, and code as Python SDK, cURL or JavaScript. Destructive and budget actions ask for confirmation.

For Meta, yes if the app must work with accounts of people who have no role in it: Standard Access covers only accounts you own or that have an app role, and Advanced Access requires App Review and Business Verification. TikTok needs a separate audit for public posts, and LinkedIn approves products such as the Community Management API individually.

No. Socialift is an independent integration layer built on the public Meta, LinkedIn, TikTok and Telegram APIs and is not an official partner of any of them.

Today there is an official Python package: pip install socialift.

A new token from the dashboard needs no card: for the first 30 days it runs in trial mode and unlocks every SDK feature — core methods, webhook helpers, publishing, Instagram Direct, Telegram accounts (TelegramAccount), insights, ads and Lead Ads. After that you renew it in 30-day periods from your balance: the price is shown in the dashboard, and features depend on the token's plan — the exact list appears under “Tekshirish va muhitlar” (Check and environments) next to the token in the dashboard. The dashboard Playground works on any plan.

The token moves to an expired state and SDK calls are rejected. To continue, top up your balance and renew the token in the dashboard.

Social network tokens and Telegram sessions connected in the dashboard, and the app keys you add there, are stored encrypted on the server, never sent to the browser, and used only for the operations you request. The SDK itself stores nothing — when you use it, tokens stay in your application. See the privacy policy for details.

On 429, 5xx and Meta limit errors (codes 4, 17, 32, 613) the SDK makes up to 3 attempts with exponential backoff. If RateLimitError still reaches you, retry_after is set only when the platform sent a Retry-After header — Meta usually doesn't, and its limits use a rolling one-hour window, so back off for minutes, not seconds.