Alert Destinations API

Your destinations, primary first.

• kind is connector_identity or email (push_device is reserved for the creator apps).
• target is the connector account's id for connector_identity, the same value GET /v1/me/identities returns as the account behind a linked identity, or the email address for email.
• classes lists the alert classes routed here, is null for every class, or is [] for none (the account is kept but receives nothing).
• is_primary marks the destination of your primary connected account. It is derived from your linked identities, never set through this API.

Until you write a destination, you are on the default: every class of alert goes to your primary connected account, and the critical classes go to your email as well. The list is empty while the default applies, and the dashboard grid shows the default as every cell ticked on that account. Linking a primary account writes the default down as rows and adds the new account to them, so from then on the rows lead.

Critical classes always reach your email. Recovery, billing and security alerts are sent to your email whatever the destinations say, because they arrive when the connector you would otherwise read them on may have just failed. Routing them to a connected account adds a message there; it never removes the email.

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": "[email protected]", "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.