Back to docs

Webhooks

Webhooks

Receive signed HTTP notifications when links, campaigns, and posts change in your workspace.

ClaudeChatGPTCursor

Styrar webhooks send signed HTTP notifications when resources in your workspace change. Use them to sync links and clicks to a CRM, trigger automations in your stack, or stream funnel events into a data warehouse.

Plan requirement: Programmatic API access (including API keys used to manage webhooks via /v1/webhooks/*) requires a Team or Agency plan. Free and Solo workspaces do not include API access. See Authentication and pricing.

This replaces the retired link-only webhooks API (/v1/link-webhooks). New integrations should use /v1/webhooks/* only.

What you can build

  • Sync short links and clicks to a CRM or data warehouse
  • Trigger internal automations when a post publishes (post.published)
  • Provision campaign folders when a campaign is created (campaign.created)
  • React when a link A/B experiment completes (link.experiment.completed)
  • Close the loop between campaigns, posts, short links, and downstream tools

Supported event types today: link.created, link.updated, link.deleted, link.clicked, link.experiment.completed, campaign.created, post.published, plus on-demand webhook.test. Call GET /v1/webhooks/event-types for the live catalog.

How it works

  1. You register a public HTTPS endpoint in Settings → Webhooks or via the API.
  2. Styrar delivers signed POST requests when subscribed event types fire.
  3. Your server verifies the signature, returns 2xx, and processes the payload asynchronously.

Deliveries are at-least-once. Deduplicate on Styrar-Event-Id.

Guides in this section

GuideDescription
Set up an endpointDashboard and API setup, test events, go live
Verify signaturesStyrar-Signature header and HMAC verification
Webhook APIList endpoints, deliveries, and management routes

For event payloads and field reference, see Events.

Related