Azure Service Bus: Namespaces
Azure Service Bus client
Fork copies the collection into your workspace, without the publisher's secrets, so you can add your own key and send requests. Star saves it to your starred APIs (Account › Marketplace) and helps others find it.
Overview
Azure Service Bus client
Endpoints 6
Namespaces
- GETNamespaces_List
/subscriptions/:subscriptionId/providers/Microsoft.ServiceBus/namespacesGets all the available namespaces within the subscription, irrespective of the resource groups. - GETNamespaces_ListByResourceGroup
/subscriptions/:subscriptionId/resourceGroups/:resourceGroupName/providers/Microsoft.ServiceBus/namespacesGets the available namespaces within a resource group. - GETNamespaces_Get
/subscriptions/:subscriptionId/resourceGroups/:resourceGroupName/providers/Microsoft.ServiceBus/namespaces/:namespaceNameGets a description for the specified namespace. - PUTNamespaces_CreateOrUpdate
/subscriptions/:subscriptionId/resourceGroups/:resourceGroupName/providers/Microsoft.ServiceBus/namespaces/:namespaceNameCreates or updates a service namespace. Once created, this namespace's resource manifest is immutable. This operation is idempotent. - DELETENamespaces_Delete
/subscriptions/:subscriptionId/resourceGroups/:resourceGroupName/providers/Microsoft.ServiceBus/namespaces/:namespaceNameDeletes an existing namespace. This operation also removes all associated resources under the namespace. - PATCHNamespaces_Update
/subscriptions/:subscriptionId/resourceGroups/:resourceGroupName/providers/Microsoft.ServiceBus/namespaces/:namespaceNameUpdates a service namespace. Once created, this namespace's resource manifest is immutable. This operation is idempotent.
API details
- Base URL
https://management.azure.com- Authentication
- OAuth 2.0 (implicit flow) with 1 scope
- Operations
- 6 operations on 3 pathsGET 3PUT 1PATCH 1DELETE 1
- Main resources
- Namespaces 6
- Response formats
application/json- Description format
- Swagger 2.0, API version
2017-04-01 - Links
- OpenAPI document
How to test the Azure Service Bus: Namespaces in Swastik Codes
- Open the APISelect “Fork & run in Swastik Codes” on this page. Sign in or create a free account if asked.
- Fork it into your workspaceChoose a workspace. You get your own copy of the Azure Service Bus: Namespaces collection, without the publisher's secrets.
- Add your credentialsThis API uses OAuth 2.0 (implicit flow) with 1 scope. Add yours in the collection's variables or an environment; the requests already reference it.
- Send a requestPick an endpoint, for example “Namespaces_List” (GET /subscriptions/:subscriptionId/providers/Microsoft.ServiceBus/namespaces), and press Send. Check the response, add tests and run the whole collection with the runner.
Frequently asked questions
What is the Azure Service Bus: Namespaces?
Azure Service Bus client It is listed under Developer tools and has 6 endpoints.
Who publishes the Azure Service Bus: Namespaces?
It is listed from Microsoft Azure's public API description (an OpenAPI document), not published by Microsoft Azure on Swastik Codes. Anyone who controls azure.com can claim the profile by adding a DNS TXT record.
What is the base URL of the Azure Service Bus: Namespaces?
Requests go to https://management.azure.com. Endpoint paths are added to this base URL.
How do I authenticate with the Azure Service Bus: Namespaces?
With OAuth 2.0 (implicit flow) with 1 scope.
How many endpoints does the Azure Service Bus: Namespaces have?
6 operations on 3 paths (3 GET, 1 PUT, 1 PATCH, 1 DELETE). The largest groups are Namespaces.
Is forking the Azure Service Bus: Namespaces free?
Yes. Forking copies the collection into your workspace for free. It has been starred 0 times and forked 0 times.