---
title: "Resource soft-deleted from a project."
method: POST
path: "project.resource.deleted"
tags: ["project.* events"]
---

# Resource soft-deleted from a project.

`POST project.resource.deleted` (webhook)

### When this fires

A resource is soft-deleted by the creator through the REST API or MCP. Existing subscriber access to the underlying place is not revoked by this action and no `member.resource_removed` events follow from it.

> This is the final event you will receive for the given `resource_id`. The row is retained with `deleted_at` stamped and disappears from the API.

### Caveats

- After this event, API endpoints scoped to the resource respond `404`.

### Related events

- `project.resource.unlinked`: typical predecessor.

## 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.resource.deleted', required: The event name, always `project.resource.deleted` 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.
    - `resource` object, required: Snapshot of the resource as it was immediately before deletion.
      - `id` string, uuid, required: Resource that was soft-deleted.
      - `title` string, required: Last-known title.
      - `kind` string, required: `manual`, or the connector's kind spelled `connector:kind` (`telegram:channel`).
      - `connector` string, nullable, required: The connector the place was on; `null` for a manual perk.
      - `space` object, nullable, required: The place it was bound to (`id`, `external_id`, `title`); `null` for a manual perk and for an unlinked row.
        - `id` string, uuid: Subscriby's id for the place.
        - `external_id` string: The platform's own id for the place.
        - `title` string: The place's title as the platform reported it.
      - `active` boolean, required: Last-known active flag.

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