auctions.godaddy.com APIauctions.godaddy.com ↗
Access GoDaddy Auctions data: search domain auctions, browse expired and closeout listings, get GoValue appraisals with bid counts, end times, and SEMrush metrics.
curl -X GET 'https://api.parse.bot/scraper/96539f73-10c8-4f95-a21d-9924ea344cb2/search_auctions?limit=3&query=tech' \ -H 'X-API-Key: $PARSE_API_KEY'
Search for domain auctions with filters and pagination. Returns auction listings sorted by the specified field, with domain valuation, bid count, backlink metrics, and SEMrush data for each result.
| Param | Type | Description |
|---|---|---|
| limit | integer | Number of results to return per page. |
| query | string | Search term to filter domains by keyword (e.g. 'tech', 'crypto'). Omitting returns all auctions. |
| start | integer | Pagination start offset (0-based). |
| types | string | Comma-separated list of auction type IDs to include. Accepted values: 16 (Expired), 38 (Closeout), 20 (Expiry), 39 (Pre-Release). Omitting defaults to all types: '16,38,20,39'. |
| sort_by | string | Sort field and direction. Format: 'field:direction'. Confirmed working values: 'auctionBids:desc', 'auctionValuationPrice:desc'. |
{
"type": "object",
"fields": {
"count": "integer number of items returned in this response",
"items": "array of auction listing objects with fields: fqdn, auction_id, auction_price, valuation_price, bids, end_time, auction_type, enrichments (SEMrush/Majestic/Estibot metrics)",
"total": "integer total number of matching auctions"
},
"sample": {
"data": {
"count": 1,
"items": [
{
"bids": 47,
"fqdn": "datacentres.com",
"end_time": "2026-05-08T17:48:00Z",
"auction_id": 700628683,
"enrichments": {
"semrush_ascore": 5,
"semrush_keyword": "datacentres",
"semrush_search_volume": 110
},
"auction_type": 38,
"auction_price": 1025,
"valuation_price": 9652,
"auction_price_usd": 1025,
"buy_it_now_amount": 0,
"domain_create_date": "2000-04-03T07:00:00Z",
"majestic_ref_domains": 270,
"majestic_ext_back_links": 11303
}
],
"total": 10000
},
"status": "success"
}
}About the auctions.godaddy.com API
The GoDaddy Auctions API covers 4 endpoints for retrieving domain auction data from auctions.godaddy.com, including active bids, valuations, and backlink metrics. The search_auctions endpoint lets you query across all auction types with keyword filtering, sort controls, and pagination. Separate endpoints isolate expired domain auctions and closeout (Buy It Now) listings, while get_domain_appraisal returns GoDaddy's GoValue estimate for any specific domain.
Auction Search and Filtering
The search_auctions endpoint accepts a query string to filter by keyword (e.g. tech, crypto), a types parameter for comma-separated auction type IDs (16 for Expired, 38 for Closeout, 20 for Expiry), and sort_by in field:direction format — for example auctionBids:desc to surface the most-contested domains first. Results are paginated via start (0-based offset) and limit. Each item in the items array includes fqdn, auction_id, auction_price, valuation_price, bids, end_time, auction_type, and enrichment fields covering backlink and SEMrush data. The response also returns count and total so you can build accurate pagination.
Expired and Closeout Listings
get_expired_domain_auctions and get_closeout_auctions are convenience endpoints that return the same auction listing object shape as search_auctions but pre-filtered to type 16 (expired) and type 38 (closeout / Buy It Now) respectively. Both accept a limit parameter and return count, items, and total. Closeout listings carry a fixed buy-it-now price rather than an active bid ladder, so auction_price reflects the posted price rather than a live bid.
Domain Appraisals
The get_domain_appraisal endpoint takes a single required domain_name and returns GoDaddy's GoValue estimate as a numeric govalue, the canonical domainName, and a valuationFactors array that breaks down the inputs driving the estimate. This is the same valuation data shown in GoDaddy's GoValue tool and can be used independently of any active auction.
- Monitor auction end times and bid counts to identify closing opportunities on expiring domains.
- Screen expired domains by keyword using the
queryparam to find brandable names in a target niche. - Compare
auction_priceagainstvaluation_pricefromsearch_auctionsto surface underpriced listings. - Pull GoValue appraisals in bulk via
get_domain_appraisalto build a domain portfolio valuation tracker. - Filter closeout listings with
get_closeout_auctionsto find fixed-price domains without entering an auction. - Use SEMrush and backlink fields from auction results to prioritize domains with existing organic authority.
- Track total auction counts over time using the
totalfield to measure supply trends in specific domain categories.
| Tier | Price | Credits/month | Rate limit |
|---|---|---|---|
| Free | $0/mo | 100 | 5 req/min |
| Hobby | $30/mo | 1,000 | 20 req/min |
| Developer | $100/mo | 5,000 | 250 req/min |
One credit = one API call regardless of which marketplace API you call. Exceeding the rate limit returns a 429 response. Authenticate with the X-API-Key header.
Does GoDaddy have an official public API for auction data?+
What fields does each auction listing item include?+
items array from search_auctions, get_expired_domain_auctions, and get_closeout_auctions includes fqdn, auction_id, auction_price, valuation_price, bids, end_time, auction_type, plus enrichment fields covering backlink metrics and SEMrush data. The total field on the response tells you the full result count beyond the current page.Can I retrieve historical auction results or sold domain prices?+
How does pagination work in search_auctions?+
start parameter as a 0-based offset and limit to control page size. The response returns count (items in the current page) and total (all matching results), so you can calculate the number of pages and iterate with incremented start values.Does the API cover domain auctions outside the .com TLD?+
fqdn field in auction results reflects whatever TLD the listed domain uses, so non-.com domains do appear when present in GoDaddy Auctions inventory. However, there is no TLD-specific filter parameter exposed — filtering by TLD would need to be applied client-side against the fqdn values returned. You can fork this API on Parse and revise it to add a TLD filter parameter if that's a core use case.