Skip to main contentWebhooks API
Linquid has multiple webhook systems for different scopes.
Webhook systems
- Workspace webhook manager (
/webhooks-manage/*)
- Link webhook manager (
/links/:linkId/webhooks/*)
- Integration outbound hooks (
/integrations/outbound/*)
- Provider inbound integration callbacks (
/integrations/webhooks/*)
Endpoint matrix
Workspace webhook manager
GET /webhooks-manage
POST /webhooks-manage
GET /webhooks-manage/:id
PATCH /webhooks-manage/:id
DELETE /webhooks-manage/:id
POST /webhooks-manage/:id/test
POST /webhooks-manage/:id/enable
GET /webhooks-manage/:id/deliveries
Link-specific webhooks
GET /links/:linkId/webhooks
POST /links/:linkId/webhooks
GET /links/:linkId/webhooks/:webhookId
PATCH /links/:linkId/webhooks/:webhookId
DELETE /links/:linkId/webhooks/:webhookId
GET /links/:linkId/webhooks/:webhookId/deliveries
GET /links/:linkId/webhooks/:webhookId/deliveries/:deliveryId
POST /links/:linkId/webhooks/:webhookId/test
POST /links/:linkId/webhooks/:webhookId/redeliver/:deliveryId
POST /links/:linkId/webhooks/:webhookId/rotate-secret
Link webhook events:
Workspace outbound trigger names are documented in:
/api-reference/webhooks/event-types
Integration outbound hooks
See integrations outbound hooks:
GET /integrations/outbound
POST /integrations/outbound
GET /integrations/outbound/events
Provider inbound callbacks
/integrations/webhooks/stripe
/integrations/webhooks/shopify
/integrations/webhooks/hubspot
/integrations/webhooks/slack/*
/integrations/webhooks/zapier/*
These are callback receivers and use provider/signature auth models, not dashboard session CSRF flow.
Permission and feature gates
- Workspace/link webhook management uses links/webhooks permissions.
- Webhook creation/update paths can be feature-gated by plan (
webhooks/integrations).
- Delivery inspection routes require read-level permissions.
Operational behavior
- Test delivery endpoints support endpoint validation before enabling.
- Delivery logs support observability and retry/redelivery flows.
- Secret rotation endpoints invalidate old signature secrets for future deliveries.
Typical failures
403 permission/feature denial
404 webhook or delivery not found in scope
- signature verification errors on inbound provider callbacks
- destination delivery failures recorded in delivery history
Related docs:
/api-reference/webhooks/event-types
/api-reference/webhooks/workspace-and-link-webhooks
/api-reference/webhooks/deliveries-testing-and-automation
/user-guides/manual/ecosystem/integrations-and-webhooks-reference
/user-guides/manual/ecosystem/workspace-integrations-reference