plan.* events

Inactive plan flipped active.

When this fires

An inactive plan is flipped to active through the REST API (POST /v1/projects/{project}/plans/{plan}/publish) or the publish_plan MCP tool, and becomes purchasable on the project landing page. Toggling a plan on from the creator dashboard does not emit this event.

Caveats

  • Publishing a plan that is already active is a no-op: nothing is written and no event is emitted.
  • Activation does not retroactively touch existing subscriptions on the plan; only checkout availability changes.
  • Frequent flipping is permitted but produces noisy timelines; use plan.updated for non-state edits.

Related events

  • plan.deactivated: paired transition.
  • plan.created: predecessor.
postWebhookplan.activated

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'plan.activated' required

The event name, always plan.activated 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.