Skip to Content

Goo-net Exchange Data Parser & API

Goo-net Exchange is the international export arm of Japan’s leading used-car portal, listing around 257,000 vehicles — and Carapis extracts its full listing data, including detailed chassis-code → trim/spec mapping, auction-sheet grades and export pricing, through one REST API. Operated by PROTO Corporation, Goo-net Exchange carries the richest spec data in the Japan-export cluster, mapping each car’s chassis code to a precise trim and equipment record.

Available now. Goo-net Exchange is in the live feed — pull it from /apix/api/vehicles/ with your API key.

CountryJapan
TypePortal
OwnerPROTO Corporation
Vehicle typesused, export
Monthly visitsmid-tier (est.)
Active listings~257K cars
API accessPartial / limited API
Parse priority★★★★☆
Official sitewww.goo-net-exchange.com

What is Goo-net Exchange?

Goo-net Exchange is the English-language, export-facing version of Japan’s Goo-net used-car portal, run by PROTO Corporation. It lists roughly 257K cars and connects global buyers with Japanese exporters. Its standout feature is detailed chassis-code-based spec mapping: from a vehicle’s chassis code, Goo-net Exchange resolves the exact trim, grade and factory equipment — making its records unusually precise for the Japan-export market.

Market Position

Goo-net Exchange is a major Japan-export portal, listing ~257K cars (Goo-net Exchange). It sits in the Japan-export cluster alongside BE FORWARD, SBT Japan, TCV and Car From Japan, all funneling JDM stock to Africa, the Caribbean, SE Asia, the Middle East and Oceania. As the export arm of PROTO Corporation’s domestic Goo-net portal, it inherits Japan’s most detailed used-car spec database — chassis-code → trim mapping — which makes its data the richest for spec-accurate import decisions. Because export supply traces back to common Japanese auctions, its auction-sheet grades share the cluster’s standard structure.

What the API returns

Response schema

Indicative — this is the shape, not a guarantee. Every source returns the same structure, so what you build against does not change when you add one. Which fields carry a value depends on the source and on the individual listing: a site that does not publish mileage returns null there, and Goo-net Exchange is no exception.

List — GET /apix/api/vehicles/ — returns 30 fields per vehicle:

  • idstring
  • source_codestring
  • brand_namestring
  • brand_slugstring
  • model_namestring
  • model_slugstring
  • trimstring
  • yearinteger
  • price_usdinteger
  • mileageinteger
  • fuel_typeFuelTypeEnum
  • transmissionTransmissionEnum
  • body_typeBodyTypeEnum
  • colorColorEnum
  • seller_typeSellerTypeEnum
  • regionstring
  • source_locationobject
  • has_accidentboolean
  • is_new_vehicleboolean
  • is_verifiedboolean
  • statusVehicleStatusEnum
  • is_availableboolean
  • first_seen_atstring
  • last_seen_atstring
  • thumbVehiclePhoto
  • photosarray
  • photos_countinteger
  • has_valuationboolean
  • has_llm_analysisboolean
  • analysisobject

Detail — GET /apix/api/vehicles/{id}/ — adds 23 more:

  • generationstring
  • price_originalstring
  • price_original_currencystring
  • original_msrpstring
  • engine_ccinteger
  • seat_countinteger
  • drive_typeDriveTypeEnum
  • has_simple_repairboolean
  • has_recallboolean
  • recall_fulfilledboolean
  • warranty_typestring
  • inspection_passedboolean
  • owner_countinteger
  • is_undervaluedboolean
  • valuation_scorenumber
  • featuresarray
  • descriptionstring
  • listing_urlstring
  • listing_idstring
  • vinstring
  • vehicle_nostring
  • availability_checked_atstring
  • status_changed_atstring

Abbreviated example:

{
  "id": "0193f2c1-...",
  "source_code": "encar",
  "brand_name": "BMW",
  "model_name": "320i",
  "trim": "M Sport",
  "year": 2021,
  "price_usd": 28400,
  "price_original": "38900000",
  "price_original_currency": "KRW",
  "mileage": 45000,
  "fuel_type": "gasoline",
  "transmission": "automatic",
  "has_accident": false,
  "listing_url": "https://...",
  "photos": [{ "url": "https://cdn.carapis.com/..." }],
  "first_seen_at": "2026-09-28T11:04:22Z",
  "is_available": true
}

Which sources you can actually query is answered by GET /apix/api/sources/ with your API key — it is the list your account can pull today, and it is the one to trust over any page on this site.

The chassis-code-to-trim mapping is what makes Goo-net Exchange uniquely valuable: it removes ambiguity about exactly which grade and equipment a JDM car carries — delivered as structured fields rather than free text.

API Quick Start

import requests resp = requests.get( "https://api.carapis.com/v2/listings", params={"source": "goo-net-exchange", "limit": 20}, headers={"Authorization": f"Bearer {API_KEY}"}, ) for car in resp.json()["results"]: print(car["make"], car["model"], car["year"], car["price"])

Get an API key at my.carapis.com  and see the full API reference. Pricing is on the pricing page .

Use Cases

  • Import / export — chassis-code spec mapping and auction-sheet grades let importers vet exact trims of Japanese stock remotely. See import & export.
  • Pricing intelligence — precise trim/spec plus FOB price powers accurate landed-cost models for dealers.
  • Market research — track JDM export supply and spec mix at trim level. See market research.

Frequently asked questions