Social webhooks: one endpoint for every community, Send test and replay
A workspace-level Social webhook endpoint now receives the events of every community in the workspace, so you configure one receiver instead of one per community. Social webhooks also gain a Send test that shows what your server answered, a 30-day event log with replay, event descriptions, and Standard Webhooks signatures.
/v1/workspaces/:workspaceId/webhooks/endpoints manages up to 10 endpoints that receive the events of every community in the workspace, including communities created later. /v1/communities/:communityId/webhooks/endpoints does the same for one community. Each endpoint picks its events (an empty list means all of them, including future ones), and every delivery carries community_id and workspace_id at the top level. GET …/webhooks/event-types describes each of the 21 events with an example payload.
POST …/webhooks/endpoints/:id/test sends a signed example right away and returns what your receiver answered. GET …/webhooks/events lists the last 30 days of events with the state of each delivery, and POST …/webhooks/events/:id/replay sends one again. Secret rotation now has a grace period during which both secrets sign. Deliveries carry the Standard Webhooks headers webhook-id, webhook-timestamp and webhook-signature, and new secrets start with whsec_, so any Standard Webhooks library verifies them.
Webhooks you created before are now community endpoints with the same id, URL, events and secret. Until 15 January 2027 they also keep the x-pcft-signature header, and the old /v1/communities/:communityId/webhooks routes and GET /v1/webhook-event-types keep working with Deprecation and Sunset headers. See the Social webhooks guide for what to change.