The UK's vehicle data landscape is a specialist's world: one provider for MOT history, another for service schedules, a third for valuations, a fourth for specifications. One Auto API built its business on ending that fragmentation, bundling the market's best data sources behind a single API so that dealers, platforms and workshop software integrate once and switch products on as they need them.
For years, one product on that shelf was conspicuously missing: the picture. Every vehicle their customers resolved arrived as clean, structured data and no image, because imagery is the one vehicle attribute you cannot ship as a JSON field alone. That is where we come in.
Imagery as a data product
The insight that made this partnership work is that vehicle imagery behaves exactly like the rest of One Auto API's catalogue. Their customers already identify vehicles through the platform; an image is simply one more product resolved against the same request. Vehicle Imagery plugs in behind their API, and their customers get studio images of the right vehicle through the same integration they already run, with sizing controlled by the same kind of parameters they use everywhere else.
An integration that stays boring
The partnership's quiet superpower is what does not happen. When our catalogue expanded to live factory colours, the update flowed through One Auto API's platform as a bigger list of available colours per vehicle, with no integration work on their side. When their customers needed specific image dimensions, height and width parameters were passed straight through. Catalogue growth on our side becomes product improvement on theirs, automatically.
- One integration serving One Auto API's entire customer base
- Eight exterior views plus interior, available on request
- Colour and coverage updates that arrive as data, not as projects
- Domain based licensing, so end customers switch imagery on like any other product
Live in production
The model is proving itself in practice: platform customers have taken imagery from evaluation through completed integration and into contracted production use, on fixed monthly terms that fit how a data platform sells. For those customers there is no second vendor relationship to manage. Imagery is simply part of the One Auto API stack, delivered through our CDN underneath.
Coverage flows in both directions
The partnership also works backwards. When One Auto API's customers need vehicles we do not yet cover, especially in the commercial vehicle ranges where photography has always been thinnest, their requests feed directly into our catalogue roadmap. Their market pull sharpens our coverage, and every platform customer downstream benefits from the additions.
Why this story matters beyond the UK
One Auto API is what a modern data platform partnership looks like: we stay the imagery specialists, they stay the aggregation specialists, and neither side asks the other to become something else. For platforms anywhere weighing whether to build an imagery layer or plug one in, this is the working answer.
