LinkedIn Profile publishing API with one SocialClaw workspace.
Start the hosted LinkedIn OAuth flow from SocialClaw and keep the connected member profile inside the same workspace used by the CLI and API. SocialClaw publishes LinkedIn member profile posts with text, native image upload, or native video upload.
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.
- LinkedIn member profile stored in the SocialClaw workspace
- LinkedIn member profiles support one video or up to twenty images per post.
- Capability or publish-preview checks before apply
- 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 LinkedIn Profile
Start the hosted LinkedIn OAuth flow from SocialClaw and keep the connected member profile inside the same workspace used by the CLI and API.
Inspect account capabilities and settings
Use capabilities and publish-preview to confirm the publish envelope before applying a schedule.
Validate before apply
Validation should happen before create-run or apply. LinkedIn member profiles support one video or up to twenty images per post.
Inspect the resulting run or post
Reconciliation currently supports LinkedIn post lookup. Analytics snapshots are available, but LinkedIn provider-native analytics fetchers are not implemented yet.
CLI and HTTP examples
Example commands and requests for this route.
socialclaw login --api-key <workspace-key> --base-url https://getsocialclaw.com
socialclaw accounts connect --provider linkedin --open
socialclaw accounts capabilities --provider linkedin --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":"linkedin"}' \
"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.
- Non-post interaction steps are not implemented.
- One video cannot be combined with image assets in the same post.
- LinkedIn profile and LinkedIn page targets use separate routes and separate target handles.
Related routes
Related integrations and use cases.
Frequently asked questions
What account type does the LinkedIn Profile publishing API route use?
LinkedIn Profile uses the LinkedIn member profile route in SocialClaw. Start the hosted LinkedIn OAuth flow from SocialClaw and keep the connected member profile inside the same workspace used by the CLI and API.
What media rules apply to the LinkedIn Profile publishing API route?
LinkedIn member profiles support one video or up to twenty images per post. SocialClaw uploads LinkedIn media natively before publish.
What should the workflow inspect before applying LinkedIn Profile posts?
Inspect capabilities or publish-preview before apply. Non-post interaction steps are not implemented.
Connect the account once, validate before publish, and keep everything in one workspace.