A dealer site on WordPress usually carries a media library of inconsistent photos and a plugin that scrapes more of them. Replace both with one lookup: the vehicle resolves in PHP, the URL is cached, and the template renders an ordinary image tag.
Every uploaded vehicle photo is a file to store, a thumbnail set to generate and a backup to carry forever. Images that resolve on demand live on our CDN, so your uploads folder stays the size it is today.
A small plugin file, a transient and a shortcode. No build step and no JavaScript.
Put the API key in wp-config as a constant, so it never sits in theme files or in the database.
Call the API with wp_remote_get from a small plugin, using the VIN or the make, model and year already stored on the post.
Store the resolved URL with set_transient for a day. Listings render from cache and the API is called once per vehicle.
Register a shortcode or a template tag that outputs an img tag with the width your theme actually uses.
Bring vehicle imagery into your product without the heavy lifting. Clear docs, open SDKs and ready-made plugins connect to your stack in minutes, and our status page shows you live how the API is doing.
Because the output is a plain image tag with a URL, it drops into Elementor, Divi, Bricks or a custom theme without special handling. Custom fields hold the VIN, the shortcode does the rest.
WordPress dealer sites tend to accumulate imagery rather than manage it. Someone uploads photos for a batch of cars, someone else installs a plugin that pulls more from a feed, and a year later the media library holds thousands of files at four different crops with no consistent lighting between them.
Resolving on demand inverts that. The post already knows which vehicle it is, so the image can be derived from the data instead of attached to it. A transient keeps the API call rare, the CDN keeps delivery fast, and the listing archive finally looks like one catalogue rather than twelve photographers.
Not yet. The integration is small enough that most teams write a short plugin file against the REST API, and we are happy to review it.
In wp-config as a PHP constant. Keep it out of theme files, out of the database and out of anything the block editor can reach.
Not if you cache. With a daily transient per vehicle, an archive page renders entirely from cache and makes no outbound calls at all.
Yes. Store the VIN or the spec as product meta and resolve from there, exactly as you would for a custom post type.
They work unchanged. The shortcode returns an image tag, which every builder can place inside its own layout.
Yes, and many dealers do for used stock. A common pattern is real photos where they exist and resolved imagery everywhere else.
Tell us which theme or page builder you use and how vehicles are stored. We come back with a working snippet for your setup.
