Media and images
Read Asset file metadata and signed original or named rendition URLs through REST.
Asset resources include a nullable file object. Relation fields that point to Assets remain IDs; read the Asset resource directly when you need its metadata or URLs.
curl 'https://delivery.example.com/rest/asset/ASSET_ID' \
-H 'x-api-key: YOUR_DELIVERY_KEY'{
"_id": "ASSET_ID",
"file": {
"originalName": "launch.jpg",
"mimeType": "image/jpeg",
"size": 248301,
"size_str": "243 KB",
"metadata": { "width": 2400, "height": 1600 },
"url": "https://images.example.com/SIGNED_ORIGINAL_PATH",
"thumbnail": "https://images.example.com/SIGNED_THUMBNAIL_PATH"
}
}url is the signed original image-service URL. Each image preset configured for the Backend appears as a named signed URL, such as thumbnail, card, or hero. The per-Backend OpenAPI document lists the available names.
A missing file has no file object. Treat absent URLs as unavailable. Do not construct image-service signatures in application code.
Preview Asset reads use the same shape and remain private, no-store. Never expose the Preview Bearer while forwarding an image URL or Asset response.