canonical: https://jentic.com/apis/dunsocial.com/dunsocial # DunSocial API The DunSocial API schedules and publishes social posts across connected accounts and manages the drafts, media, and workspace personalization behind them. It schedules single posts and X threads, publishes immediately, validates a post with a dry run before it goes out, and reschedules, cancels, or deletes queued posts. Alongside publishing it manages a media gallery with presigned uploads, draft content, memory collections for personalization, and per-account options such as Reddit flair, Pinterest boards, and Slack or Discord channels. ## For AI agents Schedule, validate, and publish social posts and threads across connected accounts, manage drafts and media, and read per-platform posting options. ## Scope Does not run paid ad campaigns, read social analytics dashboards, or manage direct messages. Use for scheduling and publishing social posts and their drafts and media only. ## Capabilities - Schedule posts and X threads or queue them for immediate publishing across connected accounts - Validate a post with a dry run before scheduling or publishing it - Reschedule, cancel, or delete scheduled posts - Manage drafts and a media gallery with presigned uploads - List connected social accounts and read per-platform options like Reddit flair and Pinterest boards - Store, search, and manage memory collections for workspace personalization - Read and update a workspace's AI voice and personalization settings ## Use cases ### Agent-driven post scheduling An AI agent connected through Jentic drafts a post, runs the validate dry run to catch per-platform problems, then schedules it across the connected accounts, all without a human opening the DunSocial app. The validate step returns the checks for each target so the agent can fix a post before it is queued rather than after it fails. Example prompt: Validate a post for the connected accounts, and if it passes, schedule it for a given time ### Thread publishing Teams publish multi-tweet X threads by scheduling or immediately queuing a thread of two to twenty-five tweets through DunSocial. The API exposes dedicated schedule-thread and publish-thread endpoints plus the X monthly posting-cap usage, so an agent can check headroom before posting. Example prompt: Check the X monthly posting-cap usage, then schedule a thread of five tweets if there is headroom ### Draft and media management Content workflows keep a library of drafts and media in DunSocial, creating and updating drafts and uploading images through presigned URLs that are confirmed into the gallery. An agent can assemble a post from stored drafts and media rather than regenerating assets each time. Example prompt: Create a draft, request a presigned upload URL for an image, and confirm the upload into the gallery ### Per-platform posting options Before posting to platforms with their own rules, teams read the live requirements, such as Reddit flair templates and post rules for a subreddit, or the boards on a connected Pinterest account. DunSocial exposes these option endpoints so an agent builds a valid post for each platform rather than guessing its constraints. Example prompt: List the Reddit flair templates and post requirements for a subreddit before scheduling a Reddit post ## Key endpoints | Method | Path | Description | | --- | --- | --- | | POST | `/api/posts/schedule` | Schedule a post | | POST | `/api/posts/publish-now` | Queue a post for immediate publish | | POST | `/api/posts/validate` | Dry-run schedule and publish checks | | GET | `/api/posts` | List posts | | POST | `/api/drafts` | Create a draft | | GET | `/api/social-accounts` | List connected social accounts | | POST | `/api/media/upload-url` | Get a presigned media upload URL | ## Key resources - **Posts** — List, schedule, publish, validate, reschedule, cancel, and delete posts and threads - **Drafts** — Create, read, update, and delete draft posts - **Media** — List media and upload via presigned URLs confirmed into the gallery - **Social accounts** — List connected accounts and read per-platform options like flair, boards, and channels - **Memory** — Manage and search memory collections that drive workspace personalization - **Workspaces** — List workspaces and read or update AI voice and personalization settings ## 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: 85 / 100 - Developer Experience & Jentic Compatibility: 62 / 100 - AI-Readiness & Agent Experience: 40 / 100 - Agent Usability: 94 / 100 - Security: 60 / 100 - AI Discoverability: 57 / 100 - **View full report:** https://jentic.com/apis/dunsocial.com/dunsocial/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 DunSocial by hand means handling its Bearer auth, adding the X-Workspace-Id header on workspace routes, and running the validate dry run and presigned media upload flow yourself. Through Jentic you install once, import DunSocial from the API Directory, store the token once, and your agent calls it. - **Permission scoping:** DunSocial carries post, draft, and media ids in the URL path, so a rule can pin your agent to the operations you pick, such as validating and scheduling posts. You choose the operations it may call, so destructive ones like deleting a post or publishing immediately are not included unless you add them. - **Credential handling:** Your DunSocial 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 social post' or 'validate a post', and Jentic returns the matching DunSocial operation with its input schema so the agent calls the right endpoint without browsing the reference docs. ## Related APIs - **Buffer** — Social scheduling across multiple networks, an alternative publishing surface to DunSocial. - **X (Twitter) API** — Direct access to the X platform that DunSocial posts to, for reads DunSocial does not cover. - **LinkedIn** — Direct LinkedIn access for profile and page actions beyond DunSocial's publishing. ## FAQ ### What authentication does the DunSocial API use? The DunSocial API authenticates with a Bearer token, a session or personal access token, in the Authorization header per its OpenAPI spec. Workspace-scoped routes additionally require an X-Workspace-Id header. Through Jentic the token is stored once and injected at call time so it never enters the agent's prompt. ### Can I schedule a post across multiple accounts with the DunSocial API? Yes. You can schedule a single post or an X thread, publish immediately, and run a validate dry run first to catch per-platform problems. Scheduled posts can then be rescheduled, cancelled, or deleted through their own endpoints. ### What are the rate limits for the DunSocial API? The OpenAPI spec does not publish fixed rate limits, though it does expose X monthly posting-cap usage so you can track that platform's limit. Check the DunSocial documentation for the per-account limits that apply to your plan. ### Is there a DunSocial API MCP server? You don't need an MCP server to give your agent the DunSocial API. Jentic connects it directly from the API Directory: import it, store your token once, and your agent schedules and publishes posts on demand without loading another server's tool definitions into its context. ### Can I limit what my agent is allowed to do with the DunSocial API? Yes. Write a rule that allows only the validate and schedule operations, so the agent can queue posts but cannot publish immediately or delete queued content, and every call it makes is logged for review. ### How do I schedule social posts with the DunSocial API through Jentic? Search Jentic for 'schedule a social post', add the DunSocial API from the directory, and store your token once; your agent can then validate and schedule posts across the connected accounts on demand. To run it on your own infrastructure, install Jentic One from its GitHub repo.