Skip to main content
One dialog creates the subscription: the delivery type first, then the target it writes to, then the event filter.
1

Choose a delivery type

On the listing, click New subscription.The subscription type optionsThe type decides which target fields the rest of the dialog asks for, and it is fixed once the subscription exists — editing a subscription later cannot turn a queue into a webhook.
Back returns to this list and rebuilds the form from scratch. Everything typed into it, including the event filter, is discarded.
2

Name it and point it at the target

The Name is yours — it identifies the subscription in Studio and nothing else.WebhookName and endpoint for a webhook subscriptionThe HTTPS endpoint must start with https://. Every event delivery request carries a webhook-signature header you verify with the signing secret — see Signing secrets.Azure Storage Queue and Azure Service BusConnection string and entity name for an Azure Service Bus subscriptionThe connection string is stored by Occtoo and never shown again — afterwards only the derived queue or entity URL comes back. If the connection string carries an EntityPath=, it has to name the same entity you typed, and the dialog blocks the mismatch before it reaches the API.
3

Choose the events

Pick at least one event type, and optionally narrow it with conditions. See Build the event filter.
4

Create it

Click Create subscription.A Webhook shows its signing secret once, then opens in Pending verification — no events are delivered until the endpoint is verified. A queue subscription has no secret and no verification step: Studio opens it straight away.
A subscription only receives events published after it starts delivering. Nothing from before that point is replayed, so a consumer that needs history has to read it from the Events API instead.