---
title: "Any mutable plan field changes."
method: POST
path: "plan.updated"
tags: ["plan.* events"]
---

# Any mutable plan field changes.

`POST plan.updated` (webhook)

### When this fires

A plan is edited through the REST API (`PATCH /v1/projects/{project}/plans/{plan}`): pricing, name, currency, billing cadence, eligibility filters. Edits made in the creator dashboard do not emit this event, and trial fields are only written (and only then reported) when the payload also carries `kind`. An `active` flag sent on a PATCH is reported here as an ordinary `changes.active` entry. The dedicated `plan.activated` and `plan.deactivated` events come only from the publish and unpublish endpoints.

### Caveats

- Existing subscriptions priced on the old terms are not retroactively re-priced. New checkouts use the new price; renewals follow the billing rules.
- An `active` flag sent on a PATCH is reported here as an ordinary `changes.active` entry. The dedicated `plan.activated` and `plan.deactivated` events come only from the publish and unpublish endpoints.

### Related events

- `plan.activated`, `plan.deactivated`: dedicated active-flag events.
- `plan.sync_completed`: fires after price changes propagate to the provider catalog.

## Headers

- `SB-Signature` string, required
- `SB-Event-Id` string, required
- `SB-Event-Name` string, required
- `Content-Type` string, required
- `User-Agent` string, required

## Payload

- object: The envelope every event is delivered in.
  - `id` string, 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.updated', required: The event name, always `plan.updated` here.
  - `created_at` string, date-time, required: When the event was emitted, server time, ISO 8601.
  - `api_version` string, required: The contract version of the payload shape, `2026-05-01` today. A breaking change to a shape ships under a new version.
  - `project_id` string, uuid, nullable, required: The project the event belongs to; null for team-scoped and billing events.
  - `data` object, required: The event-specific payload. Keys that do not apply to a given emission are omitted rather than sent as null, so check for presence.
    - `plan` object, required: Full post-update plan snapshot, the same shape as `plan.created`.
      - `id` string, uuid, required: Plan identifier.
      - `name` string, required: Display name.
      - `price` string, decimal, required: Decimal amount as a string, e.g. `"29.00"`.
      - `currency_id` string, uuid, required: Currency row id, **not** an ISO 4217 code.
      - `billing_cycle` 'day' | 'week' | 'month' | 'year' | 'lifetime', required: Billing cadence unit.
      - `active` boolean, required: Whether the plan is purchasable after the change.
    - `changes` object, required: The fields that changed, each a `{from, to}` pair keyed by the plan attribute. `from` is the plan's previous value after model casting (price is a string, enum columns are their backed string value); `to` is the caller-supplied value as validated.

## Acknowledgement `2XX`

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

## Other responses

- `default`: 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.

---

[API](https://skmtc.dev/memberpass/apis/subscriby-rest-api.md) · [All operations](https://skmtc.dev/memberpass/apis/subscriby-rest-api/llms.txt) · [OpenAPI document](https://skmtc.dev/memberpass/apis/subscriby-rest-api/revisions/59c4df91d764?raw)