Accurate Vehicle Data. Seamless Integration. Smarter Commerce.

Overview

The Vehicle Data API provides programmatic access to a comprehensive vehicle database designed for automotive eCommerce, auto parts businesses, catalog applications, and custom software integrations.

The API uses a progressive lookup approach that allows applications to discover valid vehicle combinations step by step:

Year → Make → Model → Vehicle Specifications

This approach helps applications avoid incorrect assumptions about vehicle Make, Model, and Year while providing developers with predictable JSON responses through a standard REST API.

The API currently provides detailed vehicle specifications across 22 vehicle data fields, including engine information, drivetrain, body type, transmission, fuel type, trim, submodel, and other vehicle attributes.

Vehicle Specification Data fields

Vehicle Identity	Engine & Performance	Drivetrain & Fuel
Vehicle Display Name	Engine	Transmission
Make	Engine Block Type	Drive Type
Model	Engine Cylinders	Fuel_Type
Year	Cylinder Type Name	Classification & Cataloging
Trim	Engine CC	KBB_MODEL
Sub model	Engine CID	Parts Model
Body	Engine Liter Display	Region
Number of Doors	Aspiration

Business Value

Improve Vehicle Fitment Accuracy

Give customers a reliable way to identify their vehicle before selecting vehicle-specific products and parts.

Reduce Incorrect Orders and Returns

Accurate vehicle identification helps minimize purchases based on incorrect Make, Model, or Year combinations.

Eliminate Hard-Coded Vehicle Lists

Applications can retrieve current vehicle information directly through the API instead of maintaining large, manually managed vehicle lookup tables.

Improve the Shopping Experience

Power vehicle selectors, parts finders, compatibility tools, catalog filters, and vehicle-specific product experiences.

Reduce Development and Maintenance Effort

Developers can integrate with a structured API rather than building and maintaining their own vehicle database infrastructure.

Build for Scale

The API architecture is designed to support growing eCommerce catalogs, applications, and customer usage with API-key authentication and per-client rate limiting.

Features

• Progressive vehicle lookup — Year → Make → Model → Specifications
• Get all available vehicle Years
• Get available Makes for a selected Year
• Get available Models for a selected Year and Make
• Search detailed vehicle specifications using Year, Make, and Model
• 22 vehicle specification data fields
• Canonical vehicle Make values
• Case-insensitive Make input
• Clean JSON-formatted responses
• REST API architecture
• Secure Bearer API-key authentication
• Per-client API rate limiting
• X-RateLimit-Limit and X-RateLimit-Remaining response headers
• Required-parameter validation
• Four-digit Year validation
• Wildcard protection
• Clear HTTP error responses
• HTTP 429 response when the configured rate limit is exceeded
• Demo environment for integration testing
• Developer documentation with practical integration examples

How It Works

The API is designed around a simple progressive lookup process.

Step 1 — Get Available Years

GET /rest/V1/vehicleapi/years

The application retrieves the available vehicle years.

Step 2 — Get Makes

After the customer selects a Year:

GET /rest/V1/vehicleapi/makes?year=2025

The API returns the Makes available for that Year.

Step 3 — Get Models

After the customer selects a Make:

GET /rest/V1/vehicleapi/models?year=2025&make=Toyota

The API returns the valid Models for that Year and Make.

Step 4 — Get Vehicle Specifications

After the customer selects a Model:

GET /rest/V1/vehicleapi/search?year=2025&make=Toyota&model=Camry

The API returns the matching vehicle configurations and specifications.

Complete Workflow

Year
  ↓
Make
  ↓
Model
  ↓
Vehicle Specifications

This progressive approach is particularly useful for automotive applications because it prevents the application from having to guess whether a particular Year/Make/Model combination exists.

Request

curl -i \
  "https://mage-extensions-themes.com/rest/V1/vehicleapi/search?make=Honda&model=Civic&year=2025" \
  -H "Authorization: Bearer YOUR_API_KEY"

Response

{
    "success": true,
    "count": 11,
    "has_more": false,
    "data": [
        {
            "ymm_id": "6072792945",
            "make": "Honda",
            "model": "Civic",
            "year": "2025",
            "engine": "2.0L 1993CC 122Cu. In. l4 GAS DOHC Naturally Aspirated",
            "submodel": "Sport",
            "trim": "Sport Hatchback 4-Door",
            "body": "Hatchback",
            "cylinder_type": "DOHC",
            "drive_type": "FWD",
            "engine_block_type": "L",
            "engine_cc": "1993",
            "engine_cid": "122",
            "engine_cylinders": "4",
            "engine_liter_display": "2.0L",
            "transmission": "Automatic",
            "fuel_type": "GAS",
            "vehicle_display_name": "Honda Civic 2025 Sport",
            "number_of_doors": "4",
            "aspiration": "Naturally Aspirated",
            "parts_model": "Civic",
            "market_region": "1|2"
        }
    ]
}

All matching vehicle configurations are returned up to the endpoint limit. has_more indicates whether additional matching records exist beyond the returned set.

Merchant Benefits

Better Customer Experience

Provide customers with an intuitive vehicle-selection process before they browse compatible products.

Fewer Fitment Mistakes

Use structured vehicle data to improve product compatibility and reduce incorrect purchases.

Faster Development

Integrate vehicle lookup functionality through a ready-to-use REST API instead of developing your own vehicle database system.

Platform Flexibility

The API can be integrated with Magento, other eCommerce platforms, catalog applications, middleware, and custom software.

Developer Friendly

Standard HTTP requests, JSON responses, Bearer authentication, clear error responses, and practical code examples make integration straightforward.

Secure API Access

API keys can be individually managed and controlled, with configurable request limits for each client.

Scalable Architecture

The API separates authentication, rate limiting, and vehicle data services, providing a foundation for future API capabilities.

API Access

The production API is available at:

https://mage-extensions-themes.com/rest/V1/vehicleapi

A Demo environment is also available for integration testing:

https://demo.mage-extensions-themes.com/rest/V1/vehicleapi

A Demo API key is provided separately and is not published on the product page.

User Guide

Complete technical documentation is available in the Vehicle Data API User Guide.

The guide includes:

• API overview
• Authentication
• Production and Demo URLs
• Progressive API workflow
• Endpoint documentation
• Request and response examples
• Error handling
• Rate limiting
• cURL examples
• PHP example
• Python example
• JavaScript example
• Postman integration guidance
• Integration best practices
• Future API capabilities

[View Vehicle Data API User Guide →]
Vehicle Data API User Guide

Support

Global eCom Team provides support for Vehicle Data API customers.

Support includes assistance with:

• API authentication
• API-key configuration
• Endpoint usage
• API integration
• Request/response handling
• Rate-limit questions
• General API implementation questions

Need Assistance? We can help.

1. Looking for quick help using Live chat? – Get Instant Help
2. Ask questions via contact form? – Contact us
3. Need help with API setup? Our tech team is available to help – Support Ticket