canonical: https://jentic.com/apis/ote-godaddy.com/godaddy-aftermarket

# Ote Godaddy GoDaddy Aftermarket API

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.

## For AI agents

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

## Scope

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

## Capabilities

- 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

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

Example prompt: 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.

Example prompt: 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.

Example prompt: 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.

Example 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

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

## Key resources

- **Listings** — Aftermarket auction listings managed by registrar partners
- **Expiry** — Expiry events posted into the GoDaddy auction queue

## Why Jentic

- **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 handling:** 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.
- **Discovery method:** 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.

## Related APIs

- **GoDaddy Domains API** — Domains API manages active registrations; Aftermarket API handles the expiry auction lifecycle for the same portfolio.
- **GoDaddy Abuse API** — Abuse API handles takedowns; Aftermarket API handles auction lifecycle - both run against the same GoDaddy SSO credentials.
- **GoDaddy Orders API** — Orders API surfaces purchase records; Aftermarket API governs the auction listings that feed those purchases.

## FAQ

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