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.
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.
Ability to subscribe
A token needs this to subscribe an endpoint to the event.
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.
Payload
JSONWhat Subscriby posts to your endpointapplication/json
The signed JSON envelope posted to your endpoint.
The envelope every event is delivered in.
Responses
2XXAny success status
Your endpoint acknowledged the delivery. Any 2xx status within 30 seconds marks it delivered; the response body is ignored.
defaultAny other status
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.
How is this guide?
Last updated on