Content lifecycle

Save a selection and use it later.

The editor has chosen an artwork and an image version. Save that reference with your content, then check its current details when you reopen, display or publish it.

Store a reference

Save provider, type, id and rendition for each selected artwork. Keep the rendition unchanged until the editor chooses a different version. Collection references use the first three fields only.

Storeprovidertypeidrendition

Do not treat as permanentthumbnail_urldisplay_urlsigned asset URLtitle / rights snapshot

Resolve references

Call POST /v1/references/resolve from your backend with the references:resolve scope. Send up to 100 saved references, including each artwork’s rendition. Replace the example ID and key below with a real selection.

resolve current artwork datacURL

curl --request POST "https://collection-test.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.

Available result · shortened for readabilityJSON

{
  "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

Call POST /v1/references/validate with the same references array and usage context you use for resolve. It needs the same references:resolve scope. It returns a compact check for each item, without the full artwork object:

validation resultJSON

{
  "data": [
    {
      "type": "artwork",
      "id": "art_456",
      "rendition": "crop",
      "valid": false,
      "status": "unavailable",
      "reason": "rendition_unavailable"
    }
  ]
}

From a reference to image bytes

ResolveCheck current policy

Confirm status, rights and that the stored rendition remains available.

DescribeRead delivery facts

Find the rendition in available_versions and read its delivery dimensions and MIME type.

AuthorizeRequest a signed URL

Send the same rendition key and use the temporary URL close to render time.

Next, use the signed URL example to request the image. It shows the request, successful response and per-item denial reasons.

Read Assets and delivery

Keep saved artwork usable

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.