---
title: "Get a recovery's roll call"
method: GET
path: "/v1/recovery/operations/{operation}/roll-call"
tags: ["Disaster Recovery"]
---

# Get a recovery's roll call

`GET /v1/recovery/operations/{operation}/roll-call`

## Request

- Base URL: `https://api.subscriby.net`
- URL: `https://api.subscriby.net/v1/recovery/operations/{operation}/roll-call`
- Auth: HTTP bearer

```bash
curl https://api.subscriby.net/v1/recovery/operations/$OPERATION_ID/roll-call \
  -H "Authorization: Bearer $SUBSCRIBY_TOKEN"
```

Where the re-admission after a channel recovery stands, read live.

- `total` is how many members the swap set out to re-admit; `regranted` how many hold a fresh link into the new chat; `failed` how many could not be given one.
- `unreachable` is how many the bot could not message, and `emailed` how many of those were told by email instead (at the per-email fee, when the project opted in).
- `joined` is stamped the moment the platform approves a member's join request, so `pending` (`regranted − joined`) is who is still outside.
- `settled` means the queue has handled everyone, so the counters will not move on their own. `can_nudge` is true when somebody is still outside and the reminder cooldown has passed; `cooling_down` and `nudge_available_at` explain a `false`.

A recovery of a kind that re-admits nobody (an account relink, a bot replacement) answers the same shape with every counter at zero rather than an error.

## Path parameters

- `operation` string, uuid, required

## Response `200`

200 with the counters.

- object
  - `data` ReadmissionRollCallResource, required: Where the re-admission after a channel recovery stands: how many members were given a fresh link, how many have come back, and whether a reminder can go out.
    - `total` integer, required: How many members the swap set out to re-admit.
    - `regranted` integer, required: How many hold a fresh link into the new chat.
    - `failed` integer, required: How many could not be given one.
    - `unreachable` integer, required: How many the bot could not message.
    - `emailed` integer, required: How many of the unreachable were told by email instead, at the per-email fee, when the project opted in.
    - `joined` integer, required: How many the platform has approved into the new chat; stamped the moment a join request is approved.
    - `pending` integer, required: Who is still outside: `regranted` minus `joined`.
    - `nudged` integer, required: How many reminders have gone out so far.
    - `settled` boolean, required: True once the queue has handled everyone, so the counters will not move on their own.
    - `cooling_down` boolean, required: True while the reminder cooldown has not passed since the last nudge.
    - `can_nudge` boolean, required: True when somebody is still outside and the cooldown has passed; `cooling_down` and `nudge_available_at` explain a false.
    - `last_nudged_at` string, nullable, required: When the last reminder went out, ISO 8601; null if none has.
    - `nudge_available_at` string, nullable, required: When the next reminder may go out, ISO 8601; null when one may go out now or nobody is waiting.

## Other responses

- `401`: `AUTHENTICATION_REQUIRED`: the request carries no bearer token, or one that is revoked, malformed, or minted for another environment (an `sbt_test_` token on production).
- `403`: `TOKEN_MISSING_ABILITY`: the token is valid but does not carry the ability this endpoint requires; `error.context.required_ability` names the one to grant. An endpoint that also checks who owns a row or which tier the account is on answers `FORBIDDEN`, `TEAM_TIER_REQUIRED` or `CONNECTOR_TIER_REQUIRED` with the same status, and says so in its own description.
- `404`: `RESOURCE_NOT_FOUND`: an id in the path names nothing the token can see. `TENANT_MISMATCH`: the project sits outside the token's `scope:project:` allow-list, or the token carries no team scope. Both answer 404 rather than 403 so that existence outside the token's scope cannot be inferred.
- `429`: `RATE_LIMITED`: the token has spent its 300 requests a minute or 10,000 an hour; `Retry-After` says when the next one is accepted.

---

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