Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Azure Service Bus exposes REST APIs for messaging and resource management. You can also use supported client libraries for your application language. Choose the interface for the operations your application needs.
Messaging over HTTPS
The Service Bus runtime REST reference describes operations against a namespace endpoint such as https://your-namespace.servicebus.windows.net.
The messaging operations include:
- Send a message to a queue or topic.
- Send a batch of messages.
- Receive and delete a message.
- Receive and lock a message.
- Unlock, complete, or renew the lock on a received message.
Use Microsoft Entra ID authentication or shared access signatures to authorize requests. The HTTP message format describes message properties and body handling.
Supported client libraries
Supported Service Bus client libraries use AMQP 1.0 and expose language-specific APIs for messaging. Start with the queue quickstart for your language:
| Language | Quickstart |
|---|---|
| .NET | Send and receive messages with .NET |
| Java | Send and receive messages with Java |
| JavaScript | Send and receive messages with JavaScript |
| Python | Send and receive messages with Python |
| Go | Send and receive messages with Go |
Check the chosen API's reference for the features your application needs, such as sessions, dead-lettering, and message deferral. Use the REST operation reference to establish HTTP coverage rather than assuming that every client-library operation has an equivalent REST operation.
Note
The WindowsAzure.ServiceBus .NET library retired on September 30, 2026. For new .NET applications, use Azure.Messaging.ServiceBus. For existing applications, see the .NET migration guide.
Resource management and API versions
Use the Resource Manager REST reference for operations on Azure resources such as namespace creation and configuration. Use namespace addressing for entity operations against the Service Bus service endpoint.
Follow the version requirements in the reference for the specific API you call. Resource Manager operations have their own API versions. A historical Service Bus service-version list isn't a version-selection guide for Resource Manager or current client libraries.
Classic Azure Service Manager and RDFE management APIs retired on November 1, 2021. Use the migration guidance for existing integrations.