yachtauctions.com APIyachtauctions.com ↗
Access National Liquidators' vessel auction inventory via API. List, search, and retrieve details on boats, yachts, and watercraft listings with specs and pricing.
curl -X GET 'https://api.parse.bot/scraper/c3da45f2-c2b5-4cee-afa8-0e82c04cff14/list_vessel_listings?page=0' \ -H 'X-API-Key: $PARSE_API_KEY'
List vessel listings with pagination and filters. Returns up to 18 items per page. Supports filtering by make, vessel type, live auction status, text search, and sorting.
| Param | Type | Description |
|---|---|---|
| make | string | Filter by vessel make slug from get_vessel_makes (e.g. 'sea-ray', 'bayliner'). |
| page | integer | Zero-based page number. Each page returns up to 18 items. |
| query | string | Free-text keyword to search vessel titles and descriptions. |
| sort_by | string | Sort option slug. Verified values: 'date_desc', '_price_asc', '_wpgb_featured_product_desc', 'acf/year_desc'. |
| vessel_type | string | Filter by vessel type slug from get_vessel_types (e.g. 'center-console', 'cruiser'). |
| live_auctions | string | Set to 'true' to show only live auction listings. Any other value or omission shows all listings. |
{
"type": "object",
"fields": {
"page": "integer, current page number",
"count": "integer, number of items returned on this page",
"items": "array of listing objects with title, url, slug, price, location, badges, and thumbnail"
},
"sample": {
"data": {
"page": 0,
"count": 18,
"items": [
{
"url": "https://yachtauctions.com/browse/2001-carver-506-motor-yacht-stk-41810/",
"slug": "2001-carver-506-motor-yacht-stk-41810",
"price": null,
"title": "2001 Carver 506 Motor Yacht – Stk# 41810",
"badges": [
"Live Auction"
],
"location": "Located in Michigan",
"thumbnail": "https://yachtauctions.com/wp-content/uploads/2026/04/93f2d337-f721-4914-9a67-bf0c8e5ca6fd-768x354.jpg"
}
]
},
"status": "success"
}
}About the yachtauctions.com API
This API exposes 8 endpoints covering National Liquidators' full vessel auction inventory on yachtauctions.com, including live auctions, featured listings, and recently added boats. The get_vessel_detail endpoint returns per-vessel specs, photos, asking price, contact info, and US state location. list_vessel_listings supports filtering by make, vessel type, live auction status, keyword query, and sort order, returning up to 18 results per page.
Listing and Searching Vessels
The list_vessel_listings endpoint is the primary way to browse inventory. It accepts a zero-based page integer, free-text query string, make slug (sourced from get_vessel_makes), vessel_type slug (sourced from get_vessel_types), and a sort_by option — verified values include date_desc, _price_asc, _wpgb_featured_product_desc, and acf/year_desc. Setting live_auctions to 'true' filters down to only currently active auction listings. Each page returns up to 18 items, each with title, url, slug, price, location, badges, and thumbnail. The search_vessels endpoint provides a direct keyword search matched against vessel titles and descriptions.
Vessel Detail Data
get_vessel_detail takes a vessel slug (formatted as <year>-<make>-<model>-stk-<id>) and returns the full listing: asking_price, description, photos array, contact_email, contact_phone, location_office, state, and a specs object organized by category with key-value pairs for hull, engine, dimensions, and other vessel attributes. If the listing no longer exists, the endpoint returns input_not_found.
Convenience Endpoints and Taxonomy
list_live_auctions and list_featured_listings require no inputs and return the same listing object shape used across all list endpoints. list_recently_listed returns up to 18 listings sorted by date descending — useful for monitoring new inventory as it becomes available. get_vessel_makes and get_vessel_types each return an array with name, slug, and count fields, giving you the full set of valid filter values for list_vessel_listings.
- Monitor new vessel inventory by polling
list_recently_listedand alerting when target makes appear. - Build a vessel comparison tool by pulling
specsfrom multipleget_vessel_detailcalls. - Track active auction count over time using
list_live_auctionsresponsecount. - Aggregate asking price distributions by vessel type using
list_vessel_listingswithvessel_typeand_price_ascsort. - Generate a make-specific inventory digest using
get_vessel_makesslugs piped intolist_vessel_listings. - Display a curated featured listings widget using
list_featured_listingsthumbnail and price fields. - Build a regional vessel search tool by filtering
get_vessel_detailresults on thestatefield.
| 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 yachtauctions.com have an official developer API?+
What does `get_vessel_detail` return in the `specs` object?+
specs field is an object of named categories — such as hull, engine, and dimensions — each containing key-value pairs for the attributes listed under that category. The exact keys present vary by listing depending on what the seller has provided. The endpoint also returns photos (array of image URLs), asking_price, state, contact_email, contact_phone, location_office, and the full description text.How does pagination work in `list_vessel_listings`?+
page parameter is zero-based, so page 0 is the first page. Each page returns at most 18 items. The response includes a count field reflecting how many items were returned on that specific page, not the total inventory count. To walk through all results, increment page until count is less than 18.Can I retrieve historical sold or completed auction listings?+
Are bid amounts or auction end times available in listing results?+
price, title, location, badges, slug, url, and thumbnail. The detail endpoint returns asking_price but no bid history, current bid amount, or auction countdown data. You can fork this API on Parse and revise it to surface those fields if they appear on individual listing pages.