What Car Data APIs Are & How They Power Automotive Businesses

Introduction

The automotive industry generates massive amounts of data every day — from manufacturing specifications to ownership records, accident histories, and insurance claims. For businesses that need to access this vehicle information at scale, manual lookups are not practical. A single dealership processing 200 trade-ins per month cannot afford to spend 15 minutes per vehicle on manual VIN checks. This is where car data API integration becomes essential infrastructure.

Whether you're running a dealership, importing cars from China, building an automotive marketplace, or developing insurance solutions, integrating vehicle data APIs into your systems can automate workflows, reduce errors, and deliver instant car info that drives better business decisions. The global automotive data market generates billions of data points daily — and businesses that tap into this programmatically gain a measurable competitive advantage.

What Is a Car Data API?

An API (Application Programming Interface) is a set of protocols that allows different software applications to communicate with each other. A car data API specifically provides programmatic access to vehicle-related information, enabling businesses to retrieve detailed data about any vehicle using identifiers like the VIN (Vehicle Identification Number). Think of it as a bridge between your business software and comprehensive vehicle databases — your system sends a VIN, and the API returns structured vehicle info within seconds.

When you implement car data API integration, your systems can automatically query comprehensive databases and receive structured JSON responses containing vehicle specifications, history records, market valuations, insurance claims, and service records — all without manual intervention. A single API call replaces what used to require phone calls, manual database searches, and cross-referencing multiple sources.

The Chinese Vehicle Data Gap

Here is the problem most automotive businesses face: standard vehicle data APIs cover North American and European markets well, but they have zero coverage of Chinese vehicle history. With Chinese manufacturers like BYD, Geely, Great Wall (Haval, Tank), Changan, Chery, NIO, Xpeng, and Li Auto rapidly expanding into global markets, this data gap creates real business risk. A dealer importing a used BYD Song Plus cannot verify its accident history, insurance claims, odometer readings, or service records through any conventional API.

International VIN services cover US and European markets but not China. Standard VIN decoders can identify that a vehicle is a BYD or Geely, but they cannot access the Chinese insurance databases (PICC, Ping An, CPIC) or service records from authorized dealers in China. The China Vehicle History API was built specifically to fill this gap — it is the only API that provides accident history, insurance claims, mileage chronology, and maintenance records sourced directly from Chinese databases.

Quick Start: Your First API Request

The China Vehicle History API uses standard REST protocol. All requests and responses are in JSON format. Authentication is handled through an API key in the Authorization header. Here is the base URL and a sample request to decode a Chinese VIN:

Base URL and Authentication

Base URL: https://api.chinavehiclehistory.com/v1
Authorization: Bearer YOUR_API_KEY
Content-Type: application/json

API keys are issued after registration in the partner program. Access is provided to B2B clients including dealerships, car import companies, automotive marketplace developers, and fleet management platforms. Contact us via WhatsApp or Telegram to get started.

First Request: Decode a Chinese VIN (cURL)

curl -X POST https://api.chinavehiclehistory.com/v1/decode \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"vin": "LGXCE6CB9P0123456"}'

Sample JSON Response

{
  "success": true,
  "data": {
    "vin": "LGXCE6CB9P0123456",
    "brand": "BYD",
    "model": "Song Plus DM-i",
    "year": 2023,
    "plant": "Shenzhen",
    "engine": "BYD476ZQB",
    "engine_volume": "1.5L",
    "fuel_type": "PHEV",
    "transmission": "E-CVT",
    "body_type": "SUV",
    "color": "White",
    "power_kw": 81,
    "battery_capacity_kwh": 18.3,
    "curb_weight_kg": 1780,
    "made_in": "China"
  }
}

That single API call returns 15+ data points about the vehicle — brand, model, year, engine specifications, fuel type, transmission, body type, dimensions, weight, and manufacturing plant. This is the car specs data that powers inventory listings, import compliance checks, and customs duty calculations. The response arrives in milliseconds, replacing what would otherwise require manual research across multiple Chinese-language sources.

API Endpoint Reference: 6 Endpoints for Complete Vehicle Data

The China Vehicle History API provides 6 endpoints covering the full vehicle check cycle — from VIN decode to complete service history retrieval. Each endpoint returns structured JSON data that integrates directly into your business systems. Here is the complete endpoint reference with request and response examples.

1. POST /v1/decode — VIN Decode (Basic Plan)

Returns factory specifications for a Chinese vehicle by VIN: brand, model, year, engine, transmission, body type, weight, fuel type, and manufacturing plant. This is a synchronous request — the response arrives instantly. Use this endpoint for inventory listing, customs declarations, and car specs lookups.

// Request
POST /v1/decode
{
  "vin": "LGXCE6CB9P0123456",
  "email": "partner@example.com",
  "plan": "basic"
}

// Response
{
  "success": true,
  "data": {
    "brand": "BYD",
    "model": "Song Plus DM-i",
    "series": "Song Plus",
    "year": 2023,
    "price_cny": 159800,
    "engine": "BYD476ZQB 1.5L",
    "power_kw": 81,
    "transmission": "E-CVT",
    "fuel_type": "PHEV",
    "body_type": "SUV",
    "dimensions": "4705x1890x1680mm",
    "curb_weight_kg": 1780,
    "fuel_consumption_l100km": 4.4,
    "plant": "Shenzhen"
  },
  "fromCache": false
}

2. POST /v1/history — Full Vehicle History (Standard Plan)

Returns car specs plus insurance history from Chinese databases: accident records, insurance claims (PICC, Ping An, CPIC), mileage chronology, number of previous owners, theft status, and lien status. This is the vehicle information endpoint most businesses need — it covers the data gap that standard international APIs cannot fill.

// Request
POST /v1/history
{
  "vin": "LGXCE6CB9P0123456",
  "email": "partner@example.com",
  "plan": "standard"
}

// Response (excerpt)
{
  "success": true,
  "data": {
    "vehicleInfo": { "..." : "..." },
    "insuranceInfo": {
      "total_claims": 2,
      "claims": [
        {
          "date": "2024-03-15",
          "type": "collision",
          "amount_cny": 8500,
          "description": "Rear bumper damage",
          "insurer": "PICC"
        },
        {
          "date": "2024-09-22",
          "type": "minor_scratch",
          "amount_cny": 1200,
          "description": "Left door scratch",
          "insurer": "Ping An"
        }
      ],
      "mileage_records": [
        {"date": "2023-06-01", "km": 5200},
        {"date": "2024-01-15", "km": 18400},
        {"date": "2024-09-22", "km": 34100}
      ],
      "owners_count": 1,
      "theft_status": "clear",
      "lien_status": "clear"
    }
  }
}

The mileage chronology is especially valuable for importers. By comparing recorded mileage at different dates, you can detect odometer rollbacks — a common issue with used vehicles imported from China. The insurance claims section shows every recorded incident with the claim amount, damage description, and insurer name, giving you a complete accident history that no other vehicle data API provides for Chinese cars.

3. POST /v1/premium — Full Report with Service History (Premium Plan, Async)

Includes everything from the Standard plan plus maintenance records from authorized dealers and independent service centers, and recall campaign status. This is an asynchronous request — the API returns an order_id that you use to check status and retrieve results. It also supports webhook notifications via a callback_url parameter, so your system gets notified automatically when the report is ready.

// Request
POST /v1/premium
{
  "vin": "LGXCE6CB9P0123456",
  "email": "partner@example.com",
  "plan": "premium",
  "engine": "BYD476ZQB",
  "callback_url": "https://yoursite.com/webhook/report-ready"
}

// Response
{
  "success": true,
  "order_id": "ord_abc123def456",
  "status": "processing",
  "message": "Report is being generated. Poll /v1/premium/status/ord_abc123def456 or wait for webhook."
}

4. GET /v1/premium/status/{orderId} — Check Premium Report Status

Checks the processing status of an asynchronous premium report. Returns the current status (pending, processing, completed, or failed) and a progress percentage. Use this endpoint if you prefer polling over webhook notifications.

// Request
GET /v1/premium/status/ord_abc123def456?email=partner@example.com

// Response
{
  "success": true,
  "status": "completed",
  "progress": 100
}

5. GET /v1/premium/results/{orderId} — Retrieve Premium Report

Retrieves the completed premium report after processing finishes. The response includes vehicleInfo, insuranceInfo, and a maintenanceRecords array with entries from authorized service centers — including service date, mileage at service, work performed, parts used, and whether OEM parts were installed.

// Request
GET /v1/premium/results/ord_abc123def456?email=partner@example.com

// Response (excerpt)
{
  "success": true,
  "data": {
    "vehicleInfo": { "..." : "..." },
    "insuranceInfo": { "..." : "..." },
    "maintenanceRecords": [
      {
        "date": "2023-08-10",
        "mileage_km": 10200,
        "service_type": "Scheduled maintenance",
        "items": ["Engine oil change", "Oil filter", "Air filter"],
        "dealer": "BYD Shenzhen Authorized Service",
        "oem_parts": true
      },
      {
        "date": "2024-05-20",
        "mileage_km": 25600,
        "service_type": "Scheduled maintenance",
        "items": ["Brake fluid replacement", "Cabin air filter", "Battery health check"],
        "dealer": "BYD Guangzhou Service Center",
        "oem_parts": true
      }
    ]
  }
}

6. POST /v1/lookup/plate — Find VIN by Chinese License Plate

Finds the VIN of a vehicle using its Chinese license plate number. This endpoint is useful when a client or auction listing provides a plate number but not the VIN. Once you have the VIN, you can use any of the other endpoints to retrieve full vehicle information.

// Request
POST /v1/lookup/plate
{
  "license_plate": "京A12345",
  "vehicle_type": "02"
}

// Response
{
  "success": true,
  "vin": "LGXCE6CB9P0123456"
}

Code Examples: Python, Node.js, and PHP

The following API examples show how to integrate Chinese vehicle data into your application using popular programming languages. Each example demonstrates VIN decoding and history retrieval — the two most common API calls for automotive businesses.

Python Example

import requests

API_KEY = "YOUR_API_KEY"
BASE_URL = "https://api.chinavehiclehistory.com/v1"

def decode_vin(vin: str) -> dict:
    response = requests.post(
        f"{BASE_URL}/decode",
        headers={
            "Authorization": f"Bearer {API_KEY}",
            "Content-Type": "application/json"
        },
        json={
            "vin": vin,
            "email": "partner@example.com",
            "plan": "basic"
        }
    )
    response.raise_for_status()
    return response.json()

def get_history(vin: str) -> dict:
    response = requests.post(
        f"{BASE_URL}/history",
        headers={
            "Authorization": f"Bearer {API_KEY}",
            "Content-Type": "application/json"
        },
        json={
            "vin": vin,
            "email": "partner@example.com",
            "plan": "standard"
        }
    )
    response.raise_for_status()
    return response.json()

# Usage
result = decode_vin("LGXCE6CB9P0123456")
print(f"Brand: {result['data']['brand']}")
print(f"Model: {result['data']['model']}")
print(f"Year: {result['data']['year']}")

Node.js Example

const API_KEY = "YOUR_API_KEY";
const BASE_URL = "https://api.chinavehiclehistory.com/v1";

async function decodeVin(vin) {
  const response = await fetch(`${BASE_URL}/decode`, {
    method: "POST",
    headers: {
      "Authorization": `Bearer ${API_KEY}`,
      "Content-Type": "application/json"
    },
    body: JSON.stringify({
      vin,
      email: "partner@example.com",
      plan: "basic"
    })
  });

  if (!response.ok) {
    throw new Error(`API error: ${response.status}`);
  }

  return response.json();
}

async function getHistory(vin) {
  const response = await fetch(`${BASE_URL}/history`, {
    method: "POST",
    headers: {
      "Authorization": `Bearer ${API_KEY}`,
      "Content-Type": "application/json"
    },
    body: JSON.stringify({
      vin,
      email: "partner@example.com",
      plan: "standard"
    })
  });

  if (!response.ok) {
    throw new Error(`API error: ${response.status}`);
  }

  return response.json();
}

// Usage
const result = await decodeVin("LGXCE6CB9P0123456");
console.log(`Brand: ${result.data.brand}`);
console.log(`Model: ${result.data.model}`);

PHP Example

<?php

$apiKey = "YOUR_API_KEY";
$baseUrl = "https://api.chinavehiclehistory.com/v1";

function decodeVin(string $vin): array {
    global $apiKey, $baseUrl;

    $ch = curl_init("$baseUrl/decode");
    curl_setopt_array($ch, [
        CURLOPT_POST => true,
        CURLOPT_RETURNTRANSFER => true,
        CURLOPT_HTTPHEADER => [
            "Authorization: Bearer $apiKey",
            "Content-Type: application/json"
        ],
        CURLOPT_POSTFIELDS => json_encode([
            "vin" => $vin,
            "email" => "partner@example.com",
            "plan" => "basic"
        ])
    ]);

    $response = curl_exec($ch);
    $httpCode = curl_getinfo($ch, CURLINFO_HTTP_CODE);
    curl_close($ch);

    if ($httpCode !== 200) {
        throw new Exception("API error: $httpCode");
    }

    return json_decode($response, true);
}

// Usage
$result = decodeVin("LGXCE6CB9P0123456");
echo "Brand: " . $result["data"]["brand"] . "\n";
echo "Model: " . $result["data"]["model"] . "\n";

Error Handling: HTTP Status Codes

The API returns standard HTTP status codes. Your application should handle these responses to ensure reliable operation and a good user experience:

• 200 OK — Request completed successfully. Vehicle data is in the response body.
• 400 Bad Request — Invalid VIN (not 17 characters) or missing required fields (vin, email, plan). Validate inputs before sending API calls.
• 401 Unauthorized — Invalid or missing API key in the Authorization header. Check that your key is active and correctly formatted.
• 404 Not Found — Vehicle not found in the database for the given VIN or license plate. This can happen with very new vehicles not yet indexed.
• 429 Too Many Requests — Rate limit exceeded. Implement exponential backoff before retrying the request.
• 500 Internal Server Error — Server-side error. Retry the request after 5-10 seconds. If the error persists, contact support.

How Car Data API Integration Powers Different Industries

The versatility of car data API integration makes it valuable across multiple sectors within the automotive ecosystem. Here are the most common integration scenarios:

Car Importers and Auction Buyers

Companies importing vehicles from China face the biggest data gap in the automotive industry. When a buying agent in China sends a VIN from an auction listing, the importer needs instant verification before committing to the purchase. API integration automates this entire workflow:

• Pre-purchase smart vehicle check: Agent sends VIN from Chinese auction, API automatically returns accident history, mileage records, and insurance claims within seconds — no manual research needed.
• Odometer verification: Compare mileage records across multiple dates to detect rollbacks before buying. A vehicle showing 30,000 km at auction but 55,000 km in insurance records six months earlier is an immediate red flag.
• Batch processing: Import companies checking 50-200 vehicles per week can send VINs programmatically and receive reports automatically, eliminating the bottleneck of manual checks.
• Risk scoring: Use accident claim amounts and frequency to automatically flag high-risk vehicles that should be avoided or priced accordingly.

Dealer Management Systems (DMS)

Dealer management systems are the central nervous system of modern dealerships — handling inventory, customer relationships, financing, and sales in one platform. Integrating a Chinese vehicle data API into your DMS adds a capability that no standard dealer management software currently provides:

• Trade-in workflow: When a customer brings in a Chinese vehicle as a trade-in, the sales manager scans the VIN and the DMS automatically pulls the full history report. No switching between systems, no manual lookups.
• Inventory enrichment: Every Chinese vehicle in your lot gets complete specifications auto-populated — engine, transmission, fuel type, dimensions, weight, battery capacity for EVs — directly from the API into your dealer management system.
• CRM integration: Connect the API to your CRM (Salesforce, HubSpot, or industry-specific platforms). When a new deal is created with a Chinese vehicle VIN, the system automatically attaches the history report to the customer record.
• Compliance documentation: For import dealers, the API provides the exact technical specifications needed for customs declarations and emissions compliance — engine displacement, power output, curb weight, fuel consumption — in a structured format ready for regulatory forms.

Automotive Marketplaces

Online vehicle marketplaces that list Chinese imports can differentiate their platform by offering verified vehicle data that competitors lack:

• Listing enrichment: Sellers enter a VIN and the platform auto-populates all vehicle specifications, reducing listing time and eliminating errors.
• Verified history badges: Display a 'Chinese History Verified' badge on listings that have been checked through the API, increasing buyer trust and click-through rates.
• Fraud prevention: Cross-reference seller-provided details against API data. If a seller claims 'no accidents' but the API shows two insurance claims, the platform can flag the listing.
• Vehicle management application: Build mobile tools that let dealers manage inventory, run VIN checks, and update listings from their phone using the same API backend.

Insurance Companies

Insurers writing policies for imported Chinese vehicles face a unique challenge: they cannot assess risk without knowing the vehicle's history in China. A BYD Han that looks clean on a local inspection may have had three insurance claims in China for collision damage. The API solves this:

• Risk assessment: Access the full Chinese insurance history — number of claims, claim types (collision, theft, flood), claim amounts, and insurers involved. This data directly feeds into underwriting models.
• Claims validation: When processing a claim on an imported Chinese vehicle, verify the vehicle's pre-import condition. A claim for 'pre-existing damage' can be validated against Chinese insurance records.
• Total loss calculations: Use the original Chinese retail price, mileage history, and accident records to calculate fair market value for total loss settlements.
• Fleet policy pricing: For companies insuring fleets of Chinese EVs (increasingly common with BYD commercial vehicles), batch-check every VIN to set accurate fleet premiums.

Fleet Management and Connected Car Platforms

Fleet management software for companies operating Chinese EVs needs reliable vehicle data for maintenance planning, total cost of ownership analysis, and resale timing. Chinese EV fleets are growing rapidly in ride-hailing, delivery, and corporate transport:

• Asset tracking: Maintain complete specification data for every vehicle in the fleet — battery capacity, charging specs, range, and weight — pulled directly from the API.
• Maintenance scheduling: Use service history from the API to understand each vehicle's maintenance baseline and schedule preventive service at the right intervals.
• TCO analysis: Combine purchase price, mileage data, service costs, and insurance claims to calculate true total cost of ownership for Chinese EVs versus competitors.
• Resale planning: Track mileage accumulation rates and service history quality to determine optimal replacement timing for each vehicle in the fleet.
• Connected car data: For fleets using telematics and car black box devices, API data supplements OBD-II readings with factory specifications — ensuring your vehicle management application has complete data from both real-time sensors and historical records.

Customs Brokers and Compliance

Customs brokers handling Chinese vehicle imports need precise technical specifications for duty calculations, emissions compliance, and safety certification. Manual specification lookup for Chinese vehicles is slow and error-prone because many Chinese manufacturer databases are only available in Mandarin:

• Duty calculation: Retrieve exact engine displacement, power output, curb weight, and fuel type — the parameters that determine import duty rates in most countries.
• Emissions compliance: Get fuel consumption and emissions data to verify compliance with local standards (Euro 6, EPA Tier 3, etc.) before the vehicle arrives.
• Safety certification: Access factory specifications including dimensions, weight, and equipment list for safety certification applications.
• Batch processing: Brokers handling multiple vehicles per shipment can decode all VINs in a single batch rather than researching each vehicle individually.

Comparison with Other Vehicle Data APIs

Several vehicle data APIs exist on the international market. None of them provide Chinese vehicle history data — accident records, insurance claims, mileage chronology, and service records from Chinese sources. Here is how they compare:

• Standard international VIN decoders: Cover US and European vehicle specifications well. Can identify Chinese brands by VIN prefix but cannot access any Chinese history data (accidents, insurance, mileage, service).
• Vincario API: European service with good documentation. Covers Chinese vehicle specifications through CATARC data, but does NOT include history (accidents, mileage, owners).
• 17VIN: Chinese specifications and parts catalog with CATARC data. Does NOT include vehicle history (accidents, insurance claims, service records).
• China Vehicle History API: The only API with history data from Chinese databases — accident records, insurance claims (PICC, Ping An, CPIC), mileage chronology, service history from authorized dealers, ownership count, theft and lien status.

Benefits of Car Data API Integration

Implementing car data API integration delivers measurable advantages for automotive businesses dealing with Chinese vehicles:

• Operational Efficiency: Automating data retrieval eliminates manual lookups that consume staff time. What once took 15-20 minutes per vehicle now happens in seconds, allowing teams to focus on higher-value activities like negotiating deals and serving customers.
• Data Accuracy: APIs pull vehicle information directly from Chinese insurance databases and manufacturer records, eliminating transcription errors and language barriers that occur with manual research on Chinese-language websites.
• Scalability: Whether you process ten vehicles or ten thousand per day, API integration scales effortlessly. An import company checking 200 vehicles per week uses the same integration as one checking 20 — the only difference is volume.
• Competitive Advantage: Dealers and importers with instant access to Chinese vehicle history can make faster purchasing decisions at auctions, provide transparent reports to buyers, and identify hidden problems that competitors without this data will miss entirely.
• Cost Reduction: At $16-20 per report through the API versus the hours of manual research required to piece together Chinese vehicle history from multiple sources, the ROI is immediate. A single avoided bad purchase pays for hundreds of API queries.

API Pricing and Plans

The China Vehicle History API is available through three pricing tiers based on monthly volume. All plans include full API access to every endpoint — the difference is per-report cost, which decreases with volume:

• Basic ($20/report) — Up to 100 requests per month. Full API access to all 6 endpoints. Standard support via WhatsApp and Telegram. Best for small dealerships and individual importers testing the service.
• Professional ($18/report) — 100 to 500 requests per month. Full API access with priority support. Best for established import companies and mid-size dealerships with steady Chinese vehicle volume.
• Enterprise ($16/report) — 1,000+ requests per month. Full API access with a dedicated account manager and custom integration support. Best for large dealer groups, marketplaces, and fleet operators.

For high-volume operations or custom enterprise requirements, contact us to discuss tailored pricing. Bulk discounts are available for companies processing large batches of vehicles from Chinese auctions.

Choosing the Right Vehicle Data API Provider

Not all vehicle data APIs are created equal. When evaluating providers for car data API integration, ask these questions before committing:

• Vehicle Database Coverage: The most important factor. Ensure the API covers the vehicle markets you serve. For businesses dealing with Chinese vehicles, verify that the provider has actual Chinese source data — not just VIN prefix decoding. Ask specifically: does the API return accident history, insurance claims, and service records from Chinese databases?
• Data Quality and Freshness: Request sample reports for VINs you already know the history of. Compare the API response against what you know. The best APIs aggregate data from multiple sources and update their vehicle database regularly.
• Integration Support: Look for well-documented APIs with clear examples in your programming language. Good documentation with request/response samples reduces development time from weeks to days.
• Pricing Transparency: Understand the pricing model — per-query, subscription, or tiered by volume. Calculate expected costs based on your projected usage. Watch for hidden fees like setup costs, minimum commitments, or charges for failed lookups.
• Reliability and Performance: For mission-critical integrations (like auction bidding systems where decisions happen in minutes), verify uptime guarantees and response times. Ask about the provider's infrastructure and redundancy.

Getting Started: 5 Steps to Integration

Implementing car data API integration typically follows these steps. Most teams complete the integration within 1-2 weeks:

• Step 1: Evaluate Data Quality — Start with a free VIN decode on our website. Test with VINs of Chinese vehicles you already know to verify the data matches reality. This takes 5 minutes and gives your team confidence before writing any code.
• Step 2: Get API Access — Contact us via WhatsApp or Telegram to receive your API key. Tell us about your business, expected volume, and integration plans so we can recommend the right tier.
• Step 3: Test with Postman or cURL — Use the code examples in this guide to send test API calls. Verify that responses match your expected data structure and that error handling works correctly.
• Step 4: Build the Integration — Connect the API to your existing systems (DMS, CRM, marketplace, or custom application). Use the Python, Node.js, or PHP examples as starting points. Most integrations require 2-5 days of development time.
• Step 5: Deploy and Monitor — Launch the integration, monitor API call volumes, response times, and error rates. Set up alerts for 429 (rate limit) or 500 (server error) responses so your team can respond quickly.

Frequently Asked Questions

What is a car data API?

A car data API is a programmatic interface that lets your software retrieve vehicle information automatically using a VIN (Vehicle Identification Number). Instead of manually looking up vehicle specs, history, and records on websites, your system sends a VIN to the API and receives structured data back in JSON format — ready to display, store, or process in your application.

Which Chinese vehicle brands are supported?

All major Chinese manufacturers are supported: BYD, Geely, Great Wall (Haval, Tank, Poer), Changan, Chery (Tiggo, Omoda, Jaecoo), GAC, SAIC (MG), Zeekr, NIO, Xpeng, Li Auto, Voyah, Dongfeng, FAW, BAIC, Jetour, Deepal, and Avatr. The API also covers foreign-brand vehicles manufactured in Chinese factories (parallel imports like Volkswagen, Toyota, and BMW models built in China).

Can I try the API before purchasing?

Yes. Start with a free VIN decode on our website to evaluate the data quality and see what information is returned. For API access testing, contact us and we will provide test requests so your development team can verify the integration before committing to a paid plan.

What is the difference between the API and manual VIN checks on the website?

The data is identical — same sources, same vehicle database, same level of detail. The difference is access method. Through the website, you check one VIN at a time manually. Through the API, your systems check VINs programmatically and automatically — when a new vehicle arrives in inventory, when a deal is created in your CRM, or when a customer submits a VIN on your marketplace. The API is designed for businesses processing 50 or more vehicles per month.

Does the API support webhooks for async reports?

Yes. When requesting a Premium report (which includes service history and takes longer to process), you can pass a callback_url parameter. The API sends a POST request to your URL when the report is ready, eliminating the need to poll the status endpoint repeatedly. This is the recommended approach for production integrations.

How long does integration take?

Most development teams complete the integration in 1-2 weeks. The API uses standard REST conventions with JSON requests and responses, so any developer familiar with REST APIs can integrate it quickly. The Python, Node.js, and PHP code examples in this guide provide ready-to-use starting points that reduce development time further.

How fresh is the vehicle data?

Vehicle specifications are sourced from manufacturer databases and updated when new models are released. Insurance and accident history is sourced from Chinese insurance companies (PICC, Ping An, CPIC) and reflects the most recent records available in those databases. Service history from authorized dealers is updated as new maintenance records are filed.

Can I search by license plate instead of VIN?

Yes. The POST /v1/lookup/plate endpoint accepts a Chinese license plate number and returns the corresponding VIN. This is useful when auction listings or client inquiries provide a plate number but not the VIN. Once you have the VIN, you can use any other endpoint to retrieve full vehicle information and history.

How to Get API Access

Contact us via WhatsApp or Telegram to receive your API key and discuss the right pricing tier for your business. Tell us about your use case — whether you are a dealership, import company, marketplace, fleet operator, or software developer — and your expected monthly volume. We will set you up with the appropriate plan and provide onboarding support to get your integration live as quickly as possible.