member.access_extended
Outage Compensation banked the length of a connector outage on a member's purchase — one event per member, saying when they feel the extra time.
When this fires
A connector outage that lasted an hour or more ended because the connector recovered or was replaced, and the project's Outage Compensation setting is on. Every purchase that grants access right now and unlocks a place on that connector has the outage's length banked, and this event fires once for each of them.
applies_at says when the member feels it:
now— a one-time or lifetime-style purchase with a fixed end.ends_athas already moved later byextended_seconds.membership_end— a recurring plan. No gateway lets a renewal move by a few hours, so the time is banked instead: the member's access always runsbanked_secondspast the period they last paid for, and they receive the time when the membership ends, whether they cancel, lapse or a renewal fails. Their renewal date and charges do not change.
banked_seconds is the purchase's running total across every outage it lived through; extended_seconds is what this outage added. The member is told in the chat their connector binds to them and by email; the same fact shows on their portal card and in the bot.
Required ability
project-member:view — token must carry this at mint time to subscribe an endpoint to this event.
Payload
{
"id": "evt_01HX...",
"type": "member.access_extended",
"created_at": "2026-09-13T13:21:00Z",
"api_version": "2026-05-01",
"project_id": "7f3d1c92-8b45-4e6a-9d21-5c8e0a4b6f13",
"data": {
"applies_at": "membership_end",
"banked_seconds": 11700,
"connector": "telegram",
"ends_at": "2026-10-13T13:20:00Z",
"extended_seconds": 11700,
"outage_id": "9c1e4d2a-7b3f-4e8a-a2d1-5f6b7c8d9e0f",
"project_id": "7f3d1c92-8b45-4e6a-9d21-5c8e0a4b6f13",
"subscriber_id": "2a91c4e7-6f38-4b52-8e0d-9c1a7b3f5d80",
"subscription_id": "5b7e2d40-1a86-4c39-97f2-e83d0b16c5a4"
}
}Field reference
| Field | Type | Notes |
|---|---|---|
id | string ULID | Unique event id, prefixed evt_. Use for idempotent processing. |
type | string | Always member.access_extended for this event. |
created_at | ISO 8601 timestamp | Server-side emission time. |
api_version | string | Webhook API contract version. |
project_id | string UUID | Project this event belongs to. |
data.applies_at | string | now for a fixed-term purchase whose end moved, membership_end for a recurring plan. |
data.banked_seconds | integer | The purchase's running total of banked outage time, after this outage. Also compensation_seconds on the subscription object. |
data.connector | string | The connector that was refused. |
data.ends_at | ISO 8601 timestamp | The purchase's end after the addition; for a recurring plan it already includes the banked time. |
data.extended_seconds | integer | What this outage added, its length in seconds. |
data.outage_id | string UUID | The outage row, the same id connector.outage_opened and connector.outage_closed carried. |
data.project_id | string UUID | Mirrors top-level project_id. |
data.subscriber_id | string UUID | The member. |
data.subscription_id | string UUID | The purchase. |
Caveats
- Passes and series are never extended: a dated window cannot move, so no event fires for them.
- Perk-only plans are not affected by an outage and receive nothing.
- A project that switched Outage Compensation off, an outage shorter than an hour, or one that ended with an uninstall, fires no
member.access_extendedat all;connector.outage_compensatedstill fires withmembers_extended: 0.
Related events
connector.outage_compensated— the one-line settlement summary that follows these.connector.outage_closed— the outage this compensates.- Member events overview — back to family overview.
How is this guide?