Lolly Beta
Launch App

ManageShared assets and provider connections

Canto integration with Lolly (kind: canto)

Note: Lolly Work

This guide covers the optional organisation service. Configuration, console and API paths refer to your Lolly Work instance. The packaged console keeps its release-matched copy of this guide.

Connect a Canto DAM and its files appear in the Lolly Work catalog for the groups you choose, with Canto's approval states and an optional expiry date carried across. Canto stays the source: Lolly Work reads through an app you register and never writes back. The same connection can copy the files into your own store when you want them there.

Canto acquired Image Relay in September 2024, so this kind serves Canto tenants and Image Relay tenants that have moved to Canto.

Onboarding

  1. Scope. Confirm API access under your contract, the tenant's regional domain and the album to expose. Agree Lolly Work groups, approved states and any custom expiry field, including how records with no approval state should be handled.
  2. Connection. Obtain the App ID, Secret and refresh token described below. Use the four-step connection; this kind uses a pasted credential rather than the CLI consent flow.
  3. Tenant check. Run the Canto tenant check for every required file scheme. Compare originals with direct Canto downloads and test permitted and refused access before enabling the wider audience. An Image Relay migration needs the driver selection in Leave a DAM.
Note: Not yet confirmed live

The driver is not yet confirmed against a live tenant. The endpoint paths and field names come from Canto's documentation, and Lolly Work holds no Canto account, so the check runs on your own tenant under your contract. Check a source on your own tenant lists what to look at. Contributors changing the driver follow its maintainer runbook in the Lolly Work repository.

What you need from Canto

Credential shape

One sealed OAuth credential, pasted rather than captured. clientId and clientSecret are the App ID and Secret; refreshToken is the grant against them.

{ "clientId": "…", "clientSecret": "…", "refreshToken": "…" }
lw providers credential acme-canto     # prompts for the JSON; never argv, never shell history

Get the refresh token by running Canto's own documented OAuth2 authorization-code flow once by hand against your App ID and Secret. lw providers auth refuses this kind; see OAuth sources.

instance.json / lw providers add

{
  "id": "acme-canto",
  "kind": "canto",
  "label": "Acme Canto",
  "options": { "tenant": "acme", "domain": "com", "albumId": "AB12C" },
  "mapping": { "availabilityFields": { "until": "Expiry Date" } },
  "exposure": { "groups": ["marketing"], "requireApproved": true }
}
Options
OptionWhat it does
tenant (required)The subdomain of your tenant URL. With domain it gives the API base https://<tenant>.canto.<domain>/api/v1 and the token endpoint https://oauth.canto.<domain>/oauth/api/oauth2/token.
domaincom, global or de.
baseUrl, tokenUrlOverride either endpoint. Both stay pinned to the Canto hosts.
albumIdFederate one album (the equivalent of Image Relay's folderId).
approvedStatesThe Canto approval states that count as approved, default ["approved"]. A record with no state at all federates as approved; exposure.requireApproved is what gates.
minGapMsThe gap between calls, default 350 (about three a second).

mapping.availabilityFields imports expiry: name the custom field that holds the date (here "Expiry Date", which becomes an availability window availableUntil). Without it, the manual catalog.expire control is the only expiry. An Image Relay tenant that already set this keeps its settings; only the field name changes.

Verify

lw providers preview --kind canto --options '{"tenant":"acme"}'   # dry run, nothing stored
lw providers health acme-canto
What each error means
ErrorMeaning
oauth token refresh failed (401)The App ID, Secret or refresh token is wrong, or the grant was revoked. Capture the credential again.
oauth token refresh failed (400)The token endpoint refuses the request format. A new credential cannot fix this; report it with the tenant check.
canto api 401The token exchange worked; the tenant refused the access token.
canto api 403The tenant refused the call, most often because API access is not on the contract tier.
canto url outside allowed hostsA baseUrl or tokenUrl override points outside the Canto hosts.

Notes / limits

Off-boarding

Canto is an exit target subject to tenant qualification, including whether each scheme's download is the true original. A stored checksum alone does not prove that the source supplied an original.

Prepare the destination through the self-hosting strategy with S3 storage, then rehearse materialize, drift and cutover with Leave a DAM. Verify approval and mapped expiry, keep required rights and history exports separately, and test old references after cutover. For former Image Relay tenants, choose the driver that serves the files today.

Compare offboarding destinations, starting with open-source services you can run. Each route remains subject to this source's limits.