Microsoft Azure APIs

237 APIs4,900 Endpoints17 Categories

API Catalog(7 of 237)

AzureDigitalTwinsManagementClient

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.

16 endpoints

DataBoxEdgeManagementClient

Jentic publishes the only available OpenAPI specification for DataBoxEdgeManagementClient, keeping it validated and agent-ready. The Azure Data Box Edge management API exposes 49 operations across 32 paths to provision Data Box Edge devices, configure their bandwidth schedules, alerts, roles, shares, storage account credentials, triggers, users, and orders. Use it to onboard new edge appliances at branch sites, push compute roles and storage shares onto them, and monitor alerts across a fleet from a central control plane.

49 endpoints

DeviceServices

Jentic publishes the only available OpenAPI specification for DeviceServices, keeping it validated and agent-ready. The API manages Windows IoT Device Services under Microsoft.WindowsIoT — the resource type that backs Windows IoT device fleets in Azure. It covers the create, read, update, and delete lifecycle of device service resources at subscription and resource-group scope plus the dedicated name-availability check needed before provisioning.

8 endpoints

IotCentralClient

Jentic publishes the only available OpenAPI specification for IotCentralClient, keeping it validated and agent-ready. The Microsoft.IoTCentral resource provider API manages Azure IoT Central applications in an Azure subscription. It exposes 10 ARM endpoints to create and update IoT Central apps, list them by subscription or resource group, browse the catalogue of app templates, and check that a chosen name and subdomain are available before provisioning.

10 endpoints

iotDpsClient

Jentic publishes the only available OpenAPI specification for the Azure IoT Hub Device Provisioning Service control plane, keeping it validated and agent-ready. The Microsoft.Devices/provisioningServices resource provider creates and manages DPS instances that handle zero-touch IoT device enrolment into IoT Hubs. It exposes 18 ARM endpoints to provision DPS instances, manage CA certificates, generate and verify proof-of-possession codes, list shared access keys, and check name availability before deploy.

18 endpoints

iotHubClient

Jentic publishes the only available OpenAPI specification for the Azure IoT Hub control plane (2019-07-01-preview), keeping it validated and agent-ready. The Microsoft.Devices/IotHubs resource provider creates and manages IoT Hub instances, their CA certificates, shared access keys, message routing, failover behaviour, and quota usage. It exposes 32 ARM endpoints to provision hubs, manage routing rules with $testall and $testnew dry-run paths, check routing endpoint health, list quota usage, and trigger manual failover.

32 endpoints

IoTSpacesClient

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.

8 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.