Domains API Client

Name: Domains API Client API
Brand: Domains API Client
Availability: InStock

★ Only Publicly Available OpenAPI DocumentCloud InfrastructureNetworkingoauth215 EndpointsREST

For Agents

Check domain availability, get name recommendations, and register, renew, or manage Azure-purchased domain names along with their ownership identifiers.

Connect the Domains API Client to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Domains API Client, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Install Jentic One Beta (Self-Hosted)

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

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 Domains API Client API.

Check whether a candidate domain name is available for registration

Generate domain name recommendations from seed keywords

Renew an existing Azure-purchased domain

GET STARTED

Start building with Domains API Client API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI document for Domains API Client, keeping it validated and agent-ready.

Jentic publishes the only available OpenAPI specification for Domains API Client, keeping it validated and agent-ready. The Azure Domains API Client manages domain names purchased through Azure App Service Domains. It exposes 15 endpoints covering domain availability checks, recommendation lookups, domain CRUD, renewal, ownership identifiers, and a single sign-on request endpoint that hands off to the App Service domain control center.

Use Cases

Patterns agents use Domains API Client API for, with concrete tasks.

★ Programmatic Domain Acquisition

When a product team needs a domain for a new launch, the Domains API lets an automation agent check availability with Domains_CheckAvailability, gather alternatives via Domains_ListRecommendations, and complete the purchase through Domains_CreateOrUpdate without anyone opening the portal. Domain ownership lives in the same subscription as the App Service that will consume it, so DNS can be wired up in the same automation run.

Call Domains_CheckAvailability for newproduct.com; if available, call Domains_CreateOrUpdate to register it in resource group brand-rg with consent provided.

Bulk Domain Renewal

Companies with portfolios of dozens or hundreds of brand domains lose money to lapsed registrations. The Domains API exposes Domains_List to enumerate every domain the subscription owns and Domains_Renew to extend each one in a single batch. Combined with the expiry date returned by Domains_Get, an agent can flag any domain expiring in the next 30 days and renew automatically.

List every domain in subscription X and renew any whose expirationTime is within 30 days of today.

Domain Ownership Verification at Scale

Some integrations require proof that a domain is owned by a specific Azure resource — for example, configuring a custom domain on App Service. The Domains API exposes ownership identifier endpoints so an agent can create or update a verification token, store the linked Azure resource ID, and confirm ownership without the portal flow.

Create a domain ownership identifier named appservice-verify on example.com pointing at the resource ID of the App Service that needs to claim the domain.

AI Agent Domain Concierge via Jentic

An assistant integrated through Jentic can resolve a request like buy a sensible .com for our new fintech product end-to-end. It searches Jentic for check azure domain availability, loops through Domains_CheckAvailability for shortlisted names, calls Domains_ListRecommendations for alternatives, and completes the purchase via Domains_CreateOrUpdate. Credentials never leave the Jentic vault.

Through Jentic, search for register a domain on azure, load Domains_CreateOrUpdate, and register newbrand.app in resource group launch-rg.

Key Endpoints

15 endpoints — jentic publishes the only available openapi specification for domains api client, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

POST

/subscriptions/{subscriptionId}/providers/Microsoft.DomainRegistration/checkDomainAvailability

Check if a domain is available for registration

POST

/subscriptions/{subscriptionId}/providers/Microsoft.DomainRegistration/listDomainRecommendations

Get domain name recommendations

PUT

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.DomainRegistration/domains/{domainName}

POST

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.DomainRegistration/domains/{domainName}/renew

Renew a domain

GET

/subscriptions/{subscriptionId}/providers/Microsoft.DomainRegistration/domains

List all domains in a subscription

POST

/subscriptions/{subscriptionId}/providers/Microsoft.DomainRegistration/generateSsoRequest

Generate a single sign-on request to the domain control center

POST

/subscriptions/{subscriptionId}/providers/Microsoft.DomainRegistration/checkDomainAvailability

Check if a domain is available for registration

POST

/subscriptions/{subscriptionId}/providers/Microsoft.DomainRegistration/listDomainRecommendations

Get domain name recommendations

PUT

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.DomainRegistration/domains/{domainName}

POST

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.DomainRegistration/domains/{domainName}/renew

Renew a domain

GET

/subscriptions/{subscriptionId}/providers/Microsoft.DomainRegistration/domains

List all domains in a subscription

Why though Jentic?

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

Credential isolation

Azure AD client credentials are stored encrypted in the Jentic vault (MAXsystem). The agent receives a short-lived bearer token scoped to management.azure.com — the underlying secret or certificate never enters the agent context.

Intent-based discovery

Agents search by intent (e.g. 'register a domain on azure' or 'check domain availability') and Jentic returns the matching Domains_* operation with its full input schema, so the agent picks the right endpoint without browsing ARM docs.

Time to first call

Direct integration: 1-2 days for AAD token acquisition, ARM URL construction, and async LRO polling for the registrar handshake. Through Jentic: under 30 minutes — search, load schema, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Complementary

DNS Management Client

Hosts DNS records on the domains registered via the Domains API

Use after registering a domain to publish A, CNAME, MX, and TXT records

Complementary

DomainRegistrationProvider API Client

Lists the operations exposed by the Microsoft.DomainRegistration provider

Use when the agent needs to enumerate provider operations rather than register a domain

Alternative

Domain Services Resource Provider

Manages Azure AD Domain Services rather than domain name registration

Choose when the request concerns managed Active Directory rather than DNS-level domain ownership

FAQs

Specific to using Domains API Client API through Jentic.

Why is there no official OpenAPI spec for Domains API Client?

Microsoft Azure does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Domains API Client 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 Domains API Client use?

It uses Azure Active Directory OAuth 2.0 (azure_auth) against https://management.azure.com/. The principal needs at least Contributor on the target resource group. Through Jentic the underlying client secret stays in the Jentic vault and the agent only receives a scoped bearer token.

Can I check domain availability before registering?

Yes. POST /subscriptions/{subscriptionId}/providers/Microsoft.DomainRegistration/checkDomainAvailability accepts a name in the body and returns availability plus the registration price. Pair this with /listDomainRecommendations to get alternatives when the first choice is taken.

What are the rate limits for the Domains API Client?

Standard Azure Resource Manager subscription-scoped throttling applies (broadly 12,000 reads per hour and 1,200 writes per hour). Domain registration also depends on the upstream registrar and is not instantaneous — Domains_CreateOrUpdate may take several minutes before provisioningState reads Succeeded.

How do I register a domain through Jentic?

Run pip install jentic, search for register a domain on azure, load Domains_CreateOrUpdate, supply domainName, contactAdmin, contactBilling, contactRegistrant, contactTech, consent, and privacy, then execute. Poll Domains_Get until provisioningState is Succeeded.

Does this API manage DNS records on the registered domain?

No. The Domains API only handles registration and lifecycle (purchase, renew, ownership). DNS records on the registered domain are managed through Azure DNS via the separate DnsManagementClient API.