Publishing API
Facebook Pages publishing API with one SocialClaw workspace.
Start the Facebook OAuth flow from SocialClaw, complete consent in the browser, and SocialClaw stores the publishable Page targets in the workspace. SocialClaw publishes to Facebook Pages through the explicit Facebook 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.
- Facebook Page stored in the SocialClaw workspace
- Facebook Pages support feed posts plus one effective image or video per post.
- Provider-specific settings such as pagePostMode
- 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 Facebook Pages
Start the Facebook OAuth flow from SocialClaw, complete consent in the browser, and SocialClaw stores the publishable Page targets in the workspace.
Inspect account capabilities and settings
Read the current settings surface, including pagePostMode, before generating the final payload.
Validate before apply
Validation should happen before create-run or apply. Facebook Pages support feed posts plus one effective image or video per post.
Inspect the resulting run or post
Reconciliation for explicit Facebook Page publishes is not implemented yet. Analytics snapshots are available, but Facebook provider-native analytics fetchers are not implemented yet.
CLI and HTTP examples
Example commands and requests for this route.
CLI flow
Facebook Pages publishing API
socialclaw login --api-key <workspace-key> --base-url https://getsocialclaw.com
socialclaw accounts connect --provider facebook --open
socialclaw accounts capabilities --provider facebook --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":"facebook"}' \
"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.
- Personal Facebook profiles are not publish targets.
- Facebook currently supports one effective image or video per post.
- Publish interactions currently support only post steps.
Related routes
Related integrations and use cases.
Frequently asked questions
What account type does the Facebook Pages publishing API route use?
Facebook Pages uses the Facebook Page route in SocialClaw. Start the Facebook OAuth flow from SocialClaw, complete consent in the browser, and SocialClaw stores the publishable Page targets in the workspace.
What media rules apply to the Facebook Pages publishing API route?
Facebook Pages support feed posts plus one effective image or video per post. The provider pulls a public media URL, including SocialClaw-hosted media URLs.
What should the workflow inspect before applying Facebook Pages posts?
Inspect settings such as pagePostMode and capabilities. Personal Facebook profiles are not publish targets.
Run the Facebook Pages publishing API workflow in SocialClaw
Connect the account once, validate before publish, and keep everything in one workspace.