Version
WEBHOOK

project.archived

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.

Ability to subscribe

A token needs this to subscribe an endpoint to the event.

Header Parameters

SB-Signature*string

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-Id*string

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-Name*string

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

Content-Type*string

Always application/json.

User-Agent*string

Always Subscriby-Webhooks/1.0.

Payload

JSONWhat Subscriby posts to your endpoint

The signed JSON envelope posted to your endpoint.

The envelope every event is delivered in.

Responses

2XXAny success status

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

defaultAny other status

Any other status, a connection failure, or no answer within 30 seconds counts as a failed attempt. The delivery is retried 8 times, after 10 seconds, 30 seconds, 2 minutes, 10 minutes, 1 hour, 6 hours, 1 day, 3 days; the last failure dead-letters it, and it can be retried from the dashboard or POST /v1/webhook-deliveries/{delivery}/retry. After 20 consecutive failures the endpoint is paused until it is resumed.

How is this guide?

Last updated on