Microsoft Azure IoTSpacesClient
Browse all Azure APIs44
AI ReadinessFoundational (D)44/100
Agent-ready OpenAPI document · curated by JenticIOTDevice Managementoauth28 EndpointsREST
Know of an official OpenAPI document? Contribute it →
For Agents
Provision and manage Azure IoTSpaces Graph service instances and check service name availability via Azure Resource Manager.
Use for: I need to provision a new IoTSpaces Graph service, List all IoTSpaces instances in my subscription, Check whether the name 'acme-spaces' is available for IoTSpaces, Retrieve a specific IoTSpaces instance by resource name
Not supported: Does not handle spatial graph queries, telemetry routing, or device-side data ingestion - use for IoTSpaces Graph control-plane management only.
Jentic publishes the only available OpenAPI specification for IoTSpacesClient, keeping it validated and agent-ready. The Microsoft.IoTSpaces resource provider (the predecessor of Azure Digital Twins) manages IoTSpaces Graph service instances under an Azure subscription. It exposes 8 ARM endpoints to create, update, list, and delete Graph instances, check service name availability, and enumerate provider operations.
Install Jentic One Beta
Connect the IoTSpacesClient to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the IoTSpacesClient, 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.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fazure.com%2Fiotspacesclient" | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fazure.com%2Fiotspacesclient" | sh
jentic register # connects your agent to your Jentic One instanceJentic 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 IoTSpacesClient API.
Create or update an IoTSpaces Graph service instance in a resource group
List Graph service instances across a subscription or filtered by resource group
Retrieve a single Graph instance by resource name
Check whether a candidate IoTSpaces service name is available before deploy
Enumerate Microsoft.IoTSpaces operations exposed on the subscription
Use Cases
Patterns agents use IoTSpacesClient API for, with concrete tasks.
★ Spatial Intelligence for Smart Buildings
Building operators provision an IoTSpaces Graph instance per facility to model rooms, floors, and zones, then attach sensors and devices to those nodes for spatial telemetry. The control-plane API drives the create-and-update lifecycle through ARM, so the same automation that provisions IoT Hubs can stand up a Graph instance alongside. Setup of a Graph instance is a few minutes through the API.
Check name availability for 'hq-spaces', then PUT a new IoTSpaces Graph in resource group 'rg-iot' using sku F1.
Subscription-Wide IoTSpaces Inventory
Operations teams enumerate every IoTSpaces Graph instance across a subscription to track sprawl, audit billing, and align tagging with other IoT resources. Both subscription-scoped and resource-group-scoped listings are available, so the inventory pivots cleanly by team. Inventory completes in seconds for typical fleets.
List every IoTSpaces Graph in the subscription and emit a CSV with name, resourceGroup, location, and sku.
Migration Discovery to Azure Digital Twins
Teams planning migration from IoTSpaces to its successor Azure Digital Twins start by enumerating existing IoTSpaces Graph instances and capturing their location and sku. The output drives the migration plan because each Graph instance maps to an ADT instance in the new model. Discovery typically takes minutes.
List every IoTSpaces Graph in the subscription and produce a JSON migration plan keyed by resourceName.
Agent-Driven IoTSpaces Operations via Jentic
An AI ops agent can stand up and audit IoTSpaces Graph instances through Jentic without holding raw Azure AD credentials. The agent searches Jentic for 'create an Azure IoTSpaces graph', loads the operation schema, and executes against Microsoft.IoTSpaces. Jentic's your Jentic One instance injects a scoped bearer token for management.azure.com.
Use the Jentic MCP tool azure_iotspaces_create_graph to provision IoTSpaces Graph 'demo-spaces' in resource group 'rg-iot'.
Key Endpoints
8 endpoints — jentic publishes the only available openapi specification for iotspacesclient, keeping it validated and agent-ready.
METHOD
PATH
DESCRIPTION
GET
/subscriptions/{subscriptionId}/providers/Microsoft.IoTSpaces/Graph
List IoTSpaces Graph instances in the subscription
GET
/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.IoTSpaces/Graph
List IoTSpaces Graph instances in a resource group
PUT
/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.IoTSpaces/Graph/{resourceName}
Create or update an IoTSpaces Graph
GET
/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.IoTSpaces/Graph/{resourceName}
Get a single IoTSpaces Graph by name
POST
/subscriptions/{subscriptionId}/providers/Microsoft.IoTSpaces/checkNameAvailability
Check if an IoTSpaces service name is available
GET
/subscriptions/{subscriptionId}/providers/Microsoft.IoTSpaces/Graph
List IoTSpaces Graph instances in the subscription
GET
/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.IoTSpaces/Graph
List IoTSpaces Graph instances in a resource group
PUT
/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.IoTSpaces/Graph/{resourceName}
Create or update an IoTSpaces Graph
GET
/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.IoTSpaces/Graph/{resourceName}
Get a single IoTSpaces Graph by name
POST
/subscriptions/{subscriptionId}/providers/Microsoft.IoTSpaces/checkNameAvailability
Check if an IoTSpaces service name is available
Jentic AI Readiness Score
This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.
I
IoTSpacesClient
- Foundational (D)44/100
73
Foundational Compliance63
Developer Experience & Jentic Compatibility22
AI-Readiness & Agent Experience94
Agent Usability35
Security100
AI DiscoverabilityPowered by JenticScoring Framework 1.0.0 | Scoring Engine 0.4.0
Show dimension breakdown
73
Foundational Compliance
Base layer of spec validity and structural soundness.
Grade: A-Signals: 4
94%
Lint Results
Aggregated quality score from linter diagnostics, weighted by severity.
100%
Resolution Completeness
Percentage of `$ref` references that resolve successfully.
0%
Specification Validity
Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).
100%
Structural Integrity
Structural correctness score based on schema issues using logarithmic dampening.
63
Developer Experience & Jentic Compatibility
Clarity, completeness, and ingestion readiness for developers and tooling.
Grade: B-Signals: 4
0%
Example Density
How richly the API is illustrated with examples.
100%
Example Validity
Percentage of examples that conform to their schemas.
50%
Response Coverage
Percentage of operations with complete response definitions (success, client error, server error).
100%
Tooling Readiness
Health of API ingestion, bundling, and resolution within Jentic pipelines.
22
AI-Readiness & Agent Experience
Semantic breadth, depth, and agent comprehension for AI systems.
Grade: FSignals: 4
87%
Description Coverage
Coverage of descriptions across API elements.
0%
Error Standardization
Coverage of RFC 9457 Problem Details for error responses.
0%
OperationId Quality
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
0%
Summary Coverage
Coverage of summaries across operations/tags/info.
94
Agent Usability
Functional utility, complexity comfort, and AI orchestration readiness.
Grade: A+Signals: 1
94%
Complexity Comfort
Agent comfort level based on API operational and structural complexity.
35
Security
Trust, risk posture, and security compliance.
Grade: FSignals: 1
35%
Authentication Strength
Average quality of security schemes based on authentication method strength (weakest link for OAuth2).
100
AI Discoverability
Findability, semantic richness, and reasoning readiness.
Grade: A+Signals: 1
100%
Descriptive Richness
Clarity and depth of descriptions across API elements.
Score it yourself
Every API in the directory is allowlisted, so you can re-score it with no key required.
npx @jentic/api-scorecard-cli score <openapi-url>Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the IoTSpaces (Digital Twins Graph) management API by hand means registering an Azure AD app, negotiating OAuth 2.0 tokens for management.azure.com, and carrying subscription and resource-group scope through every Graph call. Through Jentic you install once, import IoTSpacesClient from the API Directory, store the Azure AD credential once, and your agent calls it.
Permission scoping
This API puts the Graph resource in the URL path (/resourceGroups/{resourceGroupName}/providers/Microsoft.IoTSpaces/Graph/{resourceName}), so a rule can pin your agent to one Graph resource: it can read that resource and check name availability. You choose the operations it may call, so creating or replacing a Graph is not included unless you add it.
Credential isolation
Your Azure AD credential for the IoTSpaces control plane 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.
Intent-based discovery
Agents search Jentic by intent such as 'list IoTSpaces Graph resources' or 'check an IoTSpaces name', and Jentic returns the matching IoTSpaces operation with its input schema so the agent calls the right endpoint without browsing the reference docs.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using IoTSpacesClient API through Jentic.
Why is there no official OpenAPI spec for IoTSpacesClient?
Microsoft does not publish a maintained OpenAPI 3 specification for the legacy Microsoft.IoTSpaces resource provider. Jentic generates and maintains this spec so that AI agents and developers can call IoTSpacesClient 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 IoTSpacesClient use?
It uses Azure Active Directory OAuth 2.0 against management.azure.com with the user_impersonation scope, the standard ARM auth. Through Jentic the AAD client secret is held in the your Jentic One instance and a scoped bearer token is injected per call so the agent never sees raw secrets.
Can I check service name availability before creating an IoTSpaces graph?
Yes. POST to /subscriptions/{subscriptionId}/providers/Microsoft.IoTSpaces/checkNameAvailability with the candidate name in the request body. The response indicates whether the name is taken and surfaces a reason code if it is invalid.
What are the rate limits for IoTSpacesClient?
It runs on the Azure Resource Manager plane and inherits ARM throttling - typically 12,000 reads and 1,200 writes per hour per subscription, surfaced via x-ms-ratelimit-remaining-subscription-* headers. The IoTSpaces RP itself does not document tighter management-plane limits.
How do I provision an IoTSpaces graph through Jentic?
Run pip install jentic, then search Jentic with 'create an Azure IoTSpaces graph', load the create-or-update operation, and execute with subscriptionId, resourceGroupName, resourceName, location, and sku. Jentic returns the deployed resource.
Should I be using IoTSpaces or Azure Digital Twins?
For new workloads, Azure Digital Twins is the supported successor to IoTSpaces and offers a richer DTDL-based modelling surface. Use this API only when you are operating an existing IoTSpaces deployment that has not yet been migrated.
Can I limit what my agent is allowed to do with the Microsoft Azure IoTSpaces API?
Yes. Because Jentic One is self-hosted, your own rules decide which IoTSpaces operations and Azure AD credential the agent may use. Since this API carries the Graph resource in the URL path, you can pin the agent to a single Graph resource and allow only reads and name-availability checks. Create-or-update operations that replace a Graph stay off unless you explicitly grant them.
GET STARTED