Posting API

Social media posting API with connection, media, and inspection built in.

A thin post endpoint is rarely enough. SocialClaw packages the full posting flow: connected-account ownership, media handoff, provider-aware validation, publish execution, and the ability to inspect what happened afterward.

Start free View pricing

What you get

The operational pieces that matter before a workflow promises social publishing.

Connection layer Hosted OAuth and manual targets Customers connect publishable accounts once, then the API reuses those targets across later posts and schedules.

Media layer Hosted URLs or native upload by route SocialClaw handles media according to the provider route: public URL handoff, native upload, or webhook upload.

Publish layer Validate before publish execution Validation checks platform-specific requirements before the work is applied.

Inspection layer Post records and attempts The workspace keeps publish state and attempts so your product can show meaningful delivery status.

Inputs and requirements

The data and checks that keep the workflow grounded in current provider rules.

A connected account target stored in the workspace
Text content and provider-supported media
Optional provider settings such as Instagram publish mode, TikTok privacy level, or YouTube privacy status where supported
A validation call before creating publish work
Post or run inspection after apply

How it works

A provider-aware flow from connection to inspection.

Step 1

Start from a workspace target

Use an account already connected through SocialClaw instead of sending raw provider credentials with each post.

Step 2

Build the provider-specific post

Use the account type and media envelope that matches the selected route.

Step 3

Validate the payload

Check text, media, settings, and account constraints before asking SocialClaw to apply the post.

Step 4

Apply the work

Create the publish work through the hosted API or CLI.

Step 5

Inspect the outcome

Read post detail, attempts, and account health so your product can show what happened.

CLI and HTTP examples

Representative commands and requests for this workflow.

CLI flow Social media posting API

socialclaw login --api-key <workspace-key>
socialclaw accounts list --json
socialclaw accounts capabilities --provider linkedin --json
socialclaw validate -f post.json --json
socialclaw apply -f post.json --idempotency-key product_post_1 --json
socialclaw posts get --post-id <post-id> --json

HTTP API flow Hosted SocialClaw endpoints

curl -sS \
  -X POST \
  -H "Authorization: Bearer $SC_API_KEY" \
  -H "Content-Type: application/json" \
  -d @post.json \
  "https://getsocialclaw.com/v1/posts/validate"

curl -sS \
  -X POST \
  -H "Authorization: Bearer $SC_API_KEY" \
  -H "Content-Type: application/json" \
  -d @post.json \
  "https://getsocialclaw.com/v1/posts/apply"

curl -sS \
  -H "Authorization: Bearer $SC_API_KEY" \
  "https://getsocialclaw.com/v1/posts/<post-id>"

Constraints to know

Important guardrails to keep the page accurate.

Personal Facebook profiles are not publish targets.
Instagram routes require media and do not currently advertise stories, carousels, or text-only Instagram posts.
Interaction publishing is provider-specific rather than universal.

Related routes

Pages that reinforce the same product and platform intent.

Product

Scheduling API Add publish_at and schedule whole campaigns

Use case

Embedded SaaS use case Customer account connection and publish execution inside your product

Hub

Workflow pages Provider-specific examples and constraints

Hub

Integrations Account types, media rules, and settings

Compare

SocialClaw vs Postiz Hosted execution compared with agentic scheduler alternatives

Product

Pricing Plans for hosted posting workflows

Frequently asked questions

What is included in SocialClaw's posting API?

The posting API flow includes workspace auth, connected account reuse, media handling, provider-aware validation, apply, and post inspection.

Can one API post to every provider with exactly the same media rules?

No. SocialClaw keeps platform rules visible because Instagram, LinkedIn, YouTube, TikTok, X, and manual targets each have different account and media constraints.

Is SocialClaw only for scheduled posts?

SocialClaw is built around publish execution with validation and inspection. Scheduling is the main workflow surface, and posting pages should still model provider constraints and apply state clearly.

Use SocialClaw for Social media posting API

Connect accounts once, validate provider-specific payloads, schedule or apply work, and inspect the result from one hosted workspace.

Start free Browse workflows