Install Jentic One Beta

Connect the GoDaddy Domains API (OTE) to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the GoDaddy Domains API (OTE), 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.

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%2Fote-godaddy.com%2Fdomains" | sh

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%2Fote-godaddy.com%2Fdomains" | 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 GoDaddy Domains API (OTE) API.

Check domain name availability and get pricing for registration or renewal

Purchase new domains with full contact and privacy configuration

Renew existing domains before expiration or during grace period

Update and manage DNS records including A, AAAA, CNAME, MX, TXT, SRV, and NS records

GET STARTED

Start building with GoDaddy Domains API (OTE) API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use GoDaddy Domains API (OTE) API for, with concrete tasks.

★ Automated Domain Portfolio Management

Organizations managing large domain portfolios can automate renewal tracking, DNS updates, and availability monitoring. GET /v1/domains returns all domains with status and expiration metadata, POST /v1/domains/{domain}/renew handles bulk renewals, and PATCH /v1/domains/{domain}/records updates DNS at scale. Agents can monitor expiration dates and trigger renewals before grace periods.

GET /v1/domains to retrieve the portfolio, filter by expiration date, then POST /v1/domains/{domain}/renew for each domain expiring within 30 days.

Dynamic DNS Configuration for Deployments

DevOps teams can programmatically update DNS records when services move between environments or IP addresses change. PUT /v1/domains/{domain}/records/{type}/{name} replaces records atomically, and PATCH /v1/domains/{domain}/records updates selectively. This eliminates manual DNS propagation delays during blue-green deployments or failover scenarios.

PATCH /v1/domains/{domain}/records with the new A record pointing to the updated load balancer IP, then verify propagation via GET /v1/domains/{domain}/records/A/{name}.

Domain Availability Search for Registration

SaaS platforms that offer custom domain features can check availability and pricing before presenting options to users. GET /v1/domains/available validates a single domain, POST /v1/domains/suggest returns alternatives, and POST /v1/domains/purchase completes registration with full contact configuration. Combines availability checking, pricing discovery, and instant provisioning.

GET /v1/domains/available with the requested domain name, then POST /v1/domains/purchase with contact details and privacy=true if available.

Domain Transfer Automation

Agencies managing client domains across registrars can automate inbound and outbound transfers. POST /v1/domains/transfers/{domain} initiates a transfer-in with the auth code, GET /v1/domains/{domain}/authcode retrieves the auth code for transfers-out, and GET /v1/domains/transfers/{domain} monitors transfer status. Reduces manual coordination and speeds up consolidation projects.

POST /v1/domains/{domain}/authcode to generate the auth code, then provide it to the receiving registrar's transfer API.

AI Agent for Domain Operations

Let an AI agent handle routine domain tasks for a web agency - checking availability, purchasing domains, configuring DNS for new sites, and monitoring renewals. Through Jentic, the agent loads only the required operations and the GoDaddy API key is injected at execution time without entering the agent's context.

Use the Jentic search query 'check domain availability godaddy' to find GET /v1/domains/available, load its schema, and execute with the target domain name.

Key Endpoints

47 endpoints — the godaddy domains api (ote - operational test environment) provides programmatic access to domain-related actions including purchasing, renewing, managing nameservers, dns records, and domain transfers.

METHOD

PATH

DESCRIPTION

GET

/v1/domains

List all domains in the account with filtering by status

GET

/v1/domains/available

Check if a domain is available for registration

POST

/v1/domains/purchase

Purchase a new domain with contacts and privacy

POST

/v1/domains/{domain}/renew

Renew an existing domain

GET

/v1/domains/{domain}/records

Get all DNS records for a domain

PATCH

/v1/domains/{domain}/records

Update DNS records for a domain

GET

/v1/domains/{domain}/authcode

Get the authorization code for transferring the domain out

GET

/v1/domains

List all domains in the account with filtering by status

GET

/v1/domains/available

Check if a domain is available for registration

POST

/v1/domains/purchase

Purchase a new domain with contacts and privacy

POST

/v1/domains/{domain}/renew

Renew an existing domain

GET

/v1/domains/{domain}/records

Get all DNS records for a domain

PATCH

/v1/domains/{domain}/records

Update DNS records for a domain

GET

/v1/domains/{domain}/authcode

Get the authorization code for transferring the domain out

Why Jentic?

What agents get from Jentic-routed access to this vendor.

Setup

Wiring the GoDaddy Domains API by hand means setting up the GoDaddy API key and secret pair, targeting the api.godaddy.com host, and managing your own retries across registration, DNS, and transfer calls. Through Jentic you install once, import the GoDaddy Domains API from the API Directory, store the key once, and your agent calls it.

Permission scoping

The Domains API puts the domain in the URL path (/v1/domains/{domain}/...), so a rule can pin your agent to one domain: it can read records and the authcode for that domain. You choose the operations it may call, so domain purchase, renewal, or record edits are not included unless you add them.

Credential isolation

Your GoDaddy API key and secret are stored once, encrypted, by your own Jentic One instance and injected at execution time. They never enter the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'check if a domain is available' or 'read a domain's DNS records', and Jentic returns the matching GoDaddy Domains operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using GoDaddy Domains API (OTE) API through Jentic.

What is the GoDaddy OTE environment?

OTE (Operational Test Environment) is GoDaddy's sandbox for development and testing. It mirrors the production API but operates on test data and test domains. No real purchases or charges occur in OTE. Once integration is tested in OTE, switch to production credentials.

What authentication does the GoDaddy Domains API use?

The GoDaddy API uses API key authentication sent via the Authorization header. API keys are generated in the GoDaddy developer portal. Through Jentic, keys are stored encrypted and injected at execution time so they never enter the agent's context.

Can I purchase real domains through this API?

Not with OTE credentials - this is the test environment. Real domain purchases require production API credentials. OTE is for integration testing and development only.

How do I update DNS records through Jentic?

Search Jentic for 'update godaddy dns record' to find PATCH /v1/domains/{domain}/records, load its schema, then execute with the domain name and new record data. Jentic injects the API key automatically.

What are the rate limits for the GoDaddy API?

GoDaddy enforces rate limits that vary by endpoint and account tier. Limits are not numerically specified in the OpenAPI spec; they are documented in GoDaddy's developer documentation and surface as HTTP 429 responses. Implement exponential backoff for retries.

Can I manage domains from multiple GoDaddy accounts?

Yes, by using the X-Shopper-Id header on requests. This allows resellers and agencies to manage domains across customer accounts using a single API key with delegated access.

GoDaddy (OTE Test Environment) GoDaddy Domains API (OTE)

Name: GoDaddy Domains API (OTE) API
Brand: GoDaddy Domains API (OTE)
Availability: InStock

Browse all Ote Godaddy APIs

Official vendor OpenAPI document · agent-readyDeveloper ToolsMonitoring Observabilityapikey47 EndpointsREST

For Agents

Manage GoDaddy domains programmatically: purchase, renew, transfer, update DNS records and nameservers, check availability, and manage domain contacts in the OTE test environment.

Use for: Check if a domain name is available for registration, Purchase a new domain with default privacy settings, Renew a domain for another year, Update DNS A record to point to a new IP address

Not supported: Does not host websites, manage hosting plans, or handle SSL certificate provisioning beyond domain-level operations - use for domain registration, DNS, and transfer management only.

The GoDaddy Domains API (OTE - Operational Test Environment) provides programmatic access to domain-related actions including purchasing, renewing, managing nameservers, DNS records, and domain transfers. This is a test environment for development and integration testing before deploying to production. Updates to domains generally require the domain to be in an ACTIVE status, and some actions on protected domains require 2FA which is not supported via the API.

Jentic One on Github View OpenAPI Document

Connect the GoDaddy Domains API (OTE) to your agent

Capabilities

Start building with GoDaddy Domains API (OTE) API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

GoDaddy (OTE Test Environment) GoDaddy Domains API (OTE)