Retrieve an image

Delivers a stored image. Every image key in the API — a product image's uploaded.key, an upload's key — resolves through this endpoint, so https://stylor.ai/api/v1/image/{key} is a URL you can drop straight into an <img> tag. (Generated thumbnail url values are already full URLs on this endpoint.)

Authentication

None is required. Keys are unguessable UUIDs and the endpoint is public, so it works from browsers, emails and third-party embeds. It is not rate limited and does not count against your quota.

How it responds

The endpoint does not stream bytes itself. It answers 302 Found with a Location pointing at a signed CDN URL that expires 120 seconds after it was issued. Browsers and image clients follow this transparently. If you fetch programmatically, follow the redirect immediately and cache the API URL, never the signed one.

Caching

The 302 sets no Cache-Control header of its own. Transformed renditions are stored with Cache-Control: public, max-age=31536000, immutable, which the CDN returns with the image bytes; originals are stored without one. A key that does not exist still redirects, and the CDN then answers with an error (typically 403).

Transforms

Append segments of the form /-/<type>/<value> after the key to get a derived image:

Transforms may be combined and are applied in URL order: /api/v1/image/images/3f9c….jpeg/-/resize/600x/-/format/webp. A value that does not match the table is ignored rather than rejected. The first request for a given combination renders and caches it synchronously, so it is slower; later requests are served from cache. The cache is keyed on the set of transforms regardless of order, so list them in a consistent order. If rendering fails, the original image is served instead of an error.

Do not add a trailing slash: it costs an extra 308 redirect to the same URL without it. Segments before the first /-/<known type>/ are part of the key; after it, segments that do not form a valid /-/<type>/<value> triple are ignored.