Australian Rego Plate Lookup API

GET /api/v1/lookup?plate=1ZC7YN&state=VIC

Send a registration plate and state to a single REST endpoint. Get year, make, model, body type, and engine displacement back as JSON. Typical response time under 3 seconds. Built for auto parts stores, vehicle services, and anyone who needs to identify a car from its plate.


Try It

Enter any Australian registration plate. This calls the production API in real time -- no mocks.

State

What You Get Back

200 OK -- application/json
{
  "success": true,
  "vehicle": {
    "year": 2003,
    "make": "TOYOTA",
    "model": "COROLLA",
    "description": "03~06 TOYOTA COROLLA ZZE122R ASCENT",
    "body": "HATCHBACK",
    "engine": "1.8L"
  },
  "duration_ms": 1509.96,
  "alternatives": []
}

Structured Vehicle Data

Every successful lookup returns a structured JSON object with the vehicle's year, make, model, body type, and engine displacement. Responses include timing data.

When a plate maps to multiple variants (such as different engine options on the same model), the API returns alternative matches so your application can handle ambiguity.

All eight Australian states and territories are supported: ACT, NSW, NT, QLD, SA, TAS, VIC, and WA.


Why PlateAPI

All States & Territories

ACT, NSW, NT, QLD, SA, TAS, VIC, and WA. Every plan covers every state.

Fast Responses

Typical lookup completes in under 3 seconds. Every response includes timing data.

Structured JSON

Year, make, model, body type, and engine displacement in a single structured response.

Shopify Integration

Drop-in widget for Shopify stores. Customers look up their vehicle right on your site.

Vehicle Alternatives

When a plate maps to multiple variants, the API returns all possible matches.

Simple REST API

One GET endpoint. No SDK, no authentication flow. Works with any HTTP client in any language.


Built For

Auto Parts Stores

Match parts to vehicles instantly. A customer enters their plate, you know the exact year, make, model, and engine -- no manual lookup, no guessing.

Vehicle Services

Workshops, detailers, and service centres can identify vehicles at intake without manual data entry. Faster check-in, fewer errors.

Dealerships & Finance

Quick vehicle identification for trade-in quotes, valuations, and loan applications. Verify vehicle details from a plate number in seconds.

Fleet Management

Track and identify vehicles across your fleet. Integrate plate lookups into your management system to keep records accurate and up to date.


Frequently Asked Questions

What data does the API return?

Each lookup returns the vehicle year, make, model, body type (sedan, hatchback, ute, etc.), engine displacement, a full description string, and alternative vehicle matches when the plate maps to multiple variants.

Which Australian states and territories are supported?

All eight: ACT, NSW, NT, QLD, SA, TAS, VIC, and WA. Every plan covers every state at no extra cost.

How fast are lookup responses?

Typical response time is under 3 seconds. Every response includes a duration_ms field so you can monitor performance in your application.

Is there a free plan?

Yes. The free tier includes 20 lookups per month with a rate limit of 1 request per minute. No credit card required.

What happens when I hit my monthly lookup limit?

All plans below Enterprise have a hard cap. Once you reach your monthly limit, further requests will be rejected until the next billing cycle. Upgrade your plan at any time to increase your allowance.

Does PlateAPI integrate with Shopify?

Yes. PlateAPI offers a drop-in Shopify widget that lets your customers look up their vehicle directly on your store. All paid plans include full Shopify integration; the free tier includes the widget only.

What format are API responses in?

All responses are JSON. The API uses standard HTTP status codes -- 200 for successful lookups, 404 when no vehicle is found, and appropriate error codes for invalid requests.

Do I need an SDK to use PlateAPI?

No. PlateAPI is a simple REST API with a single GET endpoint. Any HTTP client in any language works -- curl, fetch, requests, or whatever your stack uses.