GoDaddy Aftermarket API

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

✓ Official Vendor SpecE 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.

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.

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 GoDaddy Aftermarket API 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

GET STARTED

Start building with GoDaddy Aftermarket API API

Explore with Jentic

View OpenAPI Document

Use Cases

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

★ 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 though Jentic?

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

Credential isolation

GoDaddy registrar SSO key/secret pairs are stored encrypted in the Jentic vault. Agents receive scoped access tokens — the raw 'sso-key' Authorization header value never enters the agent's context.

Intent-based discovery

Agents search by intent (e.g. 'withdraw a domain from auction') and Jentic returns the matching aftermarket operation with its input schema, so the agent calls /v1/aftermarket/listings or /v1/aftermarket/listings/expiry correctly.

Time to first call

Direct Aftermarket integration: 1-2 days to wire SSO auth, OTE-to-production switching, and listing payloads. Through Jentic: under 1 hour — search, load schema, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Complementary

GoDaddy Domains API

Domains API manages active registrations; Aftermarket API handles the expiry auction lifecycle for the same portfolio.

Use the Domains API when modifying live registrations or DNS; use the Aftermarket API when the domain has expired or is heading to auction.

Complementary

GoDaddy Abuse API

Abuse API handles takedowns; Aftermarket API handles auction lifecycle — both run against the same GoDaddy SSO credentials.

Use the Abuse API when the workflow is reporting hosted content; use the Aftermarket API when the workflow is registrar-side auction management.

Complementary

GoDaddy Orders API

Orders API surfaces purchase records; Aftermarket API governs the auction listings that feed those purchases.

Use the Orders API when reading purchase history; use the Aftermarket API when posting or withdrawing auction listings.

FAQs

Specific to using GoDaddy Aftermarket API 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.