Azure Communication Chat Service
cloud:azure-communication-chat · learn.microsoft.com/rest/api/azure/ ↗
Azure Communication Chat Service
About the Azure Communication Chat Service API
Azure Communication Chat Service API on Apizie: 16 endpoints (Gets chat message read receipts for a thread., Sends a read receipt event to a thread, on behalf of a user., Gets a list of messages from a thread., Sends a message to a thread., …) returned as clean JSON through one API key. Send your own provider key in the x-upstream-key header. Call it over REST at https://zieapi.vercel.app/v1/cloud:azure-communication-chat/{endpoint} or from Claude, ChatGPT and Cursor through the Apizie MCP server. Free plan: 1,000 requests a month.
| Project key | cloud:azure-communication-chat |
|---|---|
| Status | Your key |
| Endpoints | 16 |
| Category | Cloud |
| Source | learn.microsoft.com/rest/api/azure/ |
| Base URL | https://zieapi.vercel.app/v1/cloud:azure-communication-chat/{endpoint} |
| For AI tools | OpenAPI spec · Markdown (what is this?) |
Azure Communication Chat Service API FAQ
How do I call the Azure Communication Chat Service API?
Create a free Apizie key, then send GET https://zieapi.vercel.app/v1/cloud:azure-communication-chat/chat-thread-list-chat-read-receipts with the header x-api-key. Every endpoint returns { project, data, timestamp }.
Is the Azure Communication Chat Service API free on Apizie?
Yes. The Free plan includes 1,000 requests a month at 100 requests a minute, no credit card. Azure Communication Chat Service itself also needs your own key from azure.com.
Can AI agents use the Azure Communication Chat Service API?
Yes. Add the Apizie MCP server (https://zieapi.vercel.app/mcp) to Claude, ChatGPT, Cursor or VS Code, then ask in plain language. The agent calls run_scraper with project key cloud:azure-communication-chat.
What is the status of the Azure Communication Chat Service API?
Needs your own provider key (bring your own key)