Azure Iotspaces

Connector for the azure-iotspaces API, generated deterministically from its OpenAPI spec (endpoints, auth, and methods match the spec exactly — nothing is invented).

• Base URL: https://management.azure.com
• Auth: OAuth 2.0 (user-delegated) — attach an InTouch oauth credential. Mint one with itcli.py /oauth <provider> (device-code) or /google-auth (Google); the server auto-refreshes the access token before each run, so the connector never handles or stores tokens.

Operations

• operations_list — GET /providers/Microsoft.IoTSpaces/operations — Lists all of the available IoTSpaces service REST API operations.
• iotspaces_list — GET /subscriptions/{subscriptionId}/providers/Microsoft.IoTSpaces/Graph — Get all the IoTSpaces instances in a subscription.
• iotspaces_listbyresourcegroup — GET /subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.IoTSpaces/Graph — Get all the IoTSpaces instances in a resource group.
• iotspaces_get — GET /subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.IoTSpaces/Graph/{resourceName} — Get the metadata of a IoTSpaces instance.
• iotspaces_checknameavailability — POST /subscriptions/{subscriptionId}/providers/Microsoft.IoTSpaces/checkNameAvailability — Check if an IoTSpaces instance name is available.
• iotspaces_createorupdate — PUT /subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.IoTSpaces/Graph/{resourceName} — Create or update the metadata of an IoTSpaces instance. The usual pattern to mod

Inputs

• a linked oauth credential (no key inputs) — the server injects a fresh Authorization: Bearer from it
• operation — one of the operations above
• path parameters when an operation's path contains {...}
• query — optional JSON object of query params
• body — JSON object for create/update ops

Example

operation: operations_list
# (attach an 'oauth' credential to the task — no inline secrets)