Any mutable project field changes.
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.
- 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
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.
Payload
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.