Most image libraries make you translate your vehicle data into their identifiers first. That table is where errors creep in and where somebody ends up maintaining a spreadsheet. Here the lookup happens on our side.
The first call is the only one that differs.
Pass what you have. You get the configuration back, with a permanent id.
It survives catalogue updates, renames and re-imports, so it is safe to keep in your database.
From then on you address the images directly, without looking the car up again.
Use the search route. It resolves free text such as make, model, year and variant into a configuration.
It depends on the country. Where it is not, VIN or search covers the same ground.
The resolved configuration with its permanent id, which you then use to request any view.
No. Configuration ids are permanent and survive catalogue updates, so stored references keep working.
You get the candidates back and can pick, rather than the API guessing silently.
Every image service promises pictures. The difference between one that saves work and one that creates it lies in what you have to hand over before you get an image. If the answer is an internal identifier of theirs, you have just bought yourself a mapping problem.
It starts small: a spreadsheet matching your model names to theirs. Then a facelift arrives, a trim is renamed, an import feed changes its spelling, and the table quietly goes stale. The symptom shows up as a listing with the wrong picture, which is worse than no picture at all.
At intake the VIN is already being typed. The same step requests the image, and the listing can go live the same hour. Nobody opens a second system, nobody matches names, and the picture belongs to the car that is actually standing outside.
Tell us what you need, and we’ll show you exactly the images your customers would get, clean, consistent and ready to use. Send a message or book a short call, whatever suits you better. You’ll usually hear back the same day, with real examples based on your own inventory.
