Microsoft Azure APIs

237 APIs4,900 Endpoints17 Categories

API Catalog(4 of 237)

Azure Bot Service

The Azure Bot Service control-plane API provisions and manages bot resources, channels, connections, and enterprise channel infrastructure. It exposes 27 endpoints for creating Microsoft.BotService/botServices resources, registering channels such as Teams, Slack, Webchat, and Email, and configuring OAuth bot connections to third-party identity providers. It also covers enterprise channels for high-scale deployments and name-availability checks needed during onboarding.

27 endpoints

EngagementFabric

Jentic publishes the only available OpenAPI specification for EngagementFabric, keeping it validated and agent-ready. Microsoft Customer EngagementFabric is the resource provider that hosts engagement accounts and the channels (SMS, email, chat, social) that route customer-facing messages. The API exposes 16 endpoints covering account CRUD, channel CRUD, channel-type discovery, account key listing and rotation, and resource name availability checks. Use it where existing EngagementFabric accounts still drive messaging flows.

16 endpoints

NotificationHubsManagementClient

Jentic publishes the only available OpenAPI specification for NotificationHubsManagementClient, keeping it validated and agent-ready. The Azure Notification Hubs management API exposes 28 operations for provisioning notification hub namespaces, individual hubs, authorization rules, and platform-specific PNS credentials (APNS, GCM/FCM, WNS, MPNS, Baidu, ADM). Use it to set up the infrastructure that delivers cross-platform push notifications to mobile and desktop apps at scale, and to rotate the shared access keys that client SDKs use to register devices and send notifications.

28 endpoints

SignalRManagementClient

Jentic publishes the only available OpenAPI specification for SignalRManagementClient, keeping it validated and agent-ready. The Azure SignalR Service management API exposes the Microsoft.SignalRService resource provider so agents can provision SignalR resources, switch SKUs and unit counts, restart instances, list and rotate access keys, and check name availability and per-region usage. SignalR Service powers real-time WebSocket and long-poll messaging for ASP.NET Core SignalR and serverless event push scenarios — this API manages the resource itself, not the runtime hub messages.

12 endpoints

Connect Your Agent

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.