Brand & control
An automated check flags a video. A person — at Livstick or on your team — decides if it is delivered.
A message is on its way.
Review queue
The container is open. The message is still waiting.
Where it acts
A video gift is tied to an order, a card, a brand. The only question: should this message reach this recipient?
The container opens with nothing to play.
A queue for your platform, video playable.
The same three decisions, one call.
An email on rejection, if switched on.
How it works
An automated check marks the video.
The container opens. The message waits.
From the back office, the admin API or the CLI.
Good to know
Moderation is easy to describe as more than it is.
Approve, approve quietly (no notifications), or reject.
One direct delivery call skips the queue. Check it before launch.
The link or QR code no longer resolves to a video.
It depends on your programme’s pipeline: no provider, no category list.
Settled at scopingThe QR code answers as if there were nothing to play.
What comes back waits in your queue until your team clears it.
Example brand and messages, for illustration.
FAQ
It stays unreleased: the recipient’s page has nothing to play. It isn’t deleted, and it isn’t delivered.
Three: approve, approve quietly — the same release without the surrounding notifications — or reject. Decisions taken through the admin API can carry a note.
No. The public API treats it as missing, so there is no page left to bypass.
The queue is scoped to your platform. Who reviews, and how fast, is agreed per programme.
Only if your programme turns rejection notices on and provides a receiver address.
