car-api2

Features

• VIN Decoder: Allows users to decode Vehicle Identification Numbers (VINs) and access specifications and trims.
• Years: Perform complex queries using JSON-encoded conditions to search for vehicles by year, make, model, trim, and more.
• Makes: Search for vehicle makes by name and year, pinpointing specific manufacturers and their offerings.
• Models: Search models based on criteria such as year, make, model, trim, or make ID with complex query support.
• Trims: Retrieve detailed information about vehicle trims with support for complex queries.

Tools

1. vindecoder

   Decodes Vehicle Identification Numbers. The result will include a list of specifications in the specs property and a list of all possible trims matching the VIN in the trims property. For non-paying users, all VINs for 2015-2020 models (e.g. 1GTG6CEN0L1139305) will be returned, otherwise data is hidden. Paying users have full data access.

2. years

   For complex queries you may use the json field to send an array of URL encoded JSON conditions, example: [{"field": "make", "op": "in", "val": ["Scion", "Tesla"]}] Allowed operators are: >, <, >=, <=, in, not in, like, not like, is null and not null. Allowed search fields are: year, make, model, trim, make_id, and make_model_id.

3. makes

   Search makes by name and year.

4. models

   Search models by year, make, model, trim or make_id. To include the models make in the description request with the query parameter as verbose=yes. For complex queries you may use the json field to send an array of URL encoded JSON conditions, example: `[{"field": "make", "op": "in", "val": ["Ford", "Acura"]}, {"field": "year", "op": ">=", "val": 2010}] Allowed json operators are: =, !=, >, <, >=, <=, in, not in, like, not like, not null, and is null. Allowed json search fields are: year, make, model, make_id, created, and modified.

5. trims

   To include additional information about the returned body (such as year, make, model and trim) request with the query parameter as verbose=yes. For complex queries you may use the json field to send an array of URL encoded JSON conditions, example: [{"field": "year", "op": ">=", "val": 2010}, {"field": "year", "op": "<=", "val": 2020}] Allowed operators are: >, <, >=, <=, in, not in, like, not like, is null and not null. Allowed json search fields are: year, make, model, trim, bodies.type, engines.cam_type, engines.cylinders, engines.drive_type, engines.engine_type, engines.fuel_type, engines.transmission, engines.valve_timing, engines.valves, make_id, make_model_id, make_model_trim_id, created, and modified.

6. trim_view

   Returns all data associated with the vehicle trim.

7. bodies

   To include additional information about the returned body (such as year, make, model and trim) request with the query parameter as verbose=yes. For complex queries you may use the json field to send an array of URL encoded JSON conditions, example: [{"field": "doors", "op": ">=", "val": 4}, {"field": "type", "op": "in", "val": ["SUV","Van"]}] See /api/vehicle-attributes for a complete list of vehicle attributes. Allowed operators are: >, <, >=, <=, in, not in, like, not like, is null and not null. Allowed json search fields are: year, make, model, trim, type, doors, make_id, make_model_id, and make_model_trim_id.

8. engines

   To include additional information about the returned body (such as year, make, model and trim) request with the query parameter as verbose=yes. For complex queries you may use the json field to send an array of URL encoded JSON conditions, example: [{"field": "horsepower_hp", "op": ">=", "val": 100}, {"field": "horsepower_hp", "op": "<=", "val": 300}] See /api/vehicle-attributes for a complete list of vehicle attributes. Allowed operators are: >, <, >=, <=, in, not in, like, not like, is null and not null. Allowed json search fields are: year, make, model, trim, fuel_type, engine_type, transmission, drive_type, cam_type, valve_timing, valves, horsepower_hp, size, cylinders, make_id, make_model_id, and make_model_trim_id.

9. exterior_colors

   To include additional information about the returned body (such as year, make, model and trim) request with the query parameter as verbose=yes. For complex queries you may use the json field to send an array of URL encoded JSON conditions, example: [{"field": "name", "op": "in", "val": ["red", "blue"]}] Allowed operators are: >, <, >=, <=, in, not in, like, not like, is null and not null. Allowed json search fields are: year, make, model, trim, name, rgb, make_id, make_model_id, and make_model_trim_i

10. interior_colors

    To include additional information about the returned body (such as year, make, model and trim) request with the query parameter as verbose=yes. For complex queries you may use the json field to send an array of URL encoded JSON conditions, example: [{"field": "name", "op": "in", "val": ["red", "blue"]}] Allowed operators are: >, <, >=, <=, in, not in, like, not like, is null and not null. Allowed json search fields are: year, make, model, trim, name, rgb, make_id, make_model_id, and make_model_trim_i

11. vehicle_attributes

    Returns all options for given attribute.

12. mileages

    To include additional information about the returned body (such as year, make, model and trim) request with the query parameter as verbose=yes. For complex queries you may use the json field to send an array of URL encoded JSON conditions, example: [{"field": "combined_mpg", "op": ">=", "val": 20}, {"field": "combined_mpg", "op": "<=", "val": 30}] Allowed operators are: >, <, >=, <=, in, not in, like, not like, is null and not null. Allowed json search fields are: year, make, model, trim, combined_mpg, epa_city_mpg, epa_highway_mpg, range_city, range_highway, make_id, make_model_id, and make_model_trim_id.