Webhooks

React the moment anything happens

Register one HTTPS endpoint and Postproxy pushes a signed event for everything that happens across your connected accounts. Posts publishing, comments and DMs coming in, reviews, reactions, delivery receipts. No polling, one schema.

Webhooks

One endpoint,
every event

Register once and Postproxy pushes a signed JSON event for everything across your connected accounts.

One schema, every platform

Instagram, WhatsApp, Google Business, TikTok, and the rest all deliver the same event envelope. One endpoint, one JSON shape, no per-platform plumbing.

Far more than post published

Subscribe to inbound DMs and comments, new reviews, reactions, referrals, delivery and read receipts, and fresh insights. The whole social surface arrives as events.

Signed, so you can trust it

Every request carries an X-Postproxy-Signature: an HMAC-SHA256 digest over the timestamp and raw body. Verify it with your secret in a few lines, in constant time.

Retried until it lands

A non-2xx or a timeout is retried up to five times with exponential backoff, from immediate to two hours. Every attempt is recorded, so you can see what was delivered.

The API

Register once, receive everything

Point one HTTPS endpoint at Postproxy, subscribe to the events you care about, and verify each signed delivery.

api.postproxy.dev
POST /api/webhooks
$ curl -X POST "https://api.postproxy.dev/api/webhooks" \
     -H "Authorization: Bearer $API_KEY" \
     -H "Content-Type: application/json" \
     -d '{
       "url": "https://yourapp.com/webhooks",
       "events": ["*"],
       "description": "Production events"
     }'
200 OK application/json
{
  "id": "wh_abc123",
  "url": "https://yourapp.com/webhooks",
  "events": ["*"],
  "enabled": true,
  "description": "Production events",
  "secret": "whsec_a1b2c3d4e5f6",
  "created_at": "2026-11-17T10:00:00Z",
  "updated_at": "2026-11-17T10:00:00Z"
}

View the full Webhooks reference, with event types and verification code

View documentation
Event types

Everything worth reacting to

Subscribe to the full surface of your connected accounts, or just the events you care about.

Publishing status

Know the moment a post is processed, published to each platform, or fails and needs another look.

Comments and reviews

New comments on your posts, plus Google Business reviews and Facebook recommendations, as they arrive.

Direct messages

Inbound and outbound messages, with delivery and read receipts, so your inbox stays in sync both ways.

Reactions and referrals

Likes on your messages, and taps from ig.me, m.me, and Click-to-WhatsApp ads that open a conversation.

Profile and placement health

Connections, disconnections, and paused placements, so you hear the moment an account needs reconnecting.

Insights

Fresh metrics for a published post, normalized across platforms, with the raw platform stats alongside.

More of the product

What sends the events

Webhook questions

How to register, what you can subscribe to, how to verify a request, and what happens on failure.

01 How do I start receiving events?

Create a webhook with POST /api/webhooks, giving an HTTPS url and the events you want (use ["*"] for all). Save the secret from the response. It is only shown at creation and when you fetch that single webhook, and you need it to verify signatures.

02 Do I need a separate webhook per platform?

No. One endpoint receives events from every connected account in a single, normalized schema. Instagram, Facebook, WhatsApp, Telegram, Bluesky, Pinterest, Google Business, YouTube, TikTok, Threads, LinkedIn, and X all deliver the same envelope.

03 Are webhooks global or per profile?

Global. A webhook is registered on your account and receives events from every connected profile and placement. There is no per-profile subscription, so to narrow things down you pick the event types at registration and filter on payload fields, like the platform or placement id, on your side.

04 Which events can I subscribe to?

Publishing (post.processed, platform_post.published, platform_post.failed, platform_post.insights), comments and reviews (comment.created, profile_comment.created), direct messages (message.received, message.sent, plus delivery and read receipts), reactions and referrals, and profile or placement changes. Subscribe to specific types, or to everything with *.

05 How do I verify a request came from Postproxy?

Each request includes an X-Postproxy-Signature header in the form t=timestamp,v1=digest. Recompute the HMAC-SHA256 of the timestamp, a dot, and the raw request body using your webhook secret, then compare it to v1 with a constant-time check. Ruby, Node, and Python examples are in the docs.

06 What happens if my endpoint is down?

Postproxy retries a failed or non-2xx delivery up to five times with exponential backoff: immediate, then 1 minute, 5 minutes, 30 minutes, and 2 hours. Your endpoint should return a 2xx within 30 seconds. After the last attempt the delivery is marked failed, and you can list every attempt with GET /api/webhooks/:id/deliveries.

07 How do I avoid processing the same event twice?

Every delivery has a unique id prefixed whevt_, which also arrives as the X-Postproxy-Delivery header. Store the ids you have handled and skip repeats, since a retry resends the same event.

Stop polling. Start listening.

Register one endpoint and let Postproxy push every event, signed and retried, the moment it happens.