watchbase.com APIwatchbase.com ↗
Access WatchBase data via API: brands, collections, watch specs, caliber details, and images across thousands of timepieces. 10 endpoints.
No input parameters required.
curl -X GET 'https://api.parse.bot/scraper/4478feeb-1902-4307-96a0-7550387aa624/list_brands' \ -H 'X-API-Key: $PARSE_API_KEY'
List all watch brands with slugs and watch counts. Returns an array of brand objects.
No input parameters required.
{
"type": "object",
"fields": {
"data": "array of brand objects with name, slug, and watch_count",
"status": "string, always 'success'"
},
"sample": {
"data": [
{
"name": "A. Lange & Söhne",
"slug": "a-lange-sohne",
"watch_count": 0
},
{
"name": "Rolex",
"slug": "rolex",
"watch_count": 0
}
],
"status": "success"
}
}About the watchbase.com API
The WatchBase API provides structured access to the WatchBase watch database across 10 endpoints, covering brands, collections, individual references, mechanical calibers, and images. The get_watch_details endpoint returns case, dial, and movement specifications for a specific reference slug, while get_caliber_details exposes technical movement data alongside the watches that use each caliber. Search across the full catalog using search_watches with pagination.
Brands, Collections, and Watches
list_brands returns every brand in the WatchBase database as an array of objects containing name, slug, and watch_count. Those slugs feed into get_brand, which adds a description, website_url, and a nested collections array. From there, list_collections_by_brand scopes down to collection-level slugs, and list_watches_by_collection returns watch summaries with reference, name, slug, thumbnail_url, and url — the reference and collection slugs from this response are the keys to the more detailed endpoints.
Watch and Caliber Details
get_watch_details accepts brand_slug, collection_slug, and reference_slug and returns a full specification object: name, reference, family, movement, produced (production years), a structured case object, a structured dial object, a description, and an images list. get_watch_images targets the same three slugs and returns a plain array of image URL strings, useful when you only need the visual assets without the full spec payload.
On the caliber side, list_all_calibers returns every brand's movements in one call — each brand entry carries a calibers array with name and slug. get_caliber_details then returns movement-level fields including reference, movement type, diameter, jewels, description, and a watches_using_caliber array, letting you map a caliber to all references in the database that use it.
Search and Pagination
search_watches accepts a query string (e.g. speedmaster, submariner) and an optional page integer. Each page returns up to 20 results. The response includes total_results so you can calculate how many pages to iterate, plus the same summary shape used by collection listing endpoints: reference, name, slug, thumbnail URL, and full URL.
- Building a watch reference database that links caliber specs to all models using a given movement via
watches_using_caliber. - Generating a brand catalog page by iterating
list_brandsand hydrating each entry withget_brandcollection data. - Populating a watch comparison tool using the
caseanddialobjects fromget_watch_detailsacross multiple references. - Downloading watch imagery for training a visual classifier using the URL arrays returned by
get_watch_images. - Implementing a watch search feature in a collector app backed by
search_watcheswith paginated results. - Tracking which watches were produced in a specific year range using the
producedfield inget_watch_details. - Auditing a collection for movement details — cross-referencing
get_caliber_detailswith a user's owned references.
| 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 WatchBase offer an official developer API?+
What does `get_caliber_details` return beyond basic movement info?+
get_caliber_details returns the caliber's reference, movement type, diameter, jewels, and a description, plus a watches_using_caliber array. That array lets you resolve which watch references in the database are fitted with a particular movement without querying each watch individually.How does pagination work in `search_watches`?+
search_watches returns 20 results per page. The response includes a total_results integer so you can compute the number of pages needed. Pass the page parameter (integer, optional, defaults to page 1) to step through results.Does the API expose retail pricing or market valuations for watches?+
Can I retrieve watches filtered by movement type or production year directly?+
search_watches endpoint accepts a text query, and the produced and movement fields are available on individual watch records via get_watch_details. You can fork the API on Parse and revise it to add a filtered listing endpoint against those fields.