Microsoft Azure AzureDigitalTwinsManagementClient

Name: AzureDigitalTwinsManagementClient API
Brand: AzureDigitalTwinsManagementClient
Availability: InStock

★ Only Publicly Available OpenAPI DocumentIOTDevice Managementoauth216 Endpoints

Install Jentic One Beta

Connect the AzureDigitalTwinsManagementClient to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the AzureDigitalTwinsManagementClient, 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 AzureDigitalTwinsManagementClient API.

Provision and delete DigitalTwinsInstance resources scoped to a resource group

Check name availability for a new DigitalTwinsInstance in a region before creating it

Attach Event Grid, Event Hubs, or Service Bus endpoints to a twin instance for change notifications

GET STARTED

Start building with AzureDigitalTwinsManagementClient API

Explore with Jentic

View OpenAPI Document

For Agents

Provision Azure Digital Twins instances, configure their event endpoints, and link IoT Hub integration resources for twin graph telemetry.

Use for: I need to provision a new Azure Digital Twins instance in West Europe, Check whether a digital twin name is available in a given region, List all DigitalTwinsInstance resources in my subscription, Attach an Event Hub endpoint to a digital twin for telemetry forwarding

Not supported: Does not run twin queries, upload twin models, or ingest device telemetry — use for DigitalTwinsInstance provisioning and endpoint wiring only.

Jentic publishes the only available OpenAPI specification for AzureDigitalTwinsManagementClient, keeping it validated and agent-ready. The Azure Digital Twins management API provisions DigitalTwinsInstance resources, attaches event endpoints (Event Grid, Event Hubs, Service Bus), and links integration resources such as IoT Hubs to a twin graph. It is the control plane for setting up the modelling environment in which a digital twin of a physical environment lives, distinct from the data plane that runs queries against twins.

Use Cases

Patterns agents use AzureDigitalTwinsManagementClient API for, with concrete tasks.

★ Stand up a new Digital Twins environment

Solution architects use this API to bootstrap a Digital Twins instance for a smart-building or factory project. They call CheckNameAvailability, then PUT on /digitalTwinsInstances/{resourceName} to create the instance, and finally attach an Event Grid endpoint so downstream services receive twin change events. This is faster and more reproducible than clicking through the Azure portal.

Call DigitalTwins_CheckNameAvailability for 'factory-twin-eu', then DigitalTwins_CreateOrUpdate in resource group iot-rg, then DigitalTwinsEndpoint_CreateOrUpdate to attach an Event Grid endpoint

Wire IoT Hubs into a twin graph

Operations engineers connect existing IoT Hubs to a Digital Twins instance so device telemetry flows into the twin model. The API exposes IoTHub_CreateOrUpdate under the integrationResources path, letting agents declare the IoT Hub by ARM ID and receive a managed integration resource that the twin uses to ingest events.

Use IoTHub_CreateOrUpdate to attach a specific IoT Hub ARM resource ID to a DigitalTwinsInstance

Lifecycle management at scale

Platform teams that run many short-lived twin environments use this API to enumerate, tag, and tear down DigitalTwinsInstance resources by subscription. DigitalTwins_List walks every twin in a subscription, DigitalTwins_Update changes tags, and DigitalTwins_Delete removes the instance plus its endpoints in a single asynchronous operation.

Enumerate every DigitalTwinsInstance in a subscription, filter by tag environment=dev, and call DigitalTwins_Delete on each match

AI agent integration via Jentic

An IoT operations agent uses Jentic to provision and tear down twin environments without learning ARM. The agent searches Jentic for 'create an Azure Digital Twins instance', loads the DigitalTwins_CreateOrUpdate schema, and executes with structured input. Jentic mints the AAD token in the background, so the agent never holds a Microsoft Graph or ARM bearer token.

Through Jentic, search 'provision a digital twins instance', load the schema, and execute DigitalTwins_CreateOrUpdate for a new factory environment

Key Endpoints

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

METHOD

PATH

DESCRIPTION

PUT

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.DigitalTwins/digitalTwinsInstances/{resourceName}

Create or update a Digital Twins instance

DELETE

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.DigitalTwins/digitalTwinsInstances/{resourceName}

Delete a Digital Twins instance

POST

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

Check whether a Digital Twins instance name is available

PUT

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.DigitalTwins/digitalTwinsInstances/{resourceName}/endpoints/{endpointName}

Create or update an event endpoint on a twin

PUT

/{scope}/providers/Microsoft.DigitalTwins/integrationResources/{integrationResourceName}

Attach or update an IoT Hub integration resource

PUT

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.DigitalTwins/digitalTwinsInstances/{resourceName}

Create or update a Digital Twins instance

DELETE

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.DigitalTwins/digitalTwinsInstances/{resourceName}

Delete a Digital Twins instance

POST

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

Check whether a Digital Twins instance name is available

PUT

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.DigitalTwins/digitalTwinsInstances/{resourceName}/endpoints/{endpointName}

Create or update an event endpoint on a twin

Why Jentic?

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

Credential isolation

Azure AD OAuth 2.0 tokens are minted and rotated inside the Jentic vault. Agents receive scoped, short-lived tokens for management.azure.com — client secrets never enter agent context.

Intent-based discovery

Agents search Jentic by intent, e.g. 'provision an Azure Digital Twins instance', and Jentic returns DigitalTwins_CreateOrUpdate with its input schema so the agent calls the right endpoint without browsing ARM docs.

Time to first call

Direct integration: 1-3 days for AAD auth and ARM polling. Through Jentic: under 1 hour — search, load schema, execute.

FAQs

Specific to using AzureDigitalTwinsManagementClient API through Jentic.

Why is there no official OpenAPI spec for AzureDigitalTwinsManagementClient?

Microsoft Azure does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call AzureDigitalTwinsManagementClient via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.

What authentication does the AzureDigitalTwinsManagementClient API use?

The API uses Azure Active Directory OAuth 2.0 declared as azure_auth with the implicit flow. Tokens are presented as Bearer tokens against management.azure.com. Jentic stores the AAD client secret in its vault and mints scoped tokens for each call so the agent never sees the raw credential.

Can I run twin queries with this API?

No. This is the management plane only — it provisions DigitalTwinsInstance resources and configures their endpoints and integrations. Twin model uploads, twin queries, and relationship traversal happen on the data plane API of each instance.

What are the rate limits for the AzureDigitalTwinsManagementClient API?

Azure Resource Manager applies subscription-level throttling — typically 12,000 read and 1,200 write requests per hour, surfaced via x-ms-ratelimit-remaining headers. The Digital Twins management API does not document additional limits beyond ARM.

How do I provision a Digital Twins instance through Jentic?

Run pip install jentic, then use the async client to search 'provision an Azure Digital Twins instance', load the DigitalTwins_CreateOrUpdate operation, and execute with subscriptionId, resourceGroupName, and a body specifying location and tags. Jentic returns the resource details once the deployment completes.

Can I attach multiple endpoints to a single DigitalTwinsInstance?

Yes. Each endpoint is a child resource at /digitalTwinsInstances/{resourceName}/endpoints/{endpointName}. List existing endpoints with DigitalTwinsEndpoint_List and create more with DigitalTwinsEndpoint_CreateOrUpdate, choosing Event Grid, Event Hubs, or Service Bus per endpoint.

Microsoft Azure AzureDigitalTwinsManagementClient

Connect the AzureDigitalTwinsManagementClient to your agent

Capabilities

Start building with AzureDigitalTwinsManagementClient API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs