Microsoft Azure APIs

237 APIs4,900 Endpoints17 Categories

API Catalog(2 of 237)

Azure Location Based Services Resource Provider

Jentic publishes the only available OpenAPI specification for Azure Location Based Services Resource Provider, keeping it validated and agent-ready. The Azure Location Based Services Resource Provider API manages account-level resources for the Microsoft.LocationBasedServices namespace, letting operators provision Maps accounts inside an Azure subscription, list and rotate the primary and secondary subscription keys, and move accounts between resource groups. It is a control-plane API rather than a maps query API, so all calls go through Azure Resource Manager at management.azure.com and use Azure AD OAuth 2.0. Use it to automate the lifecycle of a Maps account before pointing applications at the Azure Maps data plane for geocoding or routing.

10 endpoints

Azure Maps Resource Provider

Jentic publishes the only available OpenAPI specification for Azure Maps Resource Provider, keeping it validated and agent-ready. The Azure Maps Resource Provider manages account-level resources under the Microsoft.Maps namespace, the successor to the older Microsoft.LocationBasedServices namespace. Operators can provision Azure Maps accounts, list accounts at subscription or resource-group scope, retrieve and rotate primary and secondary subscription keys, update SKU and tags, and move accounts between resource groups. All requests authenticate with Azure AD OAuth 2.0 against Azure Resource Manager.

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