project.updated
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.
Required ability
project:view-any — token must carry this at mint time to subscribe an endpoint to this event.
Payload
{
"id": "evt_01HX...",
"type": "project.updated",
"created_at": "2026-05-18T10:05:00Z",
"api_version": "2026-05-01",
"project_id": "prj_01HX...",
"data": {
"project": {
"id": "prj_01HX...",
"name": "Research Premium",
"handle": "research-premium",
"description": "Daily research drops and monthly AMAs.",
"active": true,
"team_id": "tem_01HX..."
},
"changes": {
"description": {
"from": "Weekly research drops.",
"to": "Daily research drops and monthly AMAs."
}
}
}
}Field reference
| Field | Type | Notes |
|---|---|---|
id | string ULID | Unique event id, prefixed evt_. Use for idempotent processing. |
type | string | Always project.updated for this event. |
created_at | ISO 8601 timestamp | Server-side emission time. |
api_version | string | Webhook API contract version. |
project_id | string ULID | Project this event belongs to. |
data.project | object | Full post-update project snapshot (same shape as project.created). |
data.changes | object<string, {from,to}> | Map of fields that changed. Keys are project attribute names; values are before/after. |
Caveats
- The
changesblock contains only the fields that mutated; unchanged fields are not included. - State transitions like archive / restore are not represented in
changes— listen forproject.archivedandproject.restoredinstead. - Bot rotation does not trigger
project.updated; seeproject.bot.connectedandproject.bot.disconnected.
Related events
project.created— predecessor for anyproject.updatedevent.project.archived,project.restored— dedicated state-transition events.- Project events overview — back to family overview.
How is this guide?