Disaster Recovery

Tell members about a bot replacement

curl -X POST https://api.subscriby.net/v1/recovery/operations/$OPERATION_ID/notify-members \
  -H "Authorization: Bearer $SUBSCRIBY_TOKEN" \
  -H "Idempotency-Key: $(uuidgen)"

After a bot replacement, emails every member the project can reach by email that its bot changed, with the new bot's link and the portal, at the per-email fee added to the creator's transaction fees. Sent once per recovery: a second call answers with the count already sent and sends nothing. Answers 200 with the count.

post/v1/recovery/operations/{operation}/notify-members

Request

  • Base URL: https://api.subscriby.net
  • URL: https://api.subscriby.net/v1/recovery/operations/{operation}/notify-members
  • Auth: HTTP bearer

Path parameters

operationstring uuid required

The operation, resolved within the ledger by the route binder.

Headers

Idempotency-Keystring uuid required

A key unique to this operation, such as a fresh UUID. The same key replays the original 2xx response for 24 hours (with Idempotent-Replay: true), so a retry after a timeout never repeats the write; the same key with a different body is refused with 409.

Response

200 with operation_id and how many members were notified, now or earlier.

Example response

{
  "data": {
    "operation_id": "9a4d2e71-5b38-4c6f-8e12-3d7c9b0a5f21",
    "notified": 327
  }
}

Changes

No recorded changes to this operation across all 1 revision of this API.