Microsoft Azure SignalRManagementClient

Name: SignalRManagementClient API
Brand: SignalR Management
Availability: InStock

★ Only Publicly Available OpenAPI DocumentCommunicationsChat Messagingoauth212 Endpoints

Install Jentic One Beta

Connect the SignalRManagementClient to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the SignalRManagementClient, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

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.

Capabilities

What an agent can do with SignalRManagementClient API.

Provision a SignalR Service resource with a chosen SKU tier and unit count

Scale a SignalR resource up or down by changing units or SKU

Restart a SignalR resource without recreating it

GET STARTED

Start building with SignalRManagementClient API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use SignalRManagementClient API for, with concrete tasks.

★ Real-time Backend Provisioning

Application teams provision Azure SignalR Service as the WebSocket backend for chat, dashboards, and collaborative tools. The signalR resource endpoint accepts the SKU (Free or Standard), unit count, and feature flags, so an agent can provision and tune the service to match expected concurrent connections without using the Azure portal.

PUT /.../signalR/{resourceName} with sku.name Standard_S1, sku.capacity 5, and location westeurope

Access Key Rotation

Security teams rotate SignalR access keys regularly to limit blast radius if a connection string leaks. The regenerateKey endpoint regenerates either the primary or secondary key in place and the listKeys endpoint returns the new connection strings, so an agent can update dependent clients and a secrets vault in one flow.

POST /.../signalR/{resourceName}/regenerateKey with keyType Primary, then call listKeys and store the new primaryConnectionString in the secrets manager

Capacity Scaling for Events

Engineering teams scale SignalR units ahead of a traffic spike like a product launch or live event. PATCH-ing the resource to a higher sku.capacity adds capacity without dropping existing connections, and the same call dropped back down after the event keeps cost in check, all driven by an agent rather than a manual portal change.

PATCH /.../signalR/{resourceName} setting sku.capacity to 10 ahead of the event, then back to 5 once it ends

AI Agent Realtime Setup

An agent built on Jentic stands up a SignalR backend for a developer who asks for real-time updates in their app. The agent checks name availability, provisions the resource, returns the connection string from listKeys, and reports the chosen SKU and capacity - without the developer touching the Azure portal.

Search Jentic for create azure signalr resource, load the schema, PUT the resource, and call listKeys to return the connection string

Key Endpoints

12 endpoints — jentic publishes the only available openapi specification for signalrmanagementclient, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

PUT

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.SignalRService/signalR/{resourceName}

Create or update a SignalR resource

PATCH

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.SignalRService/signalR/{resourceName}

Update SKU, capacity, or settings on an existing SignalR resource

POST

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.SignalRService/SignalR/{resourceName}/listKeys

List SignalR primary and secondary access keys

POST

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.SignalRService/SignalR/{resourceName}/regenerateKey

Regenerate primary or secondary access key

POST

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.SignalRService/signalR/{resourceName}/restart

Restart a SignalR resource

POST

/subscriptions/{subscriptionId}/providers/Microsoft.SignalRService/locations/{location}/checkNameAvailability

Check whether a SignalR resource name is available in a region

PUT

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.SignalRService/signalR/{resourceName}

Create or update a SignalR resource

PATCH

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.SignalRService/signalR/{resourceName}

Update SKU, capacity, or settings on an existing SignalR resource

POST

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.SignalRService/SignalR/{resourceName}/listKeys

List SignalR primary and secondary access keys

POST

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.SignalRService/SignalR/{resourceName}/regenerateKey

Regenerate primary or secondary access key

POST

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Your Azure AD service principal credential is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context, and neither do the connection strings returned by listKeys.

Intent-based discovery

Agents search Jentic by intent such as 'create an Azure SignalR resource' or 'scale SignalR units', and Jentic returns the matching Microsoft.SignalRService operation with its input schema so the agent calls the right endpoint without reading the ARM reference.

Time to first call

FAQs

Specific to using SignalRManagementClient API through Jentic.

Why is there no official OpenAPI spec for SignalRManagementClient?

Microsoft Azure does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call SignalRManagementClient via structured tooling. It is validated against the live API and kept up to date. Get started with Jentic One, the self-hosted execution layer.

What authentication does the SignalR management API use?

It uses Azure AD OAuth 2.0 with the implicit flow against https://login.microsoftonline.com/common/oauth2/authorize and the user_impersonation scope. When called through Jentic, your AAD service principal credentials live in your Jentic One instance and only short-lived bearer tokens reach the agent.

Can I send hub messages with this API?

No - this is the management control plane. To send messages to clients you use the SignalR Service REST API (data plane) or an ASP.NET Core SignalR Hub backed by the service. Use this API to provision the resource, then use the data plane endpoints scoped to <resourceName>.service.signalr.net for messaging.

How do I rotate a SignalR access key?

POST to /subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.SignalRService/SignalR/{resourceName}/regenerateKey with keyType set to Primary or Secondary, then call listKeys at the same resource path to retrieve the new connection strings.

What are the rate limits for this API?

Azure Resource Manager throttles around 12,000 reads and 1,200 writes per hour per principal at subscription scope, surfaced via x-ms-ratelimit-remaining-subscription-reads and x-ms-ratelimit-remaining-subscription-writes headers. Provisioning a SignalR resource is async - the 202 response contains an asyncOperation URL to poll.

How do I scale a SignalR resource through Jentic?

Search Jentic for scale azure signalr units, load the schema for PATCH /.../signalR/{resourceName}, and execute it with sku.capacity set to the new unit count. Active connections are preserved during the scaling operation. The Jentic Python SDK ships the search, load, execute pattern after pip install jentic.

Is there a free SKU for SignalR?

Yes - the Free_F1 SKU is supported by this API and provides 20 concurrent connections and 20,000 messages per day. Use Standard_S1 with sku.capacity for production workloads where you need more connections and SLA coverage.

Can I limit what my agent is allowed to do with the Microsoft Azure SignalR API?

Yes. Because you self-host Jentic One, your own rules decide which SignalR operations the agent may call and which Azure AD service principal credential it uses, so you can grant read-only actions like listKeys, checkNameAvailability, and usages while withholding destructive ones such as regenerateKey or deleting a resource. Since the subscription, resource group, and resource name sit in the URL path (/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.SignalRService/signalR/{resourceName}), you can pin the agent to a single SignalR resource. The credential stays in your instance and is injected only at execution time, so it never reaches the agent's prompt or logs.

Microsoft Azure SignalRManagementClient

Connect the SignalRManagementClient to your agent

Capabilities

Start building with SignalRManagementClient API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs