Developer API

Social Media Scheduling API

Q: Can I check a schedule before it goes out?

Yes. Send the same schedule to /v1/posts/validate first. It checks the request against each connected provider's rules and reports back without publishing or queuing anything. Send the identical body to /v1/posts/apply once you are happy with it.

Q: How do I avoid publishing the same post twice?

Include an idempotencyKey with your request to /v1/posts/apply. Sending the same key again returns the original run instead of creating a second one, so retrying a request on your end is always safe.

Q: Do I need to host my own images and video?

No. Upload a file to /v1/assets/upload and use the link it returns as your post's media. SocialClaw hosts it for you, so every connected platform always has what it needs the moment your post goes out.

Q: Does every platform accept the same payload?

No. Account types, media rules, and settings differ per provider, which is exactly what /v1/posts/validate checks before anything is scheduled, so a workflow never has to assume one universal payload shape.

Q: How do I know a post actually published?

Check /v1/runs/{runId}/status or /v1/posts/{postId} after your request. Both report whether the platform confirmed the post, so you are never just trusting that a request was accepted.

Q: Where is the full API reference?

Every endpoint, field, and error is documented at /docs/api/reference, generated from the same OpenAPI document the API itself serves at /openapi.json.

Connect accounts, upload media, validate a schedule, and publish across every connected platform, all through one hosted workspace and plain REST calls.

Start free Open API reference

curl -sS https://getsocialclaw.com/v1/posts/apply \
  -H "Authorization: Bearer $SOCIALCLAW_API_KEY" \
  -H "Content-Type: application/json" \
  -X POST \
  --data '{
    "timezone": "America/New_York",
    "posts": [
      { "account": "meta:instagram:17841400000000000", "description": "Launch day.", "publish_at": "2026-07-21T09:00:00-04:00" },
      { "account": "linkedin:person:123", "description": "Here is what changed and why.", "publish_at": "2026-07-21T09:05:00-04:00" }
    ]
  }'

const response = await fetch("https://getsocialclaw.com/v1/posts/apply", {
  method: "POST",
  headers: {
    "Authorization": "Bearer " + process.env.SOCIALCLAW_API_KEY,
    "Content-Type": "application/json"
  },
  body: JSON.stringify({
    timezone: "America/New_York",
    posts: [
      { account: "meta:instagram:17841400000000000", description: "Launch day.", publish_at: "2026-07-21T09:00:00-04:00" },
      { account: "linkedin:person:123", description: "Here is what changed and why.", publish_at: "2026-07-21T09:05:00-04:00" }
    ]
  })
});

201 Created

{
  "run": { "id": "run_7k2md9pz", "mode": "scheduled" },
  "posts": [
    { "id": "post_3n0qd1h", "provider": "instagram", "status": "scheduled" },
    { "id": "post_9h4wq2c", "provider": "linkedin", "status": "scheduled" }
  ]
}

One workspace, every platform

Connection, media, validation, and inspection all live behind the same workspace API key, whichever platform a post targets.

Connect once, reuse through API calls

OAuth and manual connections live inside the workspace, so scripts and agents never need to own provider credentials.

One schedule shape

Every post declares an account, content, media, timezone, and publish time, the same shape across every connected provider.

Validate before you apply

Validation catches account, media, setting, and provider-envelope problems before anything is scheduled.

Inspect what actually happened

Runs, posts, attempts, and account health are all queryable after apply, so you are never just trusting a 200 response.

Every call your backend
needs, in one workspace

Validate a schedule, apply it, and check delivery status, all with the same workspace key. Upload media once and reuse the link across every scheduled post.

GET /v1/accounts List connected accounts and which ones are ready to publish.

POST /v1/assets/upload Upload a photo or video and get back a link to reuse.

POST /v1/posts/validate Check a schedule against each provider's rules before anything goes out.

POST /v1/posts/apply Publish now or queue posts for a future time.

GET /v1/runs/{runId}/status Confirm a post actually went live, or catch a failure early.

Open the full API reference

Built for validation-first workflows

Every step in the publish path is checkable before it commits, so a bad request never becomes a bad post.

Validate before you apply

Run the exact schedule through /v1/posts/validate first. A batch either passes together or fails loudly, before anything is scheduled.

Terminal

curl -sS -X POST \
  -H "Authorization: Bearer $SOCIALCLAW_API_KEY" \
  -H "Content-Type: application/json" \
  --data @schedule.json \
  https://getsocialclaw.com/v1/posts/validate
{"valid":true,"posts":12}

Retry safely with an idempotency key

Add idempotencyKey to a request and a repeated call returns the original run instead of creating a second one, so retries on your end are always safe.

schedule.json

{
  "idempotencyKey": "launch_calendar_1",
  "timezone": "America/New_York",
  "posts": […]
}

Confirm delivery after publish

Poll run status once a schedule applies to see exactly what published, what is pending, and what needs a retry.

Terminal

curl -sS \
  -H "Authorization: Bearer $SOCIALCLAW_API_KEY" \
  https://getsocialclaw.com/v1/runs/run_7k2md9pz/status
{"run":{"id":"run_7k2md9pz"},"posts":[{"status":"published"}]}

Built for AI Agents
Too

Simply install the skill with this command

Call the API from Claude

Call the API from Codex

Call the API from OpenClaw

Call the API from Hermes

Ready to grow
your socials?

Start free

Every other way in

Same workspace, same connected accounts, on whichever surface fits what you are building.

Use the dashboard

Schedule and manage posts visually. No code required.

Use with CLI

Validate and apply schedules from a terminal, cron job, or CI.

Use with MCP

Connect Claude, ChatGPT, or Cursor and let the agent publish for you.

What builders are saying

Real quotes from Reddit, G2, Trustpilot, and Instagram.

G2 G2 review

“I can prepare the content once and let SocialClaw handle the distribution.”

Instagram

“If SocialClaw sees this just know you changed my entire workflow girl.”

r/mcp

“Since I try market my iOS apps, definitely SocialClaw… because then Claude can post to social media for me.”

r/socialmedia

“Most schedulers still feel like old calendar tools with an AI caption button added on top. SocialClaw feels more built around the newer AI era.”

r/automation

“SocialClaw if you want to schedule posts to social media.”

G2 G2 review

“I can prepare the content once and let SocialClaw handle the distribution.”

Instagram

“If SocialClaw sees this just know you changed my entire workflow girl.”

r/mcp

“Since I try market my iOS apps, definitely SocialClaw… because then Claude can post to social media for me.”

r/socialmedia

“Most schedulers still feel like old calendar tools with an AI caption button added on top. SocialClaw feels more built around the newer AI era.”

r/automation

“SocialClaw if you want to schedule posts to social media.”

Trustpilot Trustpilot review

“SocialClaw handles the repetitive publishing work: uploading media, managing connected accounts, scheduling posts, publishing them, and retrying when something fails.”

r/SocialMediaManagers

“I used to use stuff like Buffer etc, but I use SocialClaw with my AI agent. I just tell it to schedule like 100 videos for the next month.”

r/AI_Agents

“It has an OpenClaw skill, or use it via API, CLI, or even the web dashboard.”

r/openclaw

“I have it install the SocialClaw skill, linked my social media accounts, and it actually has approval to post on my socials for me.”

Trustpilot Trustpilot review

“SocialClaw handles the repetitive publishing work: uploading media, managing connected accounts, scheduling posts, publishing them, and retrying when something fails.”

r/SocialMediaManagers

“I used to use stuff like Buffer etc, but I use SocialClaw with my AI agent. I just tell it to schedule like 100 videos for the next month.”

r/AI_Agents

“It has an OpenClaw skill, or use it via API, CLI, or even the web dashboard.”

r/openclaw

“I have it install the SocialClaw skill, linked my social media accounts, and it actually has approval to post on my socials for me.”

Works with every major platform

Connect once, then schedule and publish everywhere from the same workspace.

Frequently Asked Questions

How do I authenticate requests to the API?

Every request needs an Authorization header in the form Bearer sc_live_your_key, using the workspace API key from your dashboard. The same key covers every connected account and platform, so there is no separate key per provider.

Can I check a schedule before it goes out?

How do I avoid publishing the same post twice?

Do I need to host my own images and video?

Does every platform accept the same payload?

How do I know a post actually published?

Where is the full API reference?