Webhook Destinations (Removed)

Webhook destinations have been removed from the Platform API.

Removed. Webhook destinations and the inbound webhook receive endpoint have been permanently removed from the Platform API as of v0.9.581. All endpoints listed below return 404.

What Was Removed

Webhook destinations allowed external systems to fire platform triggers by sending HMAC-signed HTTP payloads to a dedicated receive endpoint. The feature included:

• CRUD endpoints for managing webhook destinations (create, list, get, update, delete)

• Secret rotation with a grace period for seamless key rollover

• An inbound receive endpoint that verified HMAC signatures and fired the linked trigger

• Field mapping, event type filtering, and delivery history

Migration

If you were using webhook destinations to fire triggers from external systems, use direct API-key-authenticated trigger firing as an alternative.

Previously Available Endpoints

All of the following endpoints have been removed and return 404:

Method	Path	Description
POST	/v1/{workspace_id}/webhook-destinations	Create a webhook destination
GET	/v1/{workspace_id}/webhook-destinations	List webhook destinations
GET	/v1/{workspace_id}/webhook-destinations/{destination_id}	Get a webhook destination
PUT	/v1/{workspace_id}/webhook-destinations/{destination_id}	Update a webhook destination
DELETE	/v1/{workspace_id}/webhook-destinations/{destination_id}	Delete a webhook destination
POST	/v1/{workspace_id}/webhook-destinations/{destination_id}/rotate-secret	Rotate signing secret
GET	/v1/{workspace_id}/webhook-destinations/{destination_id}/deliveries	List delivery history
POST	/v1/{workspace_id}/hooks/{destination_id}	Receive inbound webhook