Use this file to discover all available pages before exploring further.
This quickstart gets you calling the SocialAPI.ai unified social media API in minutes: one key, one base URL, and the same Interaction schema for comments, DMs, mentions, and reviews across every connected platform.This walks you from zero to a published post in seven steps. By the end you will have a working API key, a connected social account, a comment listed and replied to, and a post live on at least one platform. Total time: about five minutes if your social account is ready, ten if you need to create one.
In the dashboard, go to Keys, then New Key. Give it a name and click Create.
Copy the key immediately, it is shown only once. It starts with sapi_key_.
Store it in your environment:
export SOCAPI_KEY="sapi_key_your_key_here"
If the dashboard does not show a key after creation, refresh the Keys list. The key value itself is shown only once; if you missed it, revoke and create another.
No platform developer app required. Click Connect and you’re authorizing through SocialAPI’s pre-approved app. Twitter is the one exception - it requires a one-time BYOK setup. See Platform credentials for the full story.
In the dashboard, go to Accounts, then Connect, and choose your platform. Complete the OAuth flow in your browser.Or connect programmatically:
The response includes an auth_url. Redirect the user there to complete OAuth.
If auth_url is missing from the response, check that platform matches one of instagram, facebook, threads, google, tiktok, linkedin, youtube, twitter. See OAuth flows for the full handshake.
To reply to a specific comment in step 6, use the platform_id value above (or pass a sapi_cmt_... interaction ID, both are accepted).
If data is empty, the account has no comments yet, or the post being queried has none. Try a different account_id, or post a comment from another account first.
If you receive 501 not_supported, the platform does not allow programmatic reply for that interaction type. Check capabilities.can_reply on the comment first.
The platform for each target is inferred from account_id, no platform field is required. Set scheduled_at instead of publish_now to queue the post for later. Omit both to save as a draft.
If status is failed, inspect targets[].error for the per-platform reason. The most common failure is missing required fields per platform: see Posts.
You now have a working integration: an API key authenticated through SocialAPI, a connected social account whose tokens we manage for you, the ability to read and respond to comments, and the ability to publish posts. Everything else in the docs builds on these primitives.If you want to understand the data model behind what you just used, read Core concepts. It explains the five nouns the API exposes (Brand, Account, Post, Interaction, Capability) in about five minutes.