Shopify gives you a template language and no server of your own, which decides the shape of this integration. Resolve vehicles in an app or a scheduled job, store the URLs as metafields, and let Liquid render them like any other field.
Liquid renders at request time and has no safe place for a secret. Resolve ahead of time and store the result on the product, so the storefront reads a metafield instead of calling anything.
Resolve outside the storefront, store on the product, render from the theme.
One namespace, a field per angle you render. Vehicle spec or VIN usually already lives on the product.
A scheduled job or a private app resolves each product and writes the URLs back through the Admin API.
The template outputs an img tag straight from the metafield, with the width your section renders.
Re-resolve when a product is created or its vehicle data changes, not on a timer.
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.
Stores selling parts by vehicle fitment need a picture of the vehicle, not of the part. Resolved imagery gives every fitment entry the same framing, which makes a filtered collection page read as one catalogue.
The instinct on Shopify is to reach for a storefront script, because that is where themes usually put anything dynamic. For vehicle imagery that is the wrong trade: it puts a key somewhere public, adds a render blocking request to every collection page and leaves you debugging a theme instead of a job.
Writing URLs into metafields moves all of the work off the critical path. Resolution happens when the catalogue changes, which is rare, and the storefront does what it is good at, which is rendering fields into a template. Collection pages stay fast, and the theme stays something a merchandiser can edit.
Not currently. Most merchants run a private app or a scheduled job against the Admin API, which keeps the integration under their own control.
No, and you would not want to. Liquid has no safe way to hold a secret. Resolve ahead of time and store the URLs as metafields.
Into product metafields, one per angle you render. The theme then reads them exactly like any other product field.
They apply to files in Shopify. Our URLs already carry width and format parameters, so request the size you need directly.
Yes, and it is a common case. The vehicle image illustrates the fitment while the product stays the part.
When products change. A nightly pass over new and updated products is enough for most catalogues.
Tell us how vehicle data sits on your products and which sections show images. We come back with resolved URLs and a metafield plan.
