/goonet/dealers

POST /api/goonet/dealers

Price: 10 credits

Get Goo-net used-car dealer details by shop id: name, description, phone, address, prefecture, opening hours, closed days, overall and per-aspect ratings, review count, inventory size and image.

How to use it

Fetch a single Goo-net dealer by its shop id (e.g. '1002180') or full dealer URL. Returns name, description, phone, address, prefecture_code, opening_hours, closed_days, rating, review_count, stock_count and per-aspect ratings (inquiry, explanation, delivery, recommendation).

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 shop id, or a full Goo-net dealer URL (examples: "1002180", "https://www.goo-net.com/usedcar_shop/1002180/detail.html"; minLength: 1)

Response

• @type string (default: "GoonetDealer")
• id string required
• url string required
• name string nullable
• description string nullable
• phone string nullable
• address string nullable
• prefecture_code string nullable
• city_code string nullable
• opening_hours string nullable
• closed_days string nullable
• rating number nullable
• review_count integer nullable
• stock_count integer nullable
• rating_inquiry number nullable
• rating_explanation number nullable
• rating_delivery number nullable
• rating_recommendation number nullable
• image string 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 — Dealer not found (the shop id does not exist or the dealer page was removed) 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.