/goonet/catalog

POST /api/goonet/catalog

Price: 10 credits

Get the Goo-net new-car catalog (specifications) for a model by maker and model slug: per release-year model variants with price range, description and a grade table (grade name, model code, displacement, doors, transmission, drive, seats, fuel economy, weight, dimensions and new-car price).

How to use it

Fetch the Goo-net catalog/spec sheet for a model by maker+model slugs ('TOYOTA'/'PRIUS'). Returns model_id, title and releases[], each with name (release-year label), price_min/price_max (new-car JPY) and grades[] (name, model_code, displacement, doors, transmission, drive, seats, fuel_economy, weight, dimensions, price).

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• maker string required — Maker slug, uppercase (e.g. 'TOYOTA') (examples: "TOYOTA"; minLength: 1)
• model string required — Model slug, uppercase (e.g. 'PRIUS') (examples: "PRIUS"; minLength: 1)

Response

• @type string (default: "GoonetCatalog")
• maker string required
• model string required
• model_id string nullable
• url string required
• releases array (default: [])
  • @type string (default: "GoonetCatalogRelease")
  • name string nullable
  • price_min number nullable
  • price_max number nullable
  • description string nullable
  • grades array (default: [])
    • @type string (default: "GoonetCatalogGrade")
    • id string nullable
    • name string nullable
    • model_code string nullable
    • displacement integer nullable
    • doors integer nullable
    • transmission string nullable
    • drive string nullable
    • seats integer nullable
    • fuel_economy string nullable
    • weight string nullable
    • dimensions string nullable
    • price number 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 — Catalog not found (no catalog exists for this maker/model slug combination) 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.