---
title: "An archived project is re-activated."
method: POST
path: "project.restored"
tags: ["project.* events"]
---

# An archived project is re-activated.

`POST project.restored` (webhook)

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

### Caveats

- Existing churned subscribers do not auto-re-activate. They must redeem a new subscription, which triggers `subscription.created`.
- Connector installations persist across archive / restore. No `connector.*` events fire on restore.

### Related events

- `project.archived`: paired transition.
- `subscription.created`: emits when subscribers rejoin.

## 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.restored', required: The event name, always `project.restored` 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: Snapshot of the restored project.
      - `id` string, uuid, required: Project identifier; matches the top-level `project_id`.
      - `name` string, required: Display name.
      - `handle` string, required: URL slug for the public landing page.
      - `active` boolean, required: Always `true` for this event.
      - `team_id` string, uuid, required: Team that owns the project (a personal team for solo creators).

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