Schedule social media posts with an API call

1. 1

   Pick targets by slug

   List connections with the API, CLI or MCP and copy the slugs (for example facebook-mypage). Slugs stay stable, so a stored schedule job never breaks when a token is refreshed.
2. 2

   Send scheduledAt and an optional timezone

   scheduledAt must be a future ISO 8601 datetime. Add a timezone such as America/New_York if you want the schedule to follow local time.
3. 3

   Edit or publish early while it is still scheduled

   PATCH /api/content/:id changes the caption or time. POST /api/content/:id/publish-now sends it immediately. Deleting it cancels the schedule.
4. 4

   Get told when it lands

   Poll GET /api/content/status?requestId=..., or on the Business plan subscribe a signed webhook to upload.completed and upload.failed.

curl -X POST https://api.socifyr.com/api/content/text \
  -H "Authorization: Bearer sk_your_key" \
  -H "X-Workspace-Id: your_workspace_id" \
  -H "Content-Type: application/json" \
  -d '{
    "connections": ["facebook-mypage", "linkedin-mybrand"],
    "text": "Webinar starts in one hour. Link in comments.",
    "scheduledAt": "2026-12-01T14:00:00Z",
    "timezone": "America/New_York"
  }'

import { Socifyr } from '@socifyr/sdk'

const socifyr = new Socifyr({
  apiKey: process.env.SOCIFYR_API_KEY!,
  workspaceId: process.env.SOCIFYR_WORKSPACE_ID!,
})

const scheduled = await socifyr.uploads.text({
  connections: ['facebook-mypage', 'linkedin-mybrand'],
  text: 'Webinar starts in one hour. Link in comments.',
  scheduledAt: '2026-12-01T14:00:00Z',
  timezone: 'America/New_York',
})

socifyr post "Webinar starts in one hour." \
  --to facebook-mypage,linkedin-mybrand \
  --at 2026-12-01T14:00:00Z

Schedule "Webinar starts in one hour. Link in comments." for
2026-12-01 at 14:00 UTC on facebook-mypage and linkedin-mybrand.

Replace sk_your_key and the workspace ID with your own from the dashboard, and use your own connection slugs.

• Product teams with a release calendar

  Schedule announcement posts from the same repo that ships the release.

• Developers adding "post later" to an app

  Expose scheduling to your own users without building a queue, retry logic and per-platform rules yourself.

• Anyone replacing a manual scheduler with code

  Keep the content in git or a CMS and let a job place it on the calendar.