Skip to main content
Embedded webhooks notify your server when activity occurs for any end user in your partner project. Each payload identifies the affected end user so you can route it back to the correct customer.

Create a subscription

Webhook endpoints must use HTTPS and must be publicly reachable.
Omit events, or pass an empty array, to receive every recognized event that occurs for your embedded end users.
Useful events for an embedded publishing integration include:

Verify the signature

Social media studio signs the exact raw HTTP request body with HMAC-SHA256. Read the body as text or bytes and verify it before parsing JSON.
The signature may be sent as a hexadecimal digest or with a v1= prefix; the SDK accepts both forms.

Payload shape

Delivery requests also include:

Delivery behavior

  • Return a 2xx response as soon as the event is durably accepted.
  • Process events asynchronously when work may take more than a few seconds.
  • Deduplicate deliveries using the payload id or X-Webhook-Delivery-Id.
  • Non-2xx responses, network failures, and timeouts are retried with exponential backoff.
  • Repeatedly failing subscriptions are automatically disabled.
Webhook delivery is at least once, so handlers must be idempotent.