Azure Service Bus

Azure Service Bus Messages API

The Messages API from Azure Service Bus — 3 operation(s) for messages.

GitHub OpenAPI

Operations 5

Each operation below carries the questions people ask an LLM about it and the instructions they give an agent to run it. Generated by API Evangelist overlay

POST /{queuePath}/messages Send a message to a queue or topic · Service Bus Send message #
Ask an LLM
“How do I post a message onto an Azure Service Bus queue over REST?”
“Can I publish a message to a topic with the same send call I use for queues?”
Tell an agent
Send a message to the {queuePath} queue.
Publish a new message onto the topic at {queuePath}.
POST /{queuePath}/messages/head Receive and delete the next queued message · Service Bus Receive and delete #
Ask an LLM
“How do I pull the next message off a queue and remove it in one step?”
“Is there a destructive read that takes a message and deletes it right away?”
Tell an agent destructive · confirm first
Receive the next message from {queuePath} and delete it immediately.
Take the head message off queue {queuePath} without locking it, removing it as it is read.
DELETE /{queuePath}/messages/head Peek and lock the next message for processing · Service Bus Peek-lock message #
Ask an LLM
“How do I read the next message but keep it on the queue until I finish processing it?”
“Can I lock a message so no other receiver picks it up while I work on it?”
Tell an agent destructive · confirm first
Peek-lock the next message on {queuePath} so I can process it.
Lock the head message of queue {queuePath} and give me its lock token.
DELETE /{queuePath}/messages/{messageId}/{lockToken} Complete a peek-locked message · Service Bus Complete message #
Ask an LLM
“How do I mark a locked message as successfully processed so it leaves the queue?”
“Which call settles a peek-locked message once my handler succeeds?”
Tell an agent destructive · confirm first
Complete message {messageId} on {queuePath} with lock token {lockToken}.
Mark locked message {messageId} in {queuePath} as done using token {lockToken} so it is removed.
PUT /{queuePath}/messages/{messageId}/{lockToken} Renew the lock on a locked message · Service Bus Renew lock #
Ask an LLM
“How do I extend the lock on a message that is taking a long time to process?”
“Can I keep a peek-locked message from going back to the queue before I'm done?”
Tell an agent
Renew the lock on message {messageId} in {queuePath} using lock token {lockToken}.
Extend my processing lock for message {messageId} with token {lockToken} on {queuePath}.

Documentation

📖
Documentation
https://learn.microsoft.com/en-us/rest/api/servicebus/
📖
Authentication
https://learn.microsoft.com/en-us/rest/api/eventhub/authenticate-shared-access-signature

Specifications

⚙
OpenAPI
https://raw.githubusercontent.com/api-evangelist/azure-service-bus/refs/heads/main/openapi/azure-service-bus-messages-api-openapi.yml

Other Resources

🔗
Reference
https://learn.microsoft.com/en-us/rest/api/servicebus/resourceprovider

Work with this as data

Every API here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for apis

7 MCP tools reach this
  • find_apisBrowse and filter every API in the catalog.
  • get_api_artifactsOne API's artifacts, grouped by type.
  • get_openapiThe primary OpenAPI for this API.
  • find_similar_apisAPIs that look like this one.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This API 
curl "https://apis.io/api/v1/apis/azure-service-bus:microsoft-azure-service-bus-messages-api"
All apis 
curl "https://apis.io/api/v1/apis?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.

OpenAPI Specification

azure-service-bus-messages-api-openapi.yml Raw ↑ 
openapi: 3.2.0
info:
  title: Azure Service Bus REST Messages API
  description: 'Azure Service Bus REST API supports messaging operations: sending, receiving, peeking, completing, abandoning, and renewing locks on messages from queues, topics, and subscriptions.'
  version: 2017-04
servers:
- url: https://{namespace}.servicebus.windows.net
  variables:
    namespace:
      default: mynamespace
security:
- sasToken: []
tags:
- name: Messages
paths:
  /{queuePath}/messages:
    parameters:
    - name: queuePath
      in: path
      required: true
      schema:
        type: string
    post:
      operationId: sendMessage
      summary: Service Bus Send message
      description: Sends a message to a queue or topic.
      tags:
      - Messages
      requestBody:
        required: true
        content:
          application/json:
            schema:
              type: object
              additionalProperties: true
      responses:
        '201':
          description: Message sent
  /{queuePath}/messages/head:
    parameters:
    - name: queuePath
      in: path
      required: true
      schema:
        type: string
    post:
      operationId: receiveAndDelete
      summary: Service Bus Receive and delete
      description: Receives the next message from a queue and deletes it.
      tags:
      - Messages
      responses:
        '200':
          description: Message received
          content:
            application/json:
              schema:
                type: object
        '204':
          description: No message available
    delete:
      operationId: peekLockMessage
      summary: Service Bus Peek-lock message
      description: Peeks the next message and locks it for processing.
      tags:
      - Messages
      responses:
        '200':
          description: Message peeked
          content:
            application/json:
              schema:
                type: object
        '204':
          description: No message
  /{queuePath}/messages/{messageId}/{lockToken}:
    parameters:
    - name: queuePath
      in: path
      required: true
      schema:
        type: string
    - name: messageId
      in: path
      required: true
      schema:
        type: string
    - name: lockToken
      in: path
      required: true
      schema:
        type: string
    delete:
      operationId: completeMessage
      summary: Service Bus Complete message
      description: Completes a peek-locked message.
      tags:
      - Messages
      responses:
        '200':
          description: Completed
    put:
      operationId: renewLock
      summary: Service Bus Renew lock
      description: Renews the lock on a message.
      tags:
      - Messages
      responses:
        '200':
          description: Lock renewed
components:
  securitySchemes:
    sasToken:
      type: apiKey
      in: header
      name: Authorization
      description: SAS token in Authorization header
externalDocs:
  description: Azure Service Bus REST API Documentation
  url: https://learn.microsoft.com/en-us/rest/api/servicebus/
x-generated-from: https://learn.microsoft.com/en-us/rest/api/servicebus/
x-generated-by: claude-crawl-2026-05-08