Social Media Webhooks API

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: July 2026

View API docs

One API key. No per-account fees. 15 platforms.

API key authScheduled publishing15 platforms

Quick start

API request

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}

Official APIs500k+ connected accountsDirect engineer support

Polling every social workflow

Without webhooks, products poll for post status and still miss the exact moment a workflow changes.

Native platforms expose event models inconsistently, so each integration needs separate listener logic.

Operations teams need failed-post alerts inside their own tools, not only in a social dashboard.

What bundle.social handles

React to bundle.social workflow events from your own backend.

Use status changes to update campaigns, notify users, or trigger retries in your product.

Keep webhook logic tied to one social layer instead of every native platform separately.

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.

Product architecture

Build social media workflows without rebuilding every platform

Social media webhooks API for publishing events and status

SaaS products, agencies, AI workflows, and internal tools need to react when publishing state changes, and that is the whole case for a webhooks API. Scheduled posts depend on media processing, token validity, platform review, and community rules, so the outcome is not known when the post is created. Without events, products poll for status and still learn about failures late.

bundle.social delivers workflow events to your own endpoint as posts move through their lifecycle. Your backend can update campaign records, notify customers, trigger retries, and route failures into support tools using the post identifier and error detail that arrive with each event.

Webhook endpoints need verification and idempotency

A webhook endpoint is a public route that changes your data, so signature verification and deduplication are part of the integration rather than optional hardening. Deliveries can repeat, and a slow handler produces retries that turn into duplicate records.

The practical pattern is to verify the payload with the configured secret, acknowledge quickly, and process the work from a queue keyed on the event and post identifiers. bundle.social scopes webhook destinations to teams and accounts, so multi-tenant products can route each customer's events to the right workspace while API queries remain available for reconciliation.

Events beside publishing, analytics, and automation workflows

The first thing most teams build on events is failure visibility. A failed post routed into Slack, a support tool, or a customer-facing campaign view turns a silent problem into an owned one, with the error attached to the customer and campaign it belongs to.

The same events then support automation. Agent workflows and backend jobs can react to a published or failed state instead of sleeping on a timer, and webhook coverage follows bundle.social workflow events rather than every event a native platform might emit, so the contract stays stable while platforms change underneath.

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.

TypeScript

API request

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

Post status eventsPublishing failuresAutomation triggersOperational alerts

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

Visible post status

Track scheduled, processing, posted, retrying, and error states per post.

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.

Resources

Technical guides & documentation

API Reference: Webhooks

Complete documentation on webhook payloads, signatures, and event types.

Unified Social Media API

See how webhooks fit into publishing, scheduling, uploads, analytics, and comments.

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.

Social Media Posting API

Create posts that emit events.

Social Media API for AI Agents

Use events in agent workflows.

Social Media Analytics API

Report on outcomes after events.