/hemmings/dealers

POST /api/hemmings/dealers

Price: 1 credit

Get one Hemmings dealer by slug or URL: numeric dealer id, name, website, street address, city, state, postal code, country, phone, logo and the number of listings on the dealer page.

How to use it

Fetch a Hemmings dealer profile by the slug from its hemmings.com/classifieds/dealer/ URL. The returned id is the dealer_id that hemmings/listings/search accepts; hemmings/dealers/listings returns the inventory directly.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• dealer string required — Dealer slug from a hemmings.com/classifieds/dealer/<slug> URL, or the URL itself (examples: "fort_pitt_classic_cars", "https://www.hemmings.com/classifieds/dealer/fort_pitt_classic_cars"; minLength: 1)

Response

• @type string (default: "HemmingsDealerProfile")
• id string required
• alias string required
• url string required
• name string nullable
• website string nullable
• address string nullable
• city string nullable
• state string nullable
• state_name string nullable
• postal_code string nullable
• country string nullable
• phone string nullable
• image string nullable
• listing_count integer nullable

Errors

• 422 — The request body did not validate Check the fields against this schema. A URN with the wrong prefix is the most common cause.
• 408 — The request ran past its time limit Raise `timeout` in the request body, up to the maximum this endpoint documents. Lowering `count` or turning off the `with_*` flags also helps, because less work finishes sooner.
• 412 — No Hemmings dealer exists at this slug. Retrying will not help: either the entity does not exist, or the input points at a different one.
• 429 — Too many requests: a rate limit or a usage window is exhausted When the response carries an X-Retry-After header, wait that many seconds and retry: the same number is in the body as `detail.retry_after`, and the limit clears once that window passes. The message in the body names the limit that was hit.
• 500 — Something broke on our side Retrying will not help. If it keeps happening, send us the X-Request-ID from the response headers.
• 529 — Rate limit reached, or the endpoint is overloaded Wait at least 30 seconds, then retry.

Response headers

• X-Error — Error message text (present only on error)
• X-Request-ID — Unique request identifier
• X-Execution-Time — Execution time in seconds
• X-Result-Count — How many records the body carries. 0 means an empty result, which is a normal answer and not by itself an error. A non-zero count can come back together with X-Error when the failure happened partway through — read this header and X-Error independently.
• X-Total-Available-Results — How many records exist for this query, when the endpoint can say. On a `dry_run` request this is the answer and the body is empty. It saturates: the endpoint's documented maximum means 'at least that many', any smaller number is exact.
• X-Warning — Present when the request body carried keys this endpoint does not document. They were ignored, so any filter you meant to apply through them did not apply. Check the spelling against this schema and retry.
• X-Retry-After — Seconds to wait before retrying. Present only on 429.