FOR DEVELOPERS
A small integration.
A shared foundation.
One endpoint between your application and your vehicle data. Your backend asks for a registration. CarData handles the database check and returns the response.
THE REQUEST
Standard HTTP.
Familiar JSON.
Call CarData from your server with a project key. Cached vehicles return immediately. New ones are fetched once, saved, and shared.
Standard HTTP and JSON Source and fetch timestamp included Server-side provider credentials
POST /api/v1/vehicles
curl -X POST "$CARDATA_URL/api/v1/vehicles" \
-H "Authorization: Bearer $PROJECT_KEY" \
-H "Content-Type: application/json" \
-d '{"vrm":"EA65AMX"}' Keep project keys on your server.
CACHE FIRST
Ask once.
Answer from memory next.
Your integration stays the same whether the response comes from the provider or your CarData library. The payload includes where it came from and when it was fetched.
Create a project key
A shared memory for your vehicle data.