Global Car Specifications Database API

Enter brand, model and model year to get normalised specifications, EV battery and charging data, trim lists, vehicle images and manufacturer logos in one call.

We continuously consolidate global public model databases and manufacturer specifications, cleaning, standardising and modelling powertrain, dimensions, performance, fuel consumption and EV battery charging fields, delivered uniformly through a REST API across 60+ manufacturers and 5,000+ models.

No need to stitch together scattered model databases, images and logo assets yourself.

View API Docs

Enterprise solution enquiryJSON APIContinuously updated specifications

OverviewPowertrainDimensionsEV chargingImages and logos

Model search key 3

1 demo-ev Make (masked)

Data sources: Public model databases
Resolve: Normalised

2 seal_sport Model (masked)

Data sources: Manufacturer specifications
Resolve: Normalised

3 2024 Model year

Data sources: Model-year release
Classification: Classified

Master model entity parsed

Sample electric coupe
demo-ev seal_sport 2024

Power type: Battery electric (BEV)
Body type: Four-door sedan
Drivetrain: Dual-motor AWD
Max power: 390 kW (sample)
EV battery capacity: 82.5 kWh (net capacity, sample)
WLTP range: 520 km (sample)
Maximum DC charging: 270 kW (sample)
Data sources: Aggregates public model databases

5,000+Normalised model records

60+Manufacturers covered

99.9%API availability

<120msAverage response time

Model data is available everywhere, but it is far from being "ready for a product".

The real problem isn't whether the data exists, but how to turn information scattered across model databases, manufacturer spec sheets, image resources and logo libraries into standardised results your business systems can fetch in one call and maintain over time.

Raw data scattered across multiple sources Manufacturer specifications / model databases

001Brand and model librarymake / model

002Model years and trimsyear / trim

003Powertrain and dimension specsengine / dimension

004EV battery & chargingev battery

Model specification record aggregation One call · multi-source data Aggregated, normalised and delivered

01
Data is scattered
Brand, model, model year, trim, specifications, images and logos come from different sources with different naming and units, so your systems have to stitch them together.
02
Inconsistent units
Units for power, torque, range and battery capacity are inconsistent (kW / PS, km / mi, kWh / MJ), so using them in a product means converting field by field.
03
EV fields are new and messy
EV fields such as battery net capacity, WLTP/CLTC range, maximum DC charging power and connector type change fast and are defined inconsistently, making stable modelling hard.
04
Images and logos missing
Model databases often only have text specifications; vehicle images and manufacturer logos must be sourced and adapted separately, which is costly for front-end display.

From scattered public model data to a directly callable specification record

A brand + model + model year passes through six auditable stages to become stable, structured, linkable JSON.

Collect

Continuously consolidating global public model databases and manufacturer specifications

source.capture()

Clean

Unifies brand, model and field naming

parse · dedupe

Normalize

Unifies units, powertrain types and EV field naming

schema.map()

Relate

Links models, trims, images and logos

graph.link()

Aggregate

One call returns specs, EV, images and logos

aggregate.v1

Deliver

Delivered to your business systems via a stable REST API

json_api.v1

You don't have to maintain model database parsing, unit conversion or image/logo sourcing.Call the API and use the results directly.

One API covering the core car specification lookup scenarios

Unified REST API · JSON responses · Bearer token authentication. Model specification lookup is the core of the product, with the other capabilities built on the same data model.

Model specification lookup API

Foundation data for model libraries, trim comparison and valuation

Enter brand, model and model year to get normalised specifications: powertrain type, body style, engine/motor, power and torque, transmission, drivetrain, dimensions and weight, fuel/electricity consumption and EV battery charging data. One call aggregates multiple data types.

Power type
Dimensions and weight
Performance
EV battery
Charging power
Images and logos

Model libraries · trim comparison · used-car valuation · insurance claims · storefront specs

GET /v1/car-specs?make=demo-ev&model=seal_sport&year=2024

Static demo · Sample response200 OK

{
  "query": {
    "make": "demo-ev",
    "model": "seal_sport",
    "year": 2024
  },
  "data": {
    "make": "Sample EV",
    "model_name": "Sample coupe",
    "year": 2024,
    "body_style": "Four-door sedan",
    "drivetrain": "AWD",
    "power_kw": 390,
    "ev": {
      "battery_kwh_net": 82.5,
      "range_wltp_km": 520,
      "max_dc_kw": 270
    }
  },
  "source": "aggregated_public_catalog"
}

API 02

Brand / model / model-year enumeration API

Returns the supported brand, model and model-year lists for front-end dropdown filtering and building your own model library.

GET /v1/cars/makes JSON

Brand list60+ manufacturers enumerated

Models and model yearsExpand models and model years by brand

Front-end filteringData source for linked dropdowns

API 03

Trim / model-year list API

Returns the trim and model-year list for a model along with their specification differences, supporting trim comparison and SKU management.

GET /v1/cars/trims?make=demo-ev&model=seal_sport Trim lists · specification differences · model years

API 04

EV battery and charging data API

Returns EV battery net capacity, WLTP/CLTC range, maximum DC charging power, connector type and port location.

GET /v1/cars/ev?make=demo-ev&model=seal_sport&year=2024 Battery capacity · range · charging power · connector

API 05

Vehicle image API

Returns standardised vehicle image URLs (transparent PNG, multiple angles) ready for model libraries and storefront display.

GET /v1/cars/image?make=demo-ev&model=seal_sport&year=2024 Transparent PNG · multiple angles · production ready

API 06

Manufacturer logo API

Returns manufacturer logo (SVG) URLs for consistent display in brand filters, listings and comparison pages.

GET /v1/cars/logo?make=demo-ev SVG vector · brand marks · multi-scenario

This data can flow into your real business processes

Not another back office to open, but model specifications where model libraries, comparisons, valuations and claims work actually happen.

Used-car platforms / dealers

Automatically fills in model specifications, trims and images when listing vehicles, supporting trim comparison and accurate valuation.

Brand + model + model yearCar Specifications APIStructured vehicle listings

Exporting automakers / parts suppliers

Get specifications for mainstream global brands for competitive benchmarking, supporting overseas model libraries and parts fitment.

Competitor modelsSpecification lookup APIBenchmarking data

Model database apps / automotive media

Quickly build specification comparison, car-selection and content pages with normalised specs, images and logos.

Model dimensionEnumeration + image APIsCar selection experience

Insurance claims / auto underwriting

Uses precise model identification to match repair parameters and parts specifications, supporting claims and underwriting decisions.

Model identificationSpecification lookup APIClaims basis

Charging services / charge point operators

Uses EV battery capacity, charging power and connector type for charging compatibility checks and power recommendations.

EV modelsEV data APICharging recommendations

Leasing / fleet management

Use model specifications and model years for residual value assessment, fleet records and trim management.

Fleet modelsTrim list APIAsset records

Data comes from global public model databases and manufacturer specifications, organised item by item

The following is compiled from public model databasesExampleModel specifications (masked, not real vehicles) with the same field structure as live data; powertrain, dimensions and EV battery and charging fields are all normalised.

Model (masked)Power typeEV battery / range / charging

demo-ev seal_sport 2024Battery electric (BEV)82.5 kWh · 520 km · 270 kW

demo-gt taycan_like 2024Battery electric (BEV)71.0 kWh · 431 km · 270 kW

demo-suv family_7 2023Plug-in hybrid (PHEV)18.3 kWh · 110 km · 40 kW

demo-sedan commuter 2022Petrol (ICE)— · — · —

demo-pickup work_4x4 2024Petrol (ICE)— · — · —

The models above are masked samples (real field structure, demo values). Full coverage spans 60+ manufacturers and 5,000+ models across specifications, EV battery and charging, images and logos; the item-level detail is archived in car_specs_sample.json.

The Car Specifications API supports further analysis

EV battery capacity distribution
Charging power benchmarking
Body style share
Powertrain type trends
Model-year specification differences
Trim comparison matrix

The value of an API is more than "returning specifications to you"

GooFuture's core value lies before the data reaches the API: turning public data scattered across model databases, manufacturer specifications, images and logos into a model data model that is program-friendly, linkable and maintainable.

Aggregate

Multi-source in one response

Aggregates brand, model, specifications, EV, images and logos into a single model record, cutting repeated queries.

Multi-source → one record

Resolve

Unit normalisation

Unifies power, range and battery capacity units so systems can compare them directly.

Multiple units → unified fields

Structure

EV field standardisation

Unifies battery net capacity, WLTP/CLTC range, maximum DC charging power and connector type.

Heterogeneous fields → standard model

Assets

Images and logos

Provides standardised vehicle images (transparent PNG) and manufacturer logos (SVG), ready for the front end.

Text → visual assets

Update

Model-year sync

The model database keeps updating as manufacturers release model years, cutting your maintenance costs.

Source → sync

From enquiry to your first API call in just three steps

Code and responses are static samples. Your consultant will propose an integration plan based on data scope, call volume and delivery method.

01
Contact a consultant
Scan the QR code to add us on WeCom and tell us your business scenario, the data you need and your expected call volume.
02
Confirm the plan
Confirm endpoint scope, EV fields, image/logo delivery method and enterprise support needs.
03
Start integration
Get your API key and integration materials, then wire the JSON results into your model library, comparison or valuation product.

cURLResponse

curl "https://api.goofuture.com/v1/car-specs?make=demo-ev&model=seal_sport&year=2024" \
  -H "Authorization: Bearer YOUR_API_KEY"

Static demo · JSON response200 OK

{
  "data": {
    "make": "Sample EV",
    "model_name": "Sample coupe",
    "year": 2024,
    "body_style": "Four-door sedan",
    "power_kw": 390,
    "ev": {
      "battery_kwh_net": 82.5,
      "range_wltp_km": 520,
      "max_dc_kw": 270
    }
  }
}

From testing to production

Choose a plan by call volume, image/logo delivery, EV fields and enterprise support. Your consultant quotes based on your business needs.

Basic

For API testing and product validation

Contact a consultant

Monthly requests: 100
Core endpoints: Spec / enumeration lookup
Images and logos: —
Monitoring conditions: —

Standard

For small-team model libraries

Contact a consultant

Monthly requests: 10,000
Core endpoints: All specification lookups
Images and logos: Includes
Monitoring conditions: 10 conditions

Recommended plan

Professional

For used-car platforms / exporting automakers

Contact a consultant

Monthly requests: 50,000
Concurrency: Higher concurrency
EV fields: Full battery charging data
Data delivery: Webhook / CSV

Enterprise

For platforms, data companies and large enterprises

Contact a consultant

Monthly requests: High-volume usage
Images and logos: Bulk + CDN
Customisation: Field / dataset
Technical support: Enterprise technical support

The questions worth confirming before integrating a car specifications API

Straight answers on public model data, field definitions, images and logos, and commercial integration.

Much of the model data is public — why do I still need this API?

If you only need to look up a model occasionally, the manufacturer website or a public model database is enough. GooFuture is built for teams that need bulk lookups, system integration, unified fields and continuous updates — aggregating public data scattered across model databases, manufacturer specifications, images and logos into a model specification record you can get in one call.

Where does the data come from?

Data comes from global public model databases and manufacturer-published specifications (powertrain, dimensions, performance, fuel consumption and EV battery charging), plus the corresponding vehicle images and manufacturer logo assets. GooFuture collects, cleans, standardises, links and aggregates the raw data and delivers it via API; sample figures on this page are masked and represent no real vehicle.

How often is the data updated?

The model database is continuously updated as manufacturers release new model years. We sync after new models or model years are published; see the API documentation for exact frequency.

Do you support VIN lookup?

The car specifications database is organised primarily by brand + model + model year (and trim). If you need to resolve a model from a VIN, combine it with GooFuture's existing vehicle history / specification resolution capability (vehicle-history-api) to chain VIN → model → specifications.

Which fields are included in the EV battery and charging data?

EV data includes battery net capacity (battery_kwh_net), WLTP / CLTC range (range_*_km), maximum DC charging power (max_dc_kw), charging connector type and port location — with unified field definitions.

How do I use the vehicle images and logos?

The image API returns standardised vehicle image URLs (transparent PNG, multiple angles) and the logo API returns manufacturer logos (SVG vector). Both are ready to use in model libraries, comparison pages, stores and listings without processing assets yourself.

Can I integrate the data into my own model library / valuation product?

Yes. The API can be used in internal systems and integrated into used-car, model database app, automotive media, insurance claims and charging service products; commercial usage is governed by the applicable plan and service agreement.

Do you support agency partnerships with commission?

Yes. We provide the data, APIs and after-sales support; partners handle customer acquisition and account management, with revenue shared by customer call volume or customer count. Contact a consultant to confirm the terms.

You no longer stitch together model databases, images and logos yourself.

From collecting public model data to unit normalisation, EV field standardisation and image/logo linking — we handle it all. Your systems just call the API.

Enterprise consultant onboarding · REST API · JSON responses

Global Car Specifications Database API

Model search key 3

Master model entity parsed

Data is scattered

Inconsistent units

EV fields are new and messy

Images and logos missing

Collect

Clean

Normalize

Relate

Aggregate

Deliver

Model specification lookup API

Brand / model / model-year enumeration API

Trim / model-year list API

EV battery and charging data API

Vehicle image API

Manufacturer logo API

Used-car platforms / dealers

Exporting automakers / parts suppliers

Model database apps / automotive media

Insurance claims / auto underwriting

Charging services / charge point operators

Leasing / fleet management

The Car Specifications API supports further analysis

Multi-source in one response

Unit normalisation

EV field standardisation

Images and logos

Model-year sync

Contact a consultant

Confirm the plan

Start integration

You no longer stitch together model databases, images and logos yourself.