Skip to main content
BlendDuck Docs

BlendDuck documentation

Learn to plan, review, publish, and measure social content with BlendDuck.

Documentation owner:
BlendDuck Documentation
Last reviewed:

BlendDuck brings social channels, a shared calendar, approvals, inbox conversations, analytics, and developer tools into one workspace. These guides start with the job you need to complete and call out permissions and platform-specific limits along the way.

Choose your path

I want to...Start here
Launch a brand or client workspace safelyOwner's workspace launch checklist
Schedule my first post10-minute quickstart
Set up a client or stakeholder reviewClient approval playbook
Check what a social platform supportsChannel capability matrix
Understand social connection recoveryAutomatic channel recovery
Build a monthly or campaign reportAnalytics reporting playbook
Integrate through codeREST API guide

Get a first post scheduled

  1. Follow the 10-minute quickstart.
  2. Connect a social channel.
  3. Create, preview, and schedule a post.
  4. Confirm its state in Calendar.

Use the channel capability guide before choosing account types or promising Analytics and Inbox access for a client.

For setup and publishing details, use the dedicated guides for Instagram/Facebook, LinkedIn, X, TikTok, YouTube, Google Business Profile, Pinterest, Reddit, Discord/Telegram, Threads/Bluesky/Mastodon, and Snapchat.

Create and collaborate

GoalGuide
Prepare media and avoid provider rejectionsMedia guide
Schedule many postsBulk scheduling
Collect internal or client sign-offContent approvals
Rehearse an end-to-end client reviewClient approval playbook
Invite teammates and control accessTeams and permissions
Reply to comments and messagesSocial Inbox
Compare results across platformsAnalytics
Keep AI-assisted drafts on-brandBrand Soul
Ground drafts in approved factsKnowledge Base
Manage privacy and workspace controlsAccount and workspace settings

Build with BlendDuck

Developers can start with the REST API guide, install one of the generated SDKs, subscribe to webhooks, or connect an AI client through MCP. The published OpenAPI 3.1 schema is the source of truth for request and response shapes.

Need help?

Use Troubleshooting for connection, publishing, approval, Inbox, and API failures. When escalating a problem, include the workspace, affected channel, approximate time, and the displayed request ID. Never send an API key, OAuth token, webhook secret, or one-time sign-in code.

On this page