POST /api/goonet/dealers/listings
Price: 20 credits
List all used-car listings in a Goo-net dealer's inventory by shop id. Returns listing cards with id, url, brand, model, grade, prices, year, mileage, inspection, condition rating and image.
List a Goo-net dealer's inventory by shop id (e.g. '1002180') or full dealer URL. Each result has id, url, brand, model, grade, price, total_price, monthly_payment, year, mileage, inspection, displacement, color, transmission, body_type, condition ratings and image.
access-token string requiredtimeout 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"; minLength: 1)count integer required — Max number of results to return (min: 1)@type string (default: "GoonetListingCard")id string requiredurl string requiredbrand string nullablemodel string nullablegrade string nullableprice number nullabletotal_price number nullablefees number nullablemonthly_payment number nullableloan_type string nullableyear integer nullablemileage integer nullableinspection string nullabledisplacement integer nullablehas_repair_history boolean nullabletransmission string nullablelegal_maintenance string nullablewarranty string nullableinterior_rating integer nullableexterior_rating integer nullableengine_status string nullablehas_obd_diagnosis boolean nullablehas_360_view boolean nullableis_goonet_select boolean nullableis_new_listing boolean nullableis_updated boolean nullabletags array (default: [])dealer object nullable@type string (default: "GoonetCardDealer")id string nullablename string nullableshop_type string nullableaddress string nullableopening_hours string nullableclosed_days string nullablerating number nullablereview_count integer nullablephone string nullableimage string nullableimage string nullable422 — 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.X-Error — Error message text (present only on error)X-Request-ID — Unique request identifierX-Execution-Time — Execution time in secondsX-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.