canonical: https://jentic.com/apis/getsocialclaw.com/getsocialclaw # Getsocialclaw SocialClaw API The SocialClaw API connects social accounts, schedules posts, and publishes them across those accounts while tracking every delivery attempt. It covers media asset upload and import, campaign previews, and draft runs you publish on demand, with reconcile and retry paths for posts whose provider status drifts. Per-post, per-account, and per-run analytics, signed media delivery URLs, and inbound webhooks round out the publishing pipeline for connected social profiles. ## For AI agents Connect social accounts, schedule and publish posts, upload media, and pull post, account, and run analytics across connected social profiles. ## Scope Does not handle ad campaign buying, audience targeting, or direct messaging. Use for scheduling and publishing posts to connected social accounts only. ## Capabilities - Connect social accounts through a guided connection flow and list each account's publishing capabilities - Schedule and publish posts to connected accounts, then track every delivery attempt - Publish draft runs on demand and reconcile posts whose provider status has drifted - Upload, import, and register media assets for use in posts - Retrieve post, account, and run analytics and refresh post metrics on demand - Preview a campaign and validate a schedule before anything is published ## Use cases ### Agent-Driven Social Publishing An AI agent connects a social account, uploads the media, schedules a post, and publishes it without a human wiring each provider by hand. The agent starts a connection, registers an asset, applies a run, and then publishes that run, checking the delivery attempts afterward to confirm the post went live. Jentic exposes each SocialClaw operation with its input schema so the agent fills the right fields on the first call. Example prompt: Connect an Instagram account, upload a video asset, create a run scheduled for Friday at 09:00, publish it, and confirm the delivery attempt succeeded ### Scheduled Content Calendar A content team queues a week of posts across several connected accounts and lets the schedule drive publishing. The SocialClaw API validates each schedule, previews the campaign, and publishes draft runs at the planned time, exposing run status and a run table so the calendar stays accurate. Posts that fail at the provider can be retried or reconciled rather than silently lost. Example prompt: List posts scheduled for the next seven days, then preview the campaign for a run before it publishes ### Post-Performance Reporting A growth team pulls engagement numbers for published posts and rolls them up by account and by run. The SocialClaw API serves post analytics, account analytics, and run analytics, and can refresh post metrics on demand so a report reflects the latest provider figures. The result is a single reporting flow over every connected profile. Example prompt: Refresh analytics for a published post, then retrieve the account analytics for the owning profile ### Media Asset Pipeline An app lets users drop in images and video that later attach to scheduled posts. The SocialClaw API registers an asset, uploads it directly or imports it from a URL, and serves it back through signed delivery URLs, with multipart upload steps available for larger files. Assets can be listed and deleted so the library stays tidy. Example prompt: Register an asset, import its source from a URL, and confirm it appears in the asset list ## Key endpoints | Method | Path | Description | | --- | --- | --- | | POST | `/v1/connections/start` | Start a connection to a social account | | GET | `/v1/accounts` | List connected accounts | | POST | `/v1/posts/apply` | Create a run from a post plan | | POST | `/v1/runs/{runId}/publish` | Publish a draft run | | GET | `/v1/posts` | List posts | | POST | `/v1/assets/upload` | Upload a media asset | | GET | `/v1/analytics/posts/{postId}` | Read analytics for one post | ## Key resources - **Connections and Accounts** — Start account connections, check connection health, list connected accounts, and read per-account capabilities and publish settings - **Posts and Runs** — Create runs, publish drafts, list and inspect posts, retry or reconcile delivery, and read run status and campaign graphs - **Assets** — Register, upload, import, list, and delete media assets, including multipart upload for larger files - **Analytics** — Read post, account, and run analytics and refresh post metrics on demand - **Webhooks** — Receive signed billing, App Store, and Meta webhook notifications ## AI readiness This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use. - **Score:** 60 / 100 - **Maturity:** Foundational - **Dimensions:** - Foundational Compliance: 57 / 100 - Developer Experience & Jentic Compatibility: 62 / 100 - AI-Readiness & Agent Experience: 48 / 100 - Agent Usability: 87 / 100 - Security: 53 / 100 - AI Discoverability: 66 / 100 - **View full report:** https://jentic.com/apis/getsocialclaw.com/getsocialclaw/scorecard - **How the score is calculated:** https://docs.jentic.com/reference/api-readiness-framework/overview/ - **More about the dimensions:** https://docs.jentic.com/reference/api-readiness-framework/specification/#dimensional-model-overview ### Score it yourself Every API in the directory is allowlisted, so you can re-score it with no key required. - **Score your own API:** https://jentic.com/scorecard.md - **Scoring CLI agent skill:** https://github.com/jentic/jentic-api-scorecard/blob/main/skills/jentic-api-scorecard/SKILL.md ```sh npx @jentic/api-scorecard-cli score ``` ## Why Jentic - **Setup:** Wiring the SocialClaw API by hand means managing its bearer token, the per-provider connection flow for each social account, and the asset upload and post-reconcile steps yourself. Through Jentic you install once, import SocialClaw from the API Directory, store the token once, and your agent calls it. - **Permission scoping:** SocialClaw puts the account id in the URL path (`/v1/accounts/{accountId}/...`), so a rule can pin your agent to one connected account and the operations you pick, such as listing posts and publishing. You choose the operations it may call, so destructive ones like disconnecting an account or deleting an asset are not included unless you add them. - **Credential handling:** Your SocialClaw token is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context. - **Discovery method:** Agents search Jentic by intent such as 'schedule a post' or 'check post analytics', and Jentic returns the matching SocialClaw operation with its input schema so the agent calls the right endpoint without reading the reference docs. ## Related APIs - **Buffer** — Buffer schedules and publishes posts across social networks with a simpler, established surface. - **ContentStudio** — ContentStudio covers content discovery alongside social scheduling and publishing. - **RiteKit** — RiteKit adds hashtag suggestions and image enhancement to posts before they are published. ## FAQ ### What authentication does the SocialClaw API use? The SocialClaw API authenticates programmatic calls with a bearer token in the Authorization header per its OpenAPI spec. Dashboard-session calls instead use a socialclaw_dash_session cookie, and inbound webhooks are verified with an x-signature header. Public endpoints like health checks, media delivery, and OAuth callbacks need no credential. Through Jentic the bearer token is stored encrypted by your own Jentic One instance and injected at call time. ### Can I schedule and publish posts with the SocialClaw API? Yes. You apply a run from a post plan, publish that draft run when you are ready, and the API tracks each delivery attempt per connected account. If a provider rejects a post you can retry it or reconcile its status, and validate a schedule before anything goes out. ### What are the rate limits for the SocialClaw API? The SocialClaw OpenAPI spec does not publish fixed rate limits. The workspace usage endpoint reports your current usage, so your agent can read consumption before sending more requests rather than guessing a ceiling. ### Is there a SocialClaw MCP server? You do not need an MCP server to give your agent the SocialClaw API. Jentic connects it directly from the API Directory: import it, store your token once, and your agent calls its operations. Operations are discovered on demand, so your agent's context stays lean instead of loading a full tool list up front. ### Can I limit what my agent is allowed to do with the SocialClaw API? Yes. Write a rule that allows only the read and publish operations under one connected account id, so the agent can list posts, schedule, and publish for that account and touch nothing else, and every call it makes is logged. Account-disconnect and asset-delete operations stay out of the allowed set unless you add them. ### How do I publish a scheduled post with the SocialClaw API through Jentic? Search Jentic for 'schedule and publish a social media post', and it returns the SocialClaw run and publish operations with their input schemas. Your agent applies a run, publishes it, and reads the delivery attempts to confirm the post is live. To run it on your own infrastructure, install Jentic One from its GitHub repo.