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
-
Read the relevant operation in the OpenAPI document.
-
Start with GET requests to find identifiers.
-
Send Authorization: Bearer YOUR_API_KEY.
-
Send X-Workspace-Id: YOUR_WORKSPACE_ID.
-
For a write, generate an Idempotency-Key unique to that action.
-
Send the request and store the returned request_id.
-
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.