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

# Any mutable project field changes.

`POST project.updated` (webhook)

### When this fires

Any mutable field on a project changes: display name, handle, description, terms, privacy text, or other dashboard-editable settings. State-flag transitions (archive, restore) emit dedicated events instead.

### Caveats

- The `changes` block contains only the fields that mutated; unchanged fields are not included.
- `changes` can report fields the `project` snapshot does not carry: `description`, `terms`, `privacy`, `metrics`, `banner_url`, and `photo_url`. Read the new value from `changes[field].to`, or fetch the project from [the project endpoint](https://docs.subscriby.net/api/v1/reference/projects).
- `POST /v1/projects/{project}/archive` and `/restore` emit the dedicated `project.archived` / `project.restored` events, but a plain `PATCH` that sets `active` reports the flip in `changes.active` on `project.updated` instead. Handle both.
- Connecting or disconnecting an installation does not trigger `project.updated`; it emits `connector.connected` / `connector.disconnected`.

### Related events

- `project.created`: predecessor for any `project.updated` event.
- `project.archived`, `project.restored`: dedicated state-transition events.

## 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` 'project.updated', required: The event name, always `project.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.
    - `project` object, required: Post-update project snapshot: `id`, `name`, `handle`, `active`, `team_id` only.
      - `id` string, uuid, required: Project identifier; matches the top-level `project_id`.
      - `name` string, required: Display name after the change.
      - `handle` string, required: URL slug for the public landing page after the change.
      - `active` boolean, required: Active flag after the change.
      - `team_id` string, uuid, required: Team that owns the project.
    - `changes` object, required: Map of fields that changed. Keys are project attribute names; values are `from` / `to` pairs.

## 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)