Social media webhooks API for post status and publishing events
Receive social publishing lifecycle events in your own product so teams can react to posted, failed, retried, and account-related changes without polling every workflow.
Last updated: May 2026
1export async function POST(request: Request) {2 const event = await request.json();34 if (event.type === "post.published") {5 const postId = event.data.postId;67 if (event.data.errors?.length || event.data.verboseErrors?.length) {8 await markCampaignItemFailed(postId, event.data.errors ?? event.data.verboseErrors);9 } else {10 await markCampaignItemLive(postId);11 }12 }1314 return new Response("ok");15}Polling every social workflow
What bundle.social handles
Stop polling for publishing state
Webhooks turn social publishing from a black box into an event stream your product can use for alerts, customer UX, and automation.
Workflow
How it works
Connect accounts once, then create and schedule posts with channel-specific fields from one API.
Configure your endpoint
Set up a webhook endpoint in your dashboard to receive events for your entire organization.
Verify the signature
Validate the incoming webhook payload using the provided secret to ensure it came from bundle.social.
Process the event
React to the event type (e.g., `post.published`, `post.failed`) and update your database or notify users.
Capabilities
Webhook events for social publishing operations
Connect post lifecycle events to your product's own database, notifications, and automation logic.
Post status events
Trigger downstream logic when posts are scheduled, posted, failed, or retried. Avoid building complex polling systems.
Team-scoped configuration
Keep webhook destinations aligned with the teams and accounts that own the content. Multi-tenant support built-in.
Operational alerts
Pipe failed publishing events into support tools, Slack, or customer-facing campaign views. Reduce mean time to resolution.
Automation handoff
Let agents and backend jobs react after publishing instead of guessing with timers. Build reliable event-driven pipelines.
Developer example
Handle a social publishing webhook
Examples use bundle.social's public API shape: API key authentication, a post date, selected social account types, and platform-specific data.
1export async function POST(request: Request) {2 const event = await request.json();34 if (event.type === "post.published") {5 const postId = event.data.postId;67 if (event.data.errors?.length || event.data.verboseErrors?.length) {8 await markCampaignItemFailed(postId, event.data.errors ?? event.data.verboseErrors);9 } else {10 await markCampaignItemLive(postId);11 }12 }1314 return new Response("ok");15}Supported content
Honest limitations
- Your endpoint must be reachable and respond quickly to webhook deliveries.
- Webhook coverage follows bundle.social workflow events, not every event a native platform might expose.
- Consumers should still handle retries and idempotency in their own system.
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
What are social media webhooks used for?
They notify your product when social workflows change state, such as posted, failed, scheduled, or retried events.
Do webhooks replace polling?
For most status workflows, yes. You can still query the API for reconciliation or manual debugging.
Can I use webhooks with AI agents?
Yes. Webhooks are a good feedback signal for agent workflows that need to react after publishing or failure.