member.resource_added
A subscriber gains access to a specific resource.
When this fires
Subscriby asks the resource's connector to give a subscriber access to one of the resources their subscription grants (on a connector that grants by link, a join-request invite link named after them) and writes the grant to the access ledger. Each resource grant emits its own event. The event marks the grant, not the subscriber's arrival: they may not have opened the link yet; the ledger row named by grant_id moves from pending to granted when they do. A manual perk arrives here too, once the creator completes its task (creator_task.completed precedes it).
Caveats
- Ordering against the join event is not guaranteed: the dispatcher is queued before
member.joinedis emitted on the access-code path, and paid joins emit nomember.*join event at all. Treat resource events as independent. - A manual perk emits this event only when its creator task is completed, never at purchase; until then the member's grant is
pendingandcreator_task.openedis what fired.
Related events
member.resource_removed: paired transition.member.joined,member.trial_joined: typical predecessors.
Header Parameters
t=<unix seconds>,v1=<hex>: the HMAC-SHA256 of "<t>.<raw body>" under the endpoint's secret. Verify it before acting, and refuse a t more than 300 seconds from now. During a secret rotation a v0= signature under the previous secret may precede v1=.
The event's ULID, bare. The envelope's id is the same ULID prefixed evt_, so strip the prefix before comparing. Deduplicate on it: a retry carries the same id.
The event name, the same as the envelope's type.
Always application/json.
Always Subscriby-Webhooks/1.0.
Request Body
application/json
The signed JSON envelope posted to your endpoint.
TypeScript Definitions
Use the request body type in TypeScript.
The envelope every event is delivered in.
Response Body
Example Requests
/member.resource_addedHow is this guide?