Back to docs

Events

Events

Outbound event envelope and when each event type fires.

Styrar emits outbound events when workspace resources change: links are created or clicked, campaigns start, posts publish, and more. Events are the data inside webhook deliveries.

Plan requirement: Receiving webhook deliveries requires a Team or Agency workspace when you manage endpoints via the API. See Authentication.

Event envelope

Every delivery uses the same top-level JSON shape. Event-specific fields live under data.object:

FieldTypeDescription
idstringUnique event id (same as Styrar-Event-Id header)
typestringEvent name (for example link.clicked)
api_versionstringPayload schema version (2026-06-22)
created_atstringISO 8601 timestamp
workspace.typestringcompany or personal
workspace.company_idstring | nullCompany id when workspace is company-scoped
data.objectobjectEvent payload (documented per type)

Available events

EventWhen it fires
link.createdA short link is created
link.updatedA short link is updated
link.deletedA short link is soft-deleted
link.clickedA tracked click is recorded
link.experiment.completedAn A/B test completes with a winner
campaign.createdA campaign is created
post.publishedA post publishes to all platform targets
webhook.testYou send a test ping from the dashboard or API

Call GET /v1/webhooks/event-types for the live catalog in your environment.

Guides in this section

GuideDescription
Event typesFull payload reference for every event
WebhooksRegister endpoints and receive deliveries

Webhooks vs REST

ApproachBest for
WebhooksReal-time reactions (CRM sync, automations, warehouses)
REST APIOn-demand reads and writes when your system polls or drives the flow

Many integrations use both: webhooks for push notifications and the REST API for backfills or mutations.

Join the beta waitlist

By signing up you agree to receive marketing email. See our Privacy Policy.