Publishing API
WordPress publishing API with one SocialClaw workspace.
Connect the WordPress.com or Jetpack-connected site through the hosted SocialClaw OAuth flow, then reuse the site target from the same workspace. SocialClaw publishes WordPress posts or pages through one explicit WordPress provider.
What SocialClaw supports for this workflow
A quick overview of what this workflow supports.
What the payload needs
The main fields and constraints to account for.
- WordPress.com or Jetpack-connected site stored in the SocialClaw workspace
- WordPress supports up to twenty remote media assets per post or page.
- Provider-specific settings such as postStatus, postType, slug
- Workspace API key auth and post or run inspection after apply
How the workflow runs
Connect the account, validate the post, then publish.
Authenticate the workspace
Use the workspace API key with the CLI or hosted HTTP API so the publishing workflow stays attached to the same customer workspace.
Connect WordPress
Connect the WordPress.com or Jetpack-connected site through the hosted SocialClaw OAuth flow, then reuse the site target from the same workspace.
Inspect account capabilities and settings
Read the current settings surface, including postStatus, postType, slug, before generating the final payload.
Validate before apply
Validation should happen before create-run or apply. WordPress supports up to twenty remote media assets per post or page.
Inspect the resulting run or post
Reconciliation currently supports WordPress post lookup. Analytics snapshots are available, but WordPress provider-native analytics fetchers are not implemented yet.
CLI and HTTP examples
Example commands and requests for this route.
CLI flow
WordPress publishing API
socialclaw login --api-key <workspace-key> --base-url https://getsocialclaw.com
socialclaw accounts connect --provider wordpress --open
socialclaw accounts capabilities --provider wordpress --json
socialclaw validate -f schedule.json --json
socialclaw apply -f schedule.json --idempotency-key launch_1 --json
socialclaw runs inspect --run-id <run-id> --json
HTTP API flow
Hosted SocialClaw endpoints
curl -sS \
-H "Authorization: Bearer $SC_API_KEY" \
"https://getsocialclaw.com/v1/keys/validate"
curl -sS \
-X POST \
-H "Authorization: Bearer $SC_API_KEY" \
-H "Content-Type: application/json" \
-d '{"provider":"wordpress"}' \
"https://getsocialclaw.com/v1/connections/start"
curl -sS \
-X POST \
-H "Authorization: Bearer $SC_API_KEY" \
-H "Content-Type: application/json" \
-d @schedule.json \
"https://getsocialclaw.com/v1/posts/validate"
curl -sS \
-X POST \
-H "Authorization: Bearer $SC_API_KEY" \
-H "Content-Type: application/json" \
-d @schedule.json \
"https://getsocialclaw.com/v1/posts/apply"Current limitations
A few practical limits to keep in mind.
- WordPress taxonomy, category, tag, and richer block-editor controls are still thin.
- WordPress media URLs must resolve to supported image or video types.
- Publish interactions currently support only post steps.
Related routes
Related integrations and use cases.
Frequently asked questions
What account type does the WordPress publishing API route use?
WordPress uses the WordPress.com or Jetpack-connected site route in SocialClaw. Connect the WordPress.com or Jetpack-connected site through the hosted SocialClaw OAuth flow, then reuse the site target from the same workspace.
What media rules apply to the WordPress publishing API route?
WordPress supports up to twenty remote media assets per post or page. SocialClaw uploads remote media into WordPress and embeds it into the published content.
What should the workflow inspect before applying WordPress posts?
Inspect settings such as postStatus, postType, slug and capabilities. WordPress taxonomy, category, tag, and richer block-editor controls are still thin.
Run the WordPress publishing API workflow in SocialClaw
Connect the account once, validate before publish, and keep everything in one workspace.