boats APIboats.com ↗
Search boats.com listings by make, type, year, and condition. Retrieve specs, pricing, and seller contact info for any boat or yacht listing.
What is the boats API?
The boats.com API provides 2 endpoints covering boat and yacht listings from one of the largest marine marketplaces on the web. Use search_boats to filter by manufacturer, boat type, condition, and year range, returning paginated summaries of up to 24 listings per page. Use get_boat_details to pull full specifications, formatted pricing, seller name and location, and the complete listing description for any individual vessel.
curl -X GET 'https://api.parse.bot/scraper/99ad4dc1-13f5-486d-8294-95eea0f35502/search_boats?make=sea-ray&page=1&query=boats&year_to=2023&boat_type=power&condition=used&year_from=2015' \ -H 'X-API-Key: $PARSE_API_KEY'
Typed, relational, agent-ready
A generated client with real types, enums, and the links between objects — the structure a flat JSON response can't carry. Autocompletes in your editor and reads cleanly to coding agents.
- Fully typed · autocompletes
- Objects link to objects
- Typed errors & pagination
Typed Python client. Set up the SDK in your uv project, then pull this API’s typed client:
uv add parse-sdk uv run parse init uv run parse add --marketplace boats-com-api
uv run parse add --marketplace pulls a pinned snapshot of this canonical API — it won’t change underneath you. To customize it, subscribe and swap to your own copy.
"""Walkthrough: Boats.com SDK — search listings, drill into details."""
from parse_apis.boats_com_api import Boats, BoatType, Condition, BoatNotFound
client = Boats()
# Search for used power boats from a specific manufacturer, capped at 5 results.
for boat in client.boats.search(boat_type=BoatType.POWER, condition=Condition.USED, make="sea-ray", limit=5):
print(boat.title, boat.year, boat.price, boat.location)
# Drill into the first result's full details via sub-resource.
boat = client.boats.search(boat_type=BoatType.SAIL, limit=1).first()
if boat:
detail = boat.details.get()
print(detail.name, detail.price, detail.seller_name)
print("Specs:", detail.specs)
# Typed error handling: catch a removed listing.
try:
bad = client.boats.search(make="tracker", year_from=2020, limit=1).first()
if bad:
_ = bad.details.get()
except BoatNotFound as exc:
print(f"Listing gone: {exc.url}")
print("exercised: boats.search / boat.details.get / BoatNotFound error handling")
Search for boat listings with filters on type, condition, manufacturer, and year range. Returns a paginated list of matching boats with summary info (title, price, year, location, image). Each page contains up to ~24 listings. Use the listing URL from results to fetch full details via get_boat_details.
| Param | Type | Description |
|---|---|---|
| make | string | Boat manufacturer/make as a lowercase slug (e.g. 'boston-whaler', 'tracker', 'sea-ray'). |
| page | integer | Page number for pagination. |
| year_to | integer | Maximum year of manufacture. |
| boat_type | string | Type of boat to filter by. |
| condition | string | Condition of the boat. |
| year_from | integer | Minimum year of manufacture. |
{
"type": "object",
"fields": {
"page": "integer, current page number",
"listings": "array of boat listing summaries with id, title, year, price, location, url, image_url",
"total_results": "integer, count of listings on current page"
},
"sample": {
"data": {
"page": 1,
"listings": [
{
"id": "10165138",
"url": "https://www.boats.com/power-boats/2005-rinker-fiesta-vee-342-10165138/",
"year": "2005",
"price": "$64,000",
"title": "Rinker Fiesta Vee 342",
"location": "St Charles, Missouri",
"image_url": "https://images.boats.com/resize/1/51/38/2005-rinker-fiesta-vee-342-power-10165138-20260428095825134-0.jpg?t=1777395505000"
}
],
"total_results": 24
},
"status": "success"
}
}About the boats API
Search and Filter Listings
The search_boats endpoint accepts filters including make (as a lowercase slug like boston-whaler or sea-ray), boat_type, condition, year_from, year_to, and page for pagination. Each response includes total_results (the count of listings on the current page), along with an array of listing summaries. Every summary object carries id, title, year, price, location, url, and image_url. The url field from each summary is what you pass to the detail endpoint.
Retrieving Full Listing Details
get_boat_details takes a full listing URL and returns a structured object with the vessel's name, price, location, description, and a specs object containing key-value pairs such as make, model, year, length, and fuel type. Seller information is returned as seller_name and seller_location, which are useful for dealer research, lead aggregation, or market mapping. The description field contains the full freeform text the seller submitted with the listing.
Pagination and Coverage
Search results are paginated at roughly 24 listings per page. Increment the page parameter to walk through deeper result sets. All filters are optional, so an unfiltered call returns a broad cross-section of available inventory. Listing freshness depends on when the source listing was last updated on boats.com itself.
The boats API is a managed, monitored endpoint for boats.com — not a raw scraper you maintain. Every endpoint is automatically health-checked on a schedule, and when boats.com changes and a check fails, the API is automatically queued for repair and re-verified. It is built to keep working as the site underneath it changes.
This isn't an official boats.com API — it's an independent, maintained REST wrapper over public data. Where the source has no official API (or only a limited one), Parse gives you a stable contract over a source that never promised one, and keeps it current. Need a new endpoint or field? You can revise it yourself in plain English and the agent rebuilds it against the live site in minutes — contributing the change back to the shared API is free.
Will this API break when the source site changes?+
Is this an official API from the source site?+
Can I fix or extend this API myself if I need a new endpoint or field?+
What happens if I call an endpoint that has an issue?+
- Aggregate new and used boat inventory by manufacturer using the
makefilter for price comparison tools - Track asking price trends for specific vessel types over time using
boat_typeandyear_from/year_tofilters - Build a dealer directory by extracting
seller_nameandseller_locationacross paginated search results - Populate a boat valuation tool using
specsfields like length, year, make, and fuel type fromget_boat_details - Generate lead lists for marine service businesses by collecting seller contact data for listings in a target region
- Monitor new listings for a specific make by polling
search_boatswith amakeslug and comparing against knownidvalues
| 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 | 100 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 boats.com have an official developer API?+
What does the `specs` object in `get_boat_details` contain?+
specs field is a key-value object drawn from the listing's technical detail section. It covers attributes like make, model, year, length, and fuel type, though the exact keys present vary by listing since sellers control what they submit. Not every listing will have every spec field populated.Does the search endpoint return total result count across all pages, or just the current page?+
total_results field reflects the count of listings on the current page, not a global total across all pages. To estimate total inventory for a given filter combination, you would need to paginate through all pages and sum the counts.Does the API expose boat reviews, user ratings, or historical sold prices?+
Can I filter search results by geographic area or distance from a zip code?+
search_boats parameters do not include a location or radius filter. You can filter by make, boat_type, condition, and year range. Location data is returned in each listing summary and detail, so client-side filtering is possible. You can fork this API on Parse and revise it to add geographic filtering if boats.com exposes that parameter.