Install Jentic One Beta

Connect the GoDaddy Aftermarket API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the GoDaddy Aftermarket API, 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%2Fgodaddy-aftermarket" | 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%2Fgodaddy-aftermarket" | 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 Aftermarket API.

Withdraw a domain or set of domains from the aftermarket listings

Post expiry events into the GoDaddy auction queue for partner-managed domains

Operate against the OTE test environment before promoting calls to production

Bulk-modify listings via the listings collection endpoint

Use Cases

Patterns agents use GoDaddy Aftermarket API for, with concrete tasks.

GET STARTED

Start building with GoDaddy Aftermarket API

Explore with Jentic One

View OpenAPI Document

★ Registrar Withdrawal of Listings

Registrars participating in the expiry stream sometimes need to withdraw a domain - for example because the registrant renewed late or transferred away. DELETE /v1/aftermarket/listings accepts the listing payload and removes the relevant entries so they no longer surface in the GoDaddy auction. Integration is typically a few hours of work for a registrar that already has GoDaddy SSO credentials.

Remove domain 'example.com' from the aftermarket listings by calling DELETE /v1/aftermarket/listings with the appropriate listing identifier.

Posting Expiry Events to the Auction Queue

Partners post expiry events into the GoDaddy queue with POST /v1/aftermarket/listings/expiry, which feeds the expiring-domain auction. The endpoint accepts the necessary domain and timing detail so GoDaddy can list the domain at the appropriate point in its drop cycle. This is a back-office endpoint used as part of the registrar-partner workflow.

Post an expiry event for 'example.com' by POSTing the expiry payload to /v1/aftermarket/listings/expiry.

OTE Sandbox Validation

The api.ote-godaddy.com base URL is GoDaddy's Operational Test Environment, used by registrar engineers to verify aftermarket calls before pointing at production. Both endpoints behave the same way as production but operate against test data, so partners can validate authentication, payload shape, and response handling without touching live listings.

Run the same DELETE /v1/aftermarket/listings call against the OTE base URL to verify authentication and payload shape before promoting to production.

AI Agent Registrar Operations via Jentic

Agents that monitor portfolio domains for expiry decisions can post or withdraw aftermarket listings programmatically. Through Jentic, the agent searches for 'withdraw a domain from the GoDaddy aftermarket', loads the DELETE /v1/aftermarket/listings schema, and executes it with the SSO credentials held in the vault. This avoids the agent ever holding the registrar's API secret in its prompt.

Use Jentic to search 'withdraw a domain from the GoDaddy aftermarket', load the DELETE /v1/aftermarket/listings schema, and execute it for the domain that just renewed.

Key Endpoints

2 endpoints — the godaddy aftermarket api (ote - operational test environment) is a small, partner-focused interface used by registrar partners participating in godaddy's expiry auction programme.

METHOD

PATH

DESCRIPTION

DELETE

/v1/aftermarket/listings

Remove domains from the aftermarket listings

POST

/v1/aftermarket/listings/expiry

Post an expiry event into the auction queue

DELETE

/v1/aftermarket/listings

Remove domains from the aftermarket listings

POST

/v1/aftermarket/listings/expiry

Post an expiry event into the auction queue

Why Jentic?

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

Setup

Wiring the GoDaddy Aftermarket API by hand means targeting the api.ote-godaddy.com test host and managing your own retries around listing withdrawals and expiry posts. Through Jentic you install once, import the GoDaddy Aftermarket API from the API Directory, store any required GoDaddy key once, and your agent calls it.

Permission scoping

The Aftermarket API identifies listings through request bodies rather than URL path ids, so scope by operations: limit the agent to the operations it needs, such as posting expiry events, and leave listing withdrawal out unless you add it. You choose the allowed set, so an agent can post expiries without being able to remove listings.

Credential isolation

Any GoDaddy credential the Aftermarket API requires is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'withdraw an aftermarket listing' or 'post a domain expiry event', and Jentic returns the matching GoDaddy Aftermarket operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using GoDaddy Aftermarket API through Jentic.

What authentication does the GoDaddy Aftermarket API use?

The OpenAPI spec does not declare a security scheme, but in practice GoDaddy's API surface is gated by an SSO key/secret pair passed as 'Authorization: sso-key <KEY>:<SECRET>'. Through Jentic the SSO credentials are stored encrypted in the vault and injected at call time, so the secret never enters the agent's context.

Can I withdraw a domain from the GoDaddy aftermarket?

Yes. DELETE /v1/aftermarket/listings accepts the listing payload and removes the matching entries so the domains no longer appear in GoDaddy's auction. Use this when a registrant renews late, transfers away, or otherwise should not be auctioned.

What are the rate limits for the GoDaddy Aftermarket API?

Specific limits are not declared in the Aftermarket OpenAPI spec; GoDaddy applies SSO-key based throttling across its API surface. Partners running bulk operations should batch calls and back off on 429 responses.

How do I post an expiry event through Jentic?

Through Jentic, search for 'post a GoDaddy expiry event', load the POST /v1/aftermarket/listings/expiry schema, and execute it with the domain and timing payload. Jentic injects the SSO key/secret from the vault.

Why does the base URL include 'ote'?

ote-godaddy.com is GoDaddy's Operational Test Environment - the public sandbox that mirrors the production API. Use OTE while validating an integration; switch to api.godaddy.com once the calls behave correctly.

Is the GoDaddy Aftermarket API free to use?

The API itself is provided to registrar partners as part of the expiry auction programme; commercial terms (auction fees, revenue share) are governed by the partner agreement with GoDaddy rather than per-call charges.

Can I limit what my agent is allowed to do with the GoDaddy Aftermarket API?

Yes. Because you run Jentic One yourself, your own rules decide which of the Aftermarket API's operations the agent may call, so you can allow it to post expiry events with POST /v1/aftermarket/listings/expiry while withholding the DELETE /v1/aftermarket/listings withdrawal operation. Since this API identifies listings through request bodies rather than URL path IDs, you scope access at the operation level and choose the exact set the agent is permitted to use. The GoDaddy credentials the agent needs are held by your instance and injected at call time, so the agent never sees the secret and can only invoke the operations you have allowed.

Ote Godaddy GoDaddy Aftermarket API

Name: GoDaddy Aftermarket API
Brand: Aftermarket API
Availability: InStock

Browse all Ote Godaddy APIs

Official vendor OpenAPI document · agent-readyE CommerceStorefrontnone2 EndpointsREST

For Agents

Manage GoDaddy aftermarket expiry auction listings as a registrar partner. Agents can withdraw domains from auction or post expiry events to the queue.

Use for: Remove a domain from the aftermarket listings, Post an expiry event to the GoDaddy auction queue, Withdraw a list of domains from auction, Test an aftermarket integration in OTE before going live

Not supported: Does not handle DNS edits, domain registration, or buyer-side auction bidding - use for registrar-partner withdrawal of listings and posting expiry events only.

The GoDaddy Aftermarket API (OTE - Operational Test Environment) is a small, partner-focused interface used by registrar partners participating in GoDaddy's expiry auction programme. It allows registrars to remove domains from the aftermarket listings or post expiry events into the auction queue. With two endpoints under /v1/aftermarket/listings, the API is purpose-built for back-office registrar integration rather than a general developer surface.

Jentic One on Github View OpenAPI Document