Content lifecycle
Persist identity. Resolve current truth.
A CMS reference is stable. Artwork metadata, rights, availability and delivery permissions are not. Resolve before rendering or publishing.
Store a reference
Persist the Picker result alongside the CMS entry. An artwork rendition is required for new selections and should remain unchanged until an editor chooses another version.
providertypeidrenditionthumbnail_urldisplay_urlsigned asset URLtitle / rights snapshotResolve references
Batch up to 100 references. Send the saved rendition so the API can verify that the selected version still exists and echo its canonical key.
curl --request POST "https://collection.vieunite.com/v1/references/resolve" \
-H "Authorization: Bearer $VIEUNITE_TENANT_TOKEN" \
-H "Content-Type: application/json" \
--data '{
"references": [
{
"type": "artwork",
"id": "art_456",
"rendition": "crop"
}
],
"fields": [
"id", "type", "name", "artist",
"rights", "availability", "assets",
"available_versions",
"version", "updated_at"
],
"context": {
"usage": "cms_display",
"audience": "general"
}
}'
Inspect every returned item's status. A reference can resolve as unavailable because of publication, rights, safety or version changes without becoming an HTTP-level failure.
{
"data": [
{
"type": "artwork",
"id": "art_456",
"rendition": "crop",
"status": "available",
"resource": {
"id": "art_456",
"name": "Example artwork",
"rights": { "license": "..." },
"assets": { "thumbnail": { "...": "..." } },
"available_versions": [
{ "key": "crop", "...": "..." }
]
}
}
]
}
Validate before publishing
Use validation when a release must not include unavailable artwork. The response is intentionally compact:
{
"data": [
{
"type": "artwork",
"id": "art_456",
"rendition": "crop",
"valid": false,
"status": "unavailable",
"reason": "rendition_unavailable"
}
]
}
From a reference to image bytes
Confirm status, rights and that the stored rendition remains available.
Find the rendition in available_versions and read its delivery dimensions and MIME type.
Send the same rendition key and use the temporary URL close to render time.
The complete JSON formats, JPEG profile, available content, version semantics, signed response and denial reasons are documented in the dedicated Asset Guide.
Reference guidance
- Keep the rendition unchanged until an editor deliberately chooses another version.
- Do not infer current rights from an old resolved snapshot or cached asset.
- Cache resolved metadata and safe thumbnails only for an intentional period.
- Re-resolve after a webhook or sync event changes the resource version.
- Validate immediately before publishing when unavailable artwork must block a release.