subscription.* events

A member whose access was paused for non-payment was let back in.

When this fires

A charge settled, or the rail reported the subscription active, for a member whose access had been paused at the close of a grace window. Their bearer links are revoked and reissued, they are welcomed back, and the clock is cleared. It fires beside subscription.payment_recovered, which carries the payment; this one carries the pause it undid.

Related events

  • subscription.access_suspended: the pause.
  • subscription.payment_recovered: the charge, raised beside this.
  • member.resource_added: the resources the member rejoins.
postWebhooksubscription.access_restored

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'subscription.access_restored' required

The event name, always subscription.access_restored 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.