SocialClaw
GitHub Dashboard
Developer tools

Use the CLI and HTTP API as one hosted publishing surface for developer workflows.

SocialClaw fits developer tools that want a clean CLI, a hosted API, workspace API keys, provider-aware validation, and inspectable runs, posts, analytics, jobs, and health.

Start free View pricing
Best for Developer tools Use the SocialClaw CLI and HTTP API to connect accounts, validate schedules, apply runs, and inspect publish state in developer workflows.
Includes Dashboard, CLI, and API The CLI is a client for the hosted SocialClaw service, not a standalone scheduler.

Why this workflow fits SocialClaw

One workspace, one connection hub, and one publishing layer.

CLI client Install and log in fast The socialclaw CLI stores the workspace API key locally and talks to the hosted service at getsocialclaw.com by default.
Hosted API HTTP endpoints mirror the CLI Account connection, media upload, validation, apply, post inspection, and run inspection are available over the hosted HTTP API.
Safe iteration Validate and preview before apply Developer workflows can validate schedules and preview campaigns before any run becomes live work.
Operational detail Inspect posts, attempts, and runs The product exposes post details, attempt history, run inspection, retries, cancel, and reconciliation where supported.
Health surfaces Analytics, usage, jobs, and health Developer workflows can read analytics snapshots, usage, connection health, workspace health, and job state from the same workspace.

How the workflow runs

Connect accounts, upload media, validate posts, then publish.

Step 1

Install the CLI or use raw HTTP

Developer tools can use the socialclaw CLI for short commands or call the hosted API directly with the same workspace key.

Step 2

Authenticate with the workspace key

Log into the CLI with the workspace API key, or pass the key in the Authorization header for hosted HTTP requests.

Step 3

Inspect connected accounts before generating payloads

Read capabilities, settings, and account actions before the tool emits a provider-specific schedule.

Step 4

Upload media when the provider expects public URLs

Use SocialClaw-hosted media URLs instead of temporary third-party links so the workflow keeps a stable delivery handoff.

Step 5

Validate or preview the payload

Validation and campaign preview should happen before apply, especially when the route includes media rules or provider-specific settings.

Step 6

Inspect results and recover cleanly

Use post attempts, run inspection, analytics, jobs, and health to drive debugging and recovery flows after publish.

CLI and HTTP examples

Example commands and requests for this setup.

CLI flow Developer tools example 
npm install -g socialclaw
socialclaw login --api-key <workspace-key>
socialclaw accounts capabilities --account-id <account-id> --json
socialclaw campaigns preview -f schedule.json --json
socialclaw apply -f schedule.json --idempotency-key dev_tool_1 --json
socialclaw workspace health --json
HTTP API flow Hosted SocialClaw endpoints 
curl -sS \
  -H "Authorization: Bearer $SC_API_KEY" \
  "https://getsocialclaw.com/v1/accounts"

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

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

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

Relevant provider coverage

Integrations that usually fit this setup best.

YouTube YouTube channel

Use SocialClaw to connect YouTube channels, upload video assets natively, validate settings, and inspect publish runs from the same workspace used by the dashboard, API, CLI, and agents.

OAuth YouTube requires one video per post.
Open integration
WordPress WordPress.com or Jetpack-connected site

SocialClaw keeps WordPress site connection, remote media upload, publish settings, validation, and post inspection in one hosted workspace shared by the dashboard, API, CLI, and agent workflows.

OAuth WordPress supports up to twenty remote media assets per post or page.
Open integration
LinkedIn Profile LinkedIn member profile

Use SocialClaw to keep LinkedIn profile connection, native media upload, schedule validation, and post inspection in one workspace shared by the dashboard, API, CLI, and agent workflows.

OAuth LinkedIn member profiles support one video or up to twenty images per post.
Open integration
X X user account

Use SocialClaw to connect X once, then validate, schedule, publish, and inspect text posts, media posts, and reply-based campaign steps from the same hosted workspace.

OAuth X supports up to four images or one video per post.
Open integration

Related workflows

More routes that fit the same setup.

Audience workflow
YouTube scheduler for dev tools Use SocialClaw as a YouTube scheduler for developer tools with hosted API access, CLI support, native upload, and run inspection.
Publishing API
YouTube publishing API Use the SocialClaw workspace API and CLI to connect YouTube, validate schedules, upload media when needed, and inspect publish state.
Publishing API
WordPress publishing API Use the SocialClaw workspace API and CLI to connect WordPress, validate schedules, upload media when needed, and inspect publish state.

Operator notes and limits

A few practical limits to keep in mind.

  • The CLI is a client for the hosted SocialClaw service, not a standalone scheduler.
  • Provider-native analytics coverage is still partial, so analytics snapshots and unsupported states must be handled explicitly.
  • Provider-specific media and interaction limits still apply to every route.

Frequently asked questions

Does the CLI replace the SocialClaw backend?

No. The CLI is a shorter client for the hosted service. It does not replace the backend or remove the need for a workspace API key.

How should a developer workflow inspect failures?

Use posts get, posts attempts, runs inspect, jobs list, and workspace or connection health to inspect the canonical lifecycle record and next action.

Can developer tools use only HTTP instead of the CLI?

Yes. The hosted HTTP API exposes the same core operations for account connection, media upload, validation, apply, and inspection.

Start with the Developer tools workflow

Create the workspace, connect accounts once, and keep validation plus delivery state inside the same hosted product.

Start free View pricing