X uses the X user account route in SocialClaw. Start the hosted X OAuth flow from the dashboard or CLI, finish consent in the browser, then reuse the connected X account through the SocialClaw workspace API key.
Start the hosted X OAuth flow from the dashboard or CLI, finish consent in the browser, then reuse the connected X account through the SocialClaw workspace API key. SocialClaw supports X text posts, media posts, and reply steps inside campaign flows.
Works with Claude, ChatGPT, OpenClaw
![]()
![]()
A quick overview of what this workflow supports.
The main fields and constraints to account for.
Connect the account, validate the post, then publish.
Use the workspace API key with the CLI or hosted HTTP API so the publishing workflow stays attached to the same customer workspace.
Start the hosted X OAuth flow from the dashboard or CLI, finish consent in the browser, then reuse the connected X account through the SocialClaw workspace API key.
Read the current settings surface, including replyControl, before generating the final payload.
Validation should happen before create-run or apply. X supports up to four images or one video per post.
Reconciliation currently supports X post lookup. Analytics snapshots are available, and provider-native analytics fetchers are still expanding.
Example commands and requests for this route.
socialclaw login --api-key <workspace-key> --base-url https://getsocialclaw.com
socialclaw accounts connect --provider x --open
socialclaw accounts capabilities --provider x --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
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":"x"}' \
"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"
A few practical limits to keep in mind.
Related integrations and use cases.
Real quotes from Reddit, G2, Trustpilot, and Instagram.
“I can prepare the content once and let SocialClaw handle the distribution.”
“If SocialClaw sees this just know you changed my entire workflow girl.”
“Since I try market my iOS apps, definitely SocialClaw… because then Claude can post to social media for me.”
“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.”
“SocialClaw if you want to schedule posts to social media.”
“SocialClaw handles the repetitive publishing work: uploading media, managing connected accounts, scheduling posts, publishing them, and retrying when something fails.”
“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.”
“It has an OpenClaw skill, or use it via API, CLI, or even the web dashboard.”
“I have it install the SocialClaw skill, linked my social media accounts, and it actually has approval to post on my socials for me.”
Connect once, then schedule and publish everywhere from the same workspace.
X uses the X user account route in SocialClaw. Start the hosted X OAuth flow from the dashboard or CLI, finish consent in the browser, then reuse the connected X account through the SocialClaw workspace API key.
X supports up to four images or one video per post. SocialClaw uploads the media to X during publish.
Inspect settings such as replyControl and capabilities. X supports one video or up to four images per post, not both together.
Connect the account once, validate before publish, and keep everything in one workspace.