Skip to main content

​
Deliveries, Testing, and Automation

Use these endpoints to validate webhook endpoints, inspect delivery outcomes, and manage outbound automations.

​
Workspace webhook operations

  • POST /api/webhooks-manage/:id/test
  • POST /api/webhooks-manage/:id/enable
  • GET /api/webhooks-manage/:id/deliveries
These are workspace-level webhook records used for core webhook dispatch.
  • POST /api/links/:linkId/webhooks/:webhookId/test
  • POST /api/links/:linkId/webhooks/:webhookId/redeliver/:deliveryId
  • POST /api/links/:linkId/webhooks/:webhookId/rotate-secret
  • GET /api/links/:linkId/webhooks/:webhookId/deliveries
  • GET /api/links/:linkId/webhooks/:webhookId/deliveries/:deliveryId
Link webhook routes validate link ownership inside the workspace before delivery actions.

​
Outbound automation operations

  • GET /api/integrations/outbound
  • GET /api/integrations/outbound/events
  • POST /api/integrations/outbound
  • GET /api/integrations/outbound/:id
  • PATCH /api/integrations/outbound/:id
  • DELETE /api/integrations/outbound/:id
  • POST /api/integrations/outbound/:id/test
  • GET /api/integrations/outbound/:id/deliveries
Outbound webhooks support event subscriptions for clicks, leads, sales, partner, commission, bounty, and payout lifecycle events. Use the canonical trigger list and event pages here:
  • /api-reference/webhooks/event-types

​
Security and signing

  • Workspace and link webhook secrets are not fully exposed on normal read responses.
  • Outbound and test deliveries are signed with Svix/Standard Webhooks headers:
    • svix-id
    • svix-timestamp
    • svix-signature
    • and unbranded aliases (webhook-id, webhook-timestamp, webhook-signature)
  • Secret rotation is supported for link webhooks.

​
Testing workflow

  1. Create webhook and confirm destination URL is reachable.
  2. Trigger test endpoint.
  3. Inspect delivery status code, response body, and response time.
  4. Use redelivery for failed link-webhook deliveries.
  5. Re-enable disabled webhook after fixing endpoint issues.

​
Permissions and gates

  • Workspace/link webhook operations follow link permission families.
  • Outbound read/mutate uses webhooks:read and webhooks:manage.
  • Outbound mutations are integration-feature gated.

​
Common errors

  • 400: invalid URL/event/filter/update payload
  • 403: permission denied or feature gate denial
  • 404: webhook/link/delivery not found in workspace scope
  • 409: duplicate outbound webhook URL in workspace