Vieunite.Developers
Open quickstart

Vieunite Collection API

Bring curated art into your CMS.

Give editors a hosted artwork Picker, store stable references, and resolve current metadata and licensed assets when content is rendered.

Curated for context
Composition-safe artwork versions
Rights-aware delivery

Choose a path

Start with the editor experience you need.

The hosted Picker is the fastest route for most CMS products. The server API is available when you need a fully custom discovery workflow.

01

Hosted Picker

Vieunite owns artwork discovery and selection UI. Your CMS receives validated references through a small browser SDK.

Integrate the Picker
02

Server API

Build your own catalogue experience with authenticated search, filters, facets, metadata and asset delivery.

Build a custom browser
03

Sync and webhooks

Keep a local index or cache aligned with publication, rights, availability and asset changes at scale.

Keep content current

Five-minute quickstart

One reusable client. One call to open.

The SDK handles the modal, window messaging, source validation, cancellation and one-time selection redemption. Application code only handles the final result.

Follow the complete quickstart
cms-editor.htmlJavaScript
<script src="https://collection.vieunite.com/sdk/v1/picker.js"></script>

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

const result = await picker.open({
  allowedTypes: ["artwork"],
  selectionMode: "multiple",
});

if (result.status === "selected") {
  await saveReferences(result.selection);
}

The durable model

Save identity. Resolve current truth.

Artwork names, rights, availability and delivery URLs can change. A CMS stores a compact reference and resolves current data when it renders or publishes.

CMS editorChooses an artwork
Hosted PickerReturns a reference
CMS databaseStores ID + version
CMS backendResolves current data
Persist this { provider, type, id, rendition }
Resolve when needed metadata · rights · availability · assets

See the complete lifecycle

Try it before you integrate it.

The minimal example shows the browser contract. The CMS demo shows version selection, reference persistence, refresh and editor state together.

Search documentation

Start with “Picker”, “rendition”, or an endpoint path.