---
title: "A subscriber loses access to a specific resource."
method: POST
path: "member.resource_removed"
tags: ["member.* events"]
---

# A subscriber loses access to a specific resource.

`POST member.resource_removed` (webhook)

### When this fires

A subscriber is evicted from a specific resource: after a subscription expires or is cancelled, after a ban, kick or removal, or when a pass window closes or is cancelled. Each resource revocation emits its own event. Nothing is emitted when another still-active subscription of theirs grants the same resource: the invite link is revoked but the member stays in.

### Caveats

- Multiple revocations for the same subscriber typically arrive in close succession when a subscription expires; use `SB-Event-Id` for dedupe.
- A manual perk emits this event only when its grant is revoked on the ledger; a place a connector gates emits it once the connector has been asked to remove the member.

### Related events

- `member.resource_added`: paired transition.
- `subscription.expired`, `subscription.cancelled`, `member.kicked`: typical triggers.

## 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` 'member.resource_removed', required: The event name, always `member.resource_removed` 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.
    - `subscription_id` string, uuid, required: Subscription whose grant was revoked.
    - `subscriber_id` string, uuid, required: Subscriber's project-scoped user id.
    - `resource_id` string, uuid, required: Resource the subscriber lost access to.
    - `resource_kind` string, required: The resource's kind: `manual`, or `connector:kind` (`telegram:channel`).
    - `connector` string, nullable, required: The connector the member was removed through.
    - `grant_id` string, uuid, nullable, required: The access ledger row that ended, now `revoked`; read it back with [the subscription grants endpoint](https://docs.subscriby.net/api/v1/reference/subscriptions). Null when the ledger never held a grant for this resource.
    - `mode` 'bearer_link' | 'membership' | 'role' | 'creator_task' | 'null', nullable, required: How the access had been given.

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