Replace your alert destinations

Takes the complete list you want to keep; anything not in it is removed. Each entry names a kind, a target and optional classes:

curl -X PUT https://api.subscriby.net/v1/me/alert-destinations \
  -H "Authorization: Bearer $SUBSCRIBY_TOKEN" \
  -H "Idempotency-Key: $(uuidgen)" \
  -H "Content-Type: application/json" \
  -d '{
    "destinations": [
      { "kind": "connector_identity", "target": "0c2d8a7e-4b1f-4d3e-9a6b-2f5e8c1d7a90", "classes": ["sales", "support", "passes"] },
      { "kind": "email", "target": "ada@example.com", "classes": null }
    ]
  }'

The response is the resulting list. PUT is a replacement, not a patch: send an empty destinations list to remove every row and return to the default. is_primary in the payload is ignored; the service derives it from your linked identities.

When a creator alert is sent, every connected account routed to its class receives a message through that connector, and email is used when an email destination routes the class, when no connected account does, or when the class is critical. The same routing decides whether the bot messages you at all about a sale, a waiting member or a pass window: a class you route away from an account is never sent there. A newly linked primary account receives a destination for every class automatically, so linking keeps working as it did; unlinking the account removes its destination.