Group gifting
A group of coworkers or friends each want to leave their own message for the same gift, and the recipient opens every message together at once. This is a gallery container: it holds several messages instead of one, and each contributor’s recording is added to the same container rather than replacing the last.
Prerequisites
An access token, and a clear read on how container modes differ — mode is fixed at creation, so decide on gallery before your first call. See Container modes.
Create the container in gallery mode
Set mode to gallery in the same call that creates the container. mode is ignored if a container already exists for that crid, so this is the only moment it can be chosen — there is no later call that switches an existing container from single to gallery.
curl -X POST https://client-api.v5.livstick.com/api/v3/containers \
-H "Authorization: Bearer {ACCESS_TOKEN}" \
-H "Content-Type: application/json" \
-d '{ "crid": "TEAM-GIFT-042", "mode": "gallery" }'Record from each contributor
uid is the container’s urid, the same value for every contributor. Because the container was created in gallery mode, each pass through the Recorder — one per contributor — adds another message to the container instead of overwriting the previous one.
<LivstickWidget uid="TEAM-GIFT-042" domain="example.com" />Reread the messages
Filter /messages by crid to read back what the gallery has collected so far. With N contributors having recorded, the call returns N messages for that container.
curl "https://client-api.v5.livstick.com/api/v3/messages?crid=TEAM-GIFT-042" \
-H "Authorization: Bearer {ACCESS_TOKEN}"Unlock the container
unlock makes the collected messages accessible to the recipient. Call it once you consider the collection complete — unlock is not idempotent, so it is a deliberate step, not one to repeat on every contributor check-in.
curl -X POST https://client-api.v5.livstick.com/api/v3/containers/TEAM-GIFT-042/unlock \
-H "Authorization: Bearer {ACCESS_TOKEN}"Next steps
The Client API stops at adding messages to a gallery container — it does not manage a shared pot, contributor invitations, or a link shared between them. Distributing the recording link to each contributor, deciding when to close the collection, and choosing the moment to call unlock are yours to design.