plan.order_changed
The creator arranged the order plans appear in on the portal and in the bot, or reset it.
When this fires
A creator drags plans into a new order in the dashboard's Arrange Storefront Order dialog and saves, calls POST /v1/projects/{project}/plans/order, or runs the reorder_plans MCP tool. Resetting to the built-in order fires it too. The event carries the resulting order of every plan currently on sale, so a mirror of the storefront can re-sort itself without a second read.
The built-in order is passes first, then seasons, then subscriptions, each group cheapest first. Plans created after an arrangement join the end in that order until the creator arranges again, so
plan_idson this event may be shorter than the plan list read a week later.
Related events
plan.created: a new plan joins the end of the storefront.plan.activated,plan.deactivated: a plan entering or leaving the storefront.
Header Parameters
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=.
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.
The event name, the same as the envelope's type.
Always application/json.
Always Subscriby-Webhooks/1.0.
Request Body
application/json
The signed JSON envelope posted to your endpoint.
TypeScript Definitions
Use the request body type in TypeScript.
The envelope every event is delivered in.
Response Body
Example Requests
/plan.order_changedHow is this guide?