project.* events

Creator archives the project; access is suspended.

When this fires

A project is archived through POST /v1/projects/{project}/archive or the MCP archive_project tool. Archiving from the dashboard does not emit this event. The only state change is the project's active flag flipping to false; existing subscriptions and the public landing page are untouched.

Caveats

  • Archive is reversible; pair with project.restored for the inverse transition.
  • Subscribers retain their existing access until their ends_at ticks over. Expect subscription.expired events to follow as those subscriptions wind down.
  • Hard-delete fires project.deleted instead and is final.

Related events

  • project.restored: paired transition.
  • project.deleted: terminal state, replaces archive when the row is hard-deleted.
postWebhookproject.archived

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'project.archived' required

The event name, always project.archived 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.