Overview
Client-mode REST API connector for the Azure Service Bus runtime REST API: send to queues and topics plus peek-lock and receive-and-delete and complete and unlock.BASE_ADDRESS defaults to https://YOUR_NAMESPACE.servicebus.windows.net. Topics use cloud/azure-service-bus/<object>/<verb>.
Authentication
Authorization: {value.json.authorization} carries either “SharedAccessSignature sr=…&sig=…&se=…&skn=…” (SAS from a policy with Send / Listen) or “Bearer <Entra token>” (scope https://servicebus.azure.net/.default; roles Azure Service Bus Data Sender / Receiver). The connector cannot sign; generate the SAS or token upstream (LoT action with GET SECRET or an external helper).Notes
- Topic names here use cloud/azure-service-bus/… (not messaging/…).
- BrokerProperties is a JSON string header, e.g. {“MessageId”:“m-1”,“SessionId”:“line-1”,“TimeToLive”:3600}; pass ”{}” when unused.
- Peek-lock returns the lock token in the BrokerProperties response header; MessageComplete and MessageUnlock need messageId and lockToken from it.
Basic Syntax
Sources
- https://learn.microsoft.com/en-us/rest/api/servicebus/send-message-to-queue
- https://learn.microsoft.com/en-us/rest/api/servicebus/peek-lock-message-non-destructive-read
- https://learn.microsoft.com/en-us/rest/api/servicebus/receive-and-delete-message-destructive-read
- https://learn.microsoft.com/en-us/rest/api/servicebus/delete-message
- https://learn.microsoft.com/en-us/rest/api/servicebus/unlock-message
- https://learn.microsoft.com/en-us/azure/service-bus-messaging/service-bus-sas

