plan.created

When this fires

A plan is created through the REST API (POST /v1/projects/{project}/plans) or the create_plan MCP tool, or a finished pass season is duplicated into its next season. Plans created from the creator dashboard or the bot do not emit this event. The plan is immediately eligible for purchase if it was created in the active state.

The two shapes are disjoint. The API and MCP path sends data.plan and nothing else; the season-duplication path sends the four flat keys and no data.plan object. Branch on whether data.plan or data.plan_id is present before reading any other field.

billing_cycle is only the unit. The multiplier lives in billing_cycle_count on the plan record and is not included in this payload: a "3 month" plan sends billing_cycle: "month" with no indication of the 3. Nor is trial_days. Fetch the plan with GET /v1/projects/{project}/plans/{plan} when you need the full cadence or trial configuration.

Caveats

A plan.created event does not imply the plan has been synced to a payment-provider catalog. Listen for plan.sync_completed for that.
Trial is configured at create time. A later trial-only edit is only applied, and only then fires plan.updated, when the PATCH also carries a kind key; without it the trial fields are dropped and no event is emitted.

Related events

plan.updated: subsequent edits.
plan.sync_completed: provider catalog sync.

Ability to subscribe

project-subscription-plan:view

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 endpointapplication/json

The signed JSON envelope posted to your endpoint.

The envelope every event is delivered in.

id*string

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

type*"plan.created"

The event name, always plan.created here.

Value in

"plan.created"

created_at*string

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

Formatdate-time

api_version*string

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

project_id*|

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

Formatuuid

data*

The event-specific payload. Keys that do not apply to a given emission are omitted rather than sent as null, so check for presence.

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.

Delivery to your endpoint

Subscriby sends this event as one HTTP request to every endpoint subscribed to it.

POSThttps://example.com/webhooks/subscribyyour endpoint URL

Headers

SB-Signature: t=1758636300,v1=5f1c…
SB-Event-Id: 01HXDELIVERY000000000TST
SB-Event-Name: plan.created
Content-Type: application/json
User-Agent: Subscriby-Webhooks/1.0

Body

{  "id": "evt_01HX...",  "type": "plan.created",  "created_at": "2026-05-18T10:05:00Z",  "api_version": "2026-05-01",  "project_id": "7f3d1c92-8b45-4e6a-9d21-5c8e0a4b6f13",  "data": {    "plan": {      "id": "c4e82f16-93a7-4d5b-b81c-6e0f27a94d3b",      "name": "Premium Monthly",      "price": "29.00",      "currency_id": "8f27a0d4-63be-4915-8c07-1a5d9e34b628",      "billing_cycle": "month",      "active": true    }  }}

Type definitions

The shapes above as types, ready to paste into your client.

export interface Body {  id: string;  type: "plan.created";  created_at: string;  api_version: string;  project_id: string | null;  data: Data;}export interface Data {  plan?: Plan;  plan_id?: string;  plan_name?: string;  kind?: "subscription" | "pass" | "pass_series";  duplicated_from_plan_id?: string;}export interface Plan {  id: string;  name: string;  price: string;  currency_id: string;  billing_cycle: "day" | "week" | "month" | "year" | "lifetime";  active: boolean;}

When it arrives

Verify the signatureCheck the SB-Signature header before trusting anything in the body.Answer 2xx within 30 secondsAny other answer, or none, and Subscriby retries the delivery.

De-duplicate on SB-Event-IdA retry carries the same id as the first attempt.