project.restored
An archived project is re-activated.
When this fires
A previously archived project is restored. The public landing page becomes reachable again, the active flag returns to true, and new subscriptions can be created.
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.restored",
"created_at": "2026-05-18T10:05:00Z",
"api_version": "2026-05-01",
"project_id": "prj_01HX...",
"data": {
"project": {
"id": "prj_01HX...",
"active": true
}
}
}Field reference
| Field | Type | Notes |
|---|---|---|
id | string ULID | Unique event id, prefixed evt_. Use for idempotent processing. |
type | string | Always project.restored 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.id | string ULID | Project identifier; matches the top-level project_id. |
data.project.active | boolean | Always true for this event. |
Caveats
- Existing churned subscribers do not auto-re-activate. They must redeem a new subscription, which triggers
subscription.created. - Bot connections persist across archive / restore. No
project.bot.*events fire on restore.
Related events
project.archived— paired transition.subscription.created— emits when subscribers rejoin.- Project events overview — back to family overview.
How is this guide?