Getting started
Authentication
Authenticate every request with your secret key as a bearer token. Keys are prefixed sc_live_ (production) and sc_test_ (sandbox).
Bearer token
[ .HTTP ]
Authorization: Bearer sc_live_xxxxxxxxxxxxxxxxxxxxHandling keys
- Keep keys server-side. Never ship them in a browser, mobile app, or public repo.
- SocialiQ handles all platform access and auth — you only manage your SocialiQ key.
- A missing or invalid key returns
401withmissing_api_keyorinvalid_api_key.
MCP connections
MCP clients can connect through https://api.socialiq.dev/mcp and authorize with SocialiQ OAuth instead of copying an API key. See the MCP server guide for setup details.