Unified social media API for posting, scheduling, analytics, and account connection
Give your product one social layer for publishing, OAuth account connection, media uploads, analytics, comments, webhooks, and post history.
Last updated: May 2026
1const response = await fetch("https://api.bundle.social/api/v1/post", {2 method: "POST",3 headers: {4 "x-api-key": process.env.BUNDLE_SOCIAL_API_KEY,5 "Content-Type": "application/json"6 },7 body: JSON.stringify({8 teamId: "team_123",9 title: "Multi-platform campaign",10 postDate: "2026-05-14T10:00:00.000Z",11 status: "SCHEDULED",12 socialAccountTypes: ["TWITTER", "LINKEDIN", "INSTAGRAM", "TIKTOK", "FACEBOOK"],13 data: {14 TWITTER: { text: "Campaign is live." },15 LINKEDIN: { text: "We shipped a new product workflow today.", uploadIds: ["upload_li_img"] },16 INSTAGRAM: { type: "REEL", text: "Launch day.", uploadIds: ["upload_reel_123"] },17 TIKTOK: { type: "VIDEO", text: "Launch day behind the scenes.", uploadIds: ["upload_tiktok"] },18 FACEBOOK: { text: "Check out our new launch.", link: "https://example.com" }19 }20 })21});A pile of disconnected native integrations
What bundle.social handles
One API layer, many native realities
A unified API should not pretend every platform is identical. bundle.social normalizes the workflow while keeping platform-specific fields visible.
Workflow
How it works
Connect accounts once, then create and schedule posts with channel-specific fields from one API.
Create an API key
Generate an organization API key and use it from your backend with the x-api-key header.
Connect accounts
Connect the social accounts your product, agent, or customer workflow should manage.
Run the workflow
Call the API with platform-specific data while bundle.social tracks status, context, and dashboard visibility.
Capabilities
What a unified social API should include
Posting is only the start: account connection, media, status, comments, analytics, and webhooks belong in the same integration surface.
Single API key workflow
Create posts and query social data from server-side automations without distributing platform credentials. Securely manage access across your entire organization.
Platform-specific fields preserved
Instagram Reels, LinkedIn company pages, TikTok privacy fields, and YouTube metadata stay explicit. You never lose access to native features when unifying.
Shared dashboard fallback
When customers need review or support needs to inspect a failure, the same objects appear in the dashboard. Reduce engineering support tickets significantly.
Expansion beyond posting
Add analytics, post history, comments, webhooks, and account connection without replacing the first integration. Scale your product features faster.
Developer example
Create a unified social post
Examples use bundle.social's public API shape: API key authentication, a post date, selected social account types, and platform-specific data.
1const response = await fetch("https://api.bundle.social/api/v1/post", {2 method: "POST",3 headers: {4 "x-api-key": process.env.BUNDLE_SOCIAL_API_KEY,5 "Content-Type": "application/json"6 },7 body: JSON.stringify({8 teamId: "team_123",9 title: "Multi-platform campaign",10 postDate: "2026-05-14T10:00:00.000Z",11 status: "SCHEDULED",12 socialAccountTypes: ["TWITTER", "LINKEDIN", "INSTAGRAM", "TIKTOK", "FACEBOOK"],13 data: {14 TWITTER: { text: "Campaign is live." },15 LINKEDIN: { text: "We shipped a new product workflow today.", uploadIds: ["upload_li_img"] },16 INSTAGRAM: { type: "REEL", text: "Launch day.", uploadIds: ["upload_reel_123"] },17 TIKTOK: { type: "VIDEO", text: "Launch day behind the scenes.", uploadIds: ["upload_tiktok"] },18 FACEBOOK: { text: "Check out our new launch.", link: "https://example.com" }19 }20 })21});Supported content
Honest limitations
- Native API availability still varies by platform and account type.
- A unified workflow cannot bypass app review, content policy, or permission restrictions.
- Some advanced platform features remain platform-specific by design.
Guarantees
Developer-first infrastructure
2% error rate
We handle the platform edge cases, media processing, and rate limits so your requests succeed.
Verbose errors
When native APIs fail, we return human-readable error messages and actionable recovery steps.
Flat pricing
No per-post counting. Predictable pricing for teams managing many users, workspaces, and connected accounts.
Same-day support
Direct access to the engineers building the API. We respond to technical issues the same day. Sometimes the same hour. Test us c;
Resources
Technical guides & documentation
FAQ
Questions developers ask before building
Is this a wrapper around native social APIs?
Yes. bundle.social runs on top of native platform APIs and provides one workflow for the product layer around them.
Can I still access platform-specific options?
Yes. Platform payloads keep channel-specific fields so unification does not flatten important capabilities.
Who is this for?
SaaS products, AI agents, agencies, internal tools, and developer teams that need social workflows without owning every integration.