POST /v1/images/download to retrieve the image
for your own storage. You can use URLs from any source; no prior product or brand
research request is required. Authenticate with your Upriver API key.
Successful responses contain binary image bytes. Read the response body as bytes,
rather than parsing it as JSON. Error responses contain a JSON detail field.
Content-Type to determine the actual format; the source URL’s
extension may differ. Supported formats are JPEG, PNG, WebP, GIF, and AVIF.
Responses are attachments with Cache-Control: no-store. No hosted image copy is
created. Each request attempts retrieval from the supplied URL; the endpoint does
not guarantee access to every protected source or preserve the image for later.
Use with product research
Requestimage_url in the include fields of POST /v1/brand/products, then send
selected image URLs to this endpoint when you need help retrieving them. Store
successful downloads in your own storage and use your own URLs for later display.
Research responses continue to include original image URLs.
Limits and errors
Downloads are limited to 10 MiB, 16 million decoded pixels in total, and 32 frames. Only public HTTPS URLs on the standard HTTPS port are accepted. URLs requiring login credentials are unsupported. Each account can make 30 attempts per minute and 1,000 per day, subject to shared service capacity. Failed attempts can count toward these limits. Downloads do not consume product-research credits. A429
response includes Retry-After; a 503 indicates temporary unavailability.
Oversized images return 413. Missing sources may return 404; upstream failures,
challenge pages, and invalid images return 502. Upstream timeouts return 504.