---
title: "A closed connector outage settled: how many members had time banked, how much each received, and how many invites lost during the outage were re-sent."
method: POST
path: "connector.outage_compensated"
tags: ["connector.* events"]
---

# A closed connector outage settled: how many members had time banked, how much each received, and how many invites lost during the outage were re-sent.

`POST connector.outage_compensated` (webhook)

### When this fires

Once per outage, shortly after `connector.outage_closed`. The settlement runs from the queue: it first re-sends any invite that never reached a member while the connector was refusing the installation (`grants_replayed`), then, when the outage lasted an hour or more, ended as `recovered` or `replaced`, and the project's **Outage Compensation** setting is on, banks the outage's length on every live purchase that unlocks a place on that connector (`members_extended`, one `member.access_extended` each). The creator receives the same summary by email, on their connected account and in the notification centre; it is also the **Compensation** column of the Recovery History page.

### Caveats

- Fires with `members_extended: 0` when the outage was shorter than an hour, ended with an uninstall, or the project switched Outage Compensation off; the creator is not emailed in that case.
- Money never moves: no charge, refund or renewal date changes. Recurring members receive the time at the end of their membership.

### Related events

- `member.access_extended`: one per compensated member.
- `connector.outage_closed`: the outage this settles.

## 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` 'connector.outage_compensated', required: The event name, always `connector.outage_compensated` 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.
    - `connector` string, required: The connector that was refused.
    - `extended_seconds` integer, required: The seconds each compensated member received; `0` when nobody was.
    - `grants_replayed` integer, required: How many purchases had their invites re-sent because none reached the member during the outage.
    - `members_extended` integer, required: How many members had the time banked.
    - `outage_id` string, uuid, required: The outage row, the same id the opened and closed events carried.
    - `project_id` string, uuid, required: Mirrors top-level `project_id`.

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