API & MCP

Connect SocioQueue with MCP

MCP lets an AI client work with your SocioQueue workspace using secure OAuth. After you connect, the client can use the workspace tools you approve for content, media, channels, publishing, inbox, and analytics. MCP connections are available on trial and paid workspaces. For Codex CLI, run: codex mcp add socioqueue --url https://api.socioqueue.com/mcp && codex mcp login socioqueue For Claude Code, run: claude mcp add --transport http socioqueue https://api.socioqueue.com/mcp Then run /mcp in Claude Code to sign in. Step-by-step 1. Open Settings, then API and MCP in SocioQueue. 2. Copy the MCP server URL or the command for your AI client. 3. Add the SocioQueue MCP server in the client. 4. Start the client’s sign-in flow. 5. In your browser, choose the SocioQueue workspace and approve access. 6. Return to the AI client and confirm it can list your SocioQueue tools. You can revoke a connected MCP client at any time from Settings → API and MCP. Revoke it immediately if a device or client should no longer have access.

Create and use a personal API key

Personal API keys let your own scripts and integrations call the SocioQueue REST API. API access is available to workspaces on an active paid subscription. Treat a key like a password: never paste it into public code, browser-side apps, or shared chat messages. Create a separate key for each integration or environment. This makes it easier to identify usage and revoke only the key that needs to be retired. SocioQueue shows a newly created key once, so copy it to a password manager or secure secret store immediately. Step-by-step 1. In SocioQueue, open Settings → API and MCP. 2. Under Personal API keys, enter a recognizable key name. 3. Create the key. 4. Copy it immediately and store it in a secure secret manager. 5. Send it only as Authorization: Bearer YOUR_API_KEY. 6. Include X-Workspace-Id with the workspace you want the request to use. 7. Test a read request before enabling write or publishing workflows. If a key is exposed, revoke it from Settings → API and MCP and create a replacement.

Make safe SocioQueue API requests

The SocioQueue REST API is available at https://api.socioqueue.com. It supports workspace content, media, publishing results, and analytics. The OpenAPI document at https://api.socioqueue.com/openapi.json is the source of truth for current request and response shapes. Every API request needs an Authorization bearer token and the X-Workspace-Id header. Use read requests first to confirm workspace, channel, post, and media identifiers before a script creates or changes anything. All write operations require an Idempotency-Key header. Generate a new unique value for each logical action and reuse that value only when retrying the exact same request. SocioQueue keeps the idempotency result for 24 hours and rejects use of a key with different request data. Step-by-step 1. Read the relevant operation in the OpenAPI document. 2. Start with GET requests to find identifiers. 3. Send Authorization: Bearer YOUR_API_KEY. 4. Send X-Workspace-Id: YOUR_WORKSPACE_ID. 5. For a write, generate an Idempotency-Key unique to that action. 6. Send the request and store the returned request_id. 7. Check post results or analytics after a publishing workflow completes. The API exposes rate-limit headers. Back off when you receive a 429 response and respect Retry-After before trying again. Include the structured error code and request_id when contacting support.