/goonet/listings

POST /api/goonet/listings

Price: 20 credits

Get full Goo-net used-car listing details by listing URL: title, brand, grade, body type, body and total price, monthly payment, year, mileage, inspection, repair history, transmission, drive, drive layout, fuel, fuel grade, displacement, doors, seats, color, steering side, power, weight, dimensions, fuel economy, the equipment list, the Goo-kantei condition rating (interior/exterior/engine), warranty, dealer (name/address/phone) and photos.

How to use it

Fetch a single Goo-net used-car listing by its full listing URL (e.g. 'https://www.goo-net.com/usedcar/spread/goo/{n}/{car_code}.html'). Returns title, brand, grade, price and total_price (JPY), monthly_payment, body_type, year, mileage (km), inspection, has_repair_history, is_one_owner, is_non_smoking, is_unused, is_eco_car, transmission, drive, drive_layout (FF/FR/…), fuel, fuel_grade, displacement (cc), doors, seats, color, wheel (left/right), max_power, weight, dimensions, fuel_economy, turbocharger, import_route, equipment (list of fitted features), interior_rating/exterior_rating/engine_status (Goo-kantei condition eval), warranty, dealer (name/address/phone) and images.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• listing string required — Listing as a full Goo-net listing URL (examples: "https://www.goo-net.com/usedcar/spread/goo/17/700100218030260415003.html"; minLength: 1)

Response

• @type string (default: "GoonetListing")
• id string required
• url string required
• brand string nullable
• model string nullable
• grade string nullable
• body_type string nullable
• price number nullable
• total_price number nullable
• currency string nullable
• year integer nullable
• mileage integer nullable
• inspection string nullable
• has_repair_history boolean nullable
• is_one_owner boolean nullable
• is_non_smoking boolean nullable
• is_unused boolean nullable
• has_maintenance_record boolean nullable
• transmission string nullable
• drive string nullable
• drive_layout string nullable
• fuel string nullable
• fuel_grade string nullable
• displacement integer nullable
• doors string nullable
• seats integer nullable
• color string nullable
• wheel string nullable
• prefecture_code string nullable
• city_code string nullable
• max_power string nullable
• weight string nullable
• dimensions string nullable
• fuel_economy string nullable
• turbocharger string nullable
• cargo_bed_dimensions string nullable
• import_route string nullable
• is_import_certified boolean nullable
• is_eco_car boolean nullable
• monthly_payment number nullable
• interior_rating integer nullable
• exterior_rating integer nullable
• engine_status string nullable
• warranty string nullable
• legal_maintenance string nullable
• chassis_last_digits string nullable
• equipment array (default: [])
• description string nullable
• dealer object nullable
  • @type string (default: "GoonetListingDealer")
  • id string nullable
  • name string nullable
  • address string nullable
  • phone string nullable
  • url string nullable
• image string nullable
• images array (default: [])

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 — Listing not found (well-formed URL but the listing does not exist or 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.