Social media posting API: one REST call, 18 platforms

Create an API key in the dashboard under Settings, API Keys. It starts with sk_ and is shown once. Send it as a Bearer token, together with your workspace ID.

Authorization: Bearer sk_your_key
X-Workspace-Id: <workspaceId>
Content-Type: application/json

The base URL is https://api.socifyr.com/api. Keys are scoped to one workspace. Rotate a key by creating a new one, deploying it, then deleting the old one; both work in parallel until you delete the old one.

curl -X POST https://api.socifyr.com/api/content/text \
  -H "Authorization: Bearer sk_your_key" \
  -H "X-Workspace-Id: <workspaceId>" \
  -H "Content-Type: application/json" \
  -d '{
    "connections": ["linkedin-myhandle", "x-myhandle"],
    "text": "Just shipped"
  }'

{
  "success": true,
  "data": {
    "success": true,
    "requestId": "97005ec5-6361-4953-8a69-ce7292ad9f11",
    "uploadId": "6a05033584584482ace13d72",
    "usage": { "count": 7, "limit": -1, "remaining": -1 }
  }
}

Images go to POST /content/photos and video to POST /content/video. Both accept a JSON body with media library IDs or public URLs in medias, or multipart/form-data with raw files. A video post takes exactly one entry in medias.

curl -X POST https://api.socifyr.com/api/content/text \
  -H "Authorization: Bearer sk_your_key" \
  -H "X-Workspace-Id: <workspaceId>" \
  -H "Content-Type: application/json" \
  -d '{
    "connections": ["linkedin-myhandle"],
    "text": "Goes live Tuesday at 9",
    "scheduledAt": "2026-12-01T09:00:00-05:00",
    "timezone": "America/New_York"
  }'

scheduledAt is ISO 8601 and may carry a UTC offset. timezone is an IANA name used for display in the dashboard. Scheduling is available on Pro and Business; on the Free plan the API rejects a request with scheduledAt. For many posts at once, POST /content/bulk-schedule takes up to 500 rows or a CSV string. See how to schedule social media posts with an API.

curl "https://api.socifyr.com/api/content/status?requestId=97005ec5-6361-4953-8a69-ce7292ad9f11" \
  -H "Authorization: Bearer sk_your_key" \
  -H "X-Workspace-Id: <workspaceId>"

The result carries an overall status and one entry per account under channels, each with result.status, result.postUrl and result.error. Statuses move through queued, pending, processing and publishing to completed, partial_failure or failed. A scheduled post waits in the queue until its time; there is no separate "scheduled" status. To retry only the failed channels, call POST /content/:id/retry.

{
  "success": false,
  "error": "Connection \"nonexistent-slug\" not found",
  "statusCode": 400,
  "path": "/api/content/text",
  "timestamp": "2026-11-13T10:00:00.000Z"
}

Validation failures return error as an array of strings, one per problem. Server errors (5xx) also include a requestId for log correlation.

Publishing endpoints allow 60 requests per minute by default, and the list and fetch endpoints (GET /content, GET /content/:id) allow 240 per minute. A request over the limit gets a 429 with a Retry-After header in seconds. Separately, each platform has its own daily posting cap that Socifyr enforces for you, and your plan caps monthly uploads. See daily posting limits per platform and the plan limits.

# Try a silent renewal first
curl -X POST https://api.socifyr.com/api/workspaces/<workspaceId>/connections/instagram-mybrand/refresh \
  -H "Authorization: Bearer sk_your_key" \
  -H "X-Workspace-Id: <workspaceId>"

# If it cannot refresh, get a one-time link for the owner
curl -X POST https://api.socifyr.com/api/oauth/connections/instagram-mybrand/reconnect-link \
  -H "Authorization: Bearer sk_your_key" \
  -H "X-Workspace-Id: <workspaceId>"

The second call returns { url, expiresIn, platform, slug }. Only the workspace owner can approve the link, and keys with guardrails cannot create one. Read OAuth token expiry and how to refresh or reconnect accounts.