Vieunite Collection API

Bring artwork
into your CMS.

Give editors a way to find and choose Vieunite artwork without leaving your CMS. Start with the hosted Picker, then save and display what they select.

Start the quickstart Try the CMS demo

Choose a path

What are you building?

Most CMS integrations start with the Picker. Use the API directly if you need your own browsing interface.

Hosted Picker

Add an artwork button to your editor. Vieunite provides the browsing window; your backend receives the chosen artwork IDs and image versions.

Integrate the Picker

Server API

Build your own search and artwork screens. Your backend fetches the catalogue, applies filters and requests images for display.

Build a custom browser

Sync and webhooks

Already storing artwork data? Follow catalogue changes so your cache reflects updated images, rights and availability.

Keep content current

Curated artwork

Display-ready versions

Rights-aware delivery

Your first selection

Start with a button in your editor.

Load the SDK and connect your two CMS routes. This client opens the Picker and returns the result. The quickstart adds the button, backend setup, cancellation handling and form storage.

Follow the complete quickstart

After loading the Picker SDKJavaScript

const picker = VieunitePicker.create({
  sessionEndpoint: "/api/vieunite/picker/session",
  redeemEndpoint: "/api/vieunite/picker/redeem",
  pickerOrigin: "https://collection-test.vieunite.com",
});

async function chooseArtwork() {
  return picker.open({
    allowedTypes: ["artwork"],
    selectionMode: "multiple",
  });
}

const picker: VieunitePicker.PickerClient = VieunitePicker.create({
  sessionEndpoint: "/api/vieunite/picker/session",
  redeemEndpoint: "/api/vieunite/picker/redeem",
  pickerOrigin: "https://collection-test.vieunite.com",
});

async function chooseArtwork(): Promise<VieunitePicker.PickerResult> {
  return picker.open({
    allowedTypes: ["artwork"],
    selectionMode: "multiple",
  });
}

After selection

Save the artwork and the chosen version.

The Picker returns a small object called a reference. Store it with your content. When you need the artwork, ask the API for its current details and an image URL.

CMS editorChooses an artwork

Hosted PickerReturns a reference

CMS databaseStores ID + rendition

CMS backendResolves current data

Save in your CMS { provider, type, id, rendition }

Fetch when needed metadata · rights · availability · assets

See the complete lifecycle

See what your editors will use.

Open the minimal example to choose an artwork and inspect the result. Try the CMS demo to see how a selection fits into a content form.

Minimal PickerOpen quickstart ↗ Full workflowOpen CMS demo ↗