link.* events

A new Smart Link was authored in a project.

When this fires

A creator authored a new Smart Link on the dashboard, over the REST API or via the create_link MCP tool. The link answers at url from this moment: a click counts, the visit waits in the visitor's browser for up to thirty days, and the member who signs in inside that window is attributed to the link.

It fires on authoring, not on the first click. A link created with an expires_at fires this immediately and stops counting when that instant passes; there is no separate event for the expiry.

Related events

  • link.updated: the link's fields changed.
  • link.archived: the link was put out of use.
postWebhooklink.created

Headers

SB-Signaturestring required

t=<unix seconds>,v1=<hex>: the HMAC-SHA256 of "<t>.<raw body>" under the endpoint's secret. Verify it before acting, and refuse a t more than 300 seconds from now. During a secret rotation a v0= signature under the previous secret may precede v1=.

SB-Event-Idstring required

The event's ULID, bare. The envelope's id is the same ULID prefixed evt_, so strip the prefix before comparing. Deduplicate on it: a retry carries the same id.

SB-Event-Namestring required

The event name, the same as the envelope's type.

Content-Typestring required

Always application/json.

User-Agentstring required

Always Subscriby-Webhooks/1.0.

Payload

idstring required

A ULID unique to the event, prefixed evt_. Every retry carries the same id, so it is the key to deduplicate on.

type'link.created' required

The event name, always link.created here.

created_atstring date-time required

When the event was emitted, server time, ISO 8601.

api_versionstring required

The contract version of the payload shape, 2026-05-01 today. A breaking change to a shape ships under a new version.

project_idstring uuid nullable required

The project the event belongs to; null for team-scoped and billing events.

Response

Your endpoint acknowledged the delivery. Any 2xx status within 30 seconds marks it delivered; the response body is ignored.

Changes

Webhooks have no change history: a webhook is keyed by its event name rather than a path and method, so no recorded change can name it.