License plate API: how it works and why you should use it

The license plate is the first visible identifier on any vehicle. For automotive professionals, being able to query a plate and instantly receive the vehicle's complete data is a tremendous productivity gain. That is exactly what a license plate API delivers.

License plate formats in France

France has had two main registration systems, and both still coexist in the current vehicle fleet.

The SIV system (since 2009)

The Vehicle Registration System (SIV), introduced on 15 April 2009, assigns each vehicle a permanent number in the format AA-123-AA. This number stays with the vehicle throughout its lifetime, regardless of ownership or location changes. The series is national and chronological, starting from AA-001-AA and progressing sequentially.

The SIV format uses two letters, three digits and two letters, separated by hyphens. Certain letters are excluded to avoid confusion: I (confused with 1), O (confused with 0) and U (confused with V).

The legacy FNI system

The National Registration File used a department-based format: 1234 AB 75 (number + letters + department). This system is obsolete for new registrations, but millions of vehicles still carry these plates. The API must therefore handle both formats.

For a full history of plate formats, see our article on SIV and FNI plate formats.

How does the license plate API work?

The AutomotivAPI license plate API queries the Ministry of the Interior's Vehicle Registration System (SIV). Access to this database is strictly regulated: only approved operators may access it. AutomotivAPI holds this approval, ensuring official and up-to-date data.

The process is as follows:

1. You send the license plate via the plate.lookup endpoint
2. The API normalises the format (SIV or FNI) and queries the SIV database
3. The raw data is enriched with manufacturer reference data
4. You receive a complete JSON object with the vehicle identification

The average response time is under 300 milliseconds. The cost is 0.20 credits per request, making it the most affordable endpoint in the API.

What data is returned?

A license plate query typically returns:

• The vehicle's VIN (chassis number)
• The make, model and commercial version
• The date of first registration
• The fuel type and fiscal horsepower
• The vehicle colour
• The administrative status (lien, objection, theft)
• Basic technical data (power, displacement)

Once the VIN is retrieved, you can follow up with a call to the VIN API for a full decode including equipment and options.

Professional use cases

Vehicle sourcing and trade-ins

A dealer receiving a customer for a trade-in can scan or enter the plate and immediately get all the vehicle's information. No need to ask for the registration document or manually look up specifications. The valuation process starts in seconds.

Call centres and CRM

Automotive call centres (roadside assistance, aftersales, sales) can identify the customer's vehicle from the start of the conversation. The agent enters the plate and instantly accesses the complete vehicle record, improving service quality and reducing call duration.

Parking and tolling applications

Smart parking and electronic toll solutions use automatic number plate recognition (ANPR) coupled with the license plate API to identify the vehicle category and apply the correct tariff.

Verification and compliance

Peer-to-peer sales platforms use the API to verify consistency between a listing and the vehicle's official data: mileage, first registration date, actual power output.

Technical integration

Integrating the license plate API is straightforward. A single HTTP call is all it takes. For technical details and code examples, see our integration guide for Python, JavaScript and cURL. Pricing is available on our pricing page.