---
title: "A subscriber is entitled to a resource but has no account on its connector yet, so access waits for them to connect one."
method: POST
path: "member.resource_pending"
tags: ["member.* events"]
---

# A subscriber is entitled to a resource but has no account on its connector yet, so access waits for them to connect one.

`POST member.resource_pending` (webhook)

### When this fires

A purchase entitles a subscriber to a resource on a connector where the subscriber has no connected account: a member who bought on the portal with only an email, or a plan that spans a connector the member has not linked. Nothing can be issued, so the access ledger records a grant in state `pending_identity` and this event says so. The moment the member connects an account on that connector (from the portal, by signing in through the connector, or by adopting an account from a sibling project), the grant is issued and `member.resource_added` follows with the same `grant_id`.

### Caveats

- One event per resource the purchase entitles the member to on that connector; a plan with three channels raises three, all waiting on the same account.
- Nothing is sent to the member by the bot; it cannot reach them yet. The portal shows the pending access on the membership card; an integration that wants to nudge them should use the email it holds.
- A subscription that ends before the account is connected leaves the grant `pending_identity` in the ledger; no `member.resource_removed` is raised for access that was never given.

### Related events

- `member.resource_added`: raised for the same `grant_id` once the account is connected and access is issued.
- `member.identity_linked`: the act that releases the pending grants.

## 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_pending', required: The event name, always `member.resource_pending` 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 that entitles the member.
    - `subscriber_id` string, uuid, required: Subscriber's project-scoped user id.
    - `resource_id` string, uuid, required: Resource the member is waiting to be admitted to.
    - `resource_kind` string, required: The resource's kind: `manual`, or `connector:kind` (`telegram:channel`).
    - `connector` string, required: The connector the member needs an account on.
    - `grant_id` string, uuid, required: The access ledger row, in state `pending_identity`; read it with [the subscription grants endpoint](https://docs.subscriby.net/api/v1/reference/subscriptions).
    - `mode` 'bearer_link' | 'membership' | 'role' | 'creator_task', required: How access will be given once the account is connected.

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