Integration
The Livstick API lets your checkout or CRM create a gift, get its recording link, trigger delivery and read the status back.
Record a few words for Camille.
POST /api/v3/containersAuthorization: Bearer liv_a1b2c3_••••••••••••{ "crid": "ORDER-48219", "language": "fr", "recipient": { "firstName": "Camille", "channel": "email" } }201 Created{ "crid": "ORDER-48219", "url": "…/record", "urlPreview": "…/preview" }Your own order reference goes in; the recording link comes back.
Where it acts
A checkout, an order system or a CRM knows the reference, the buyer, the recipient and the language long before anyone thinks about a video.
One call creates the container; the recording link, QR code and PDF card follow.
An explicit call: your logistics, your release date, your timing.
List containers, read a message, keep your own database current.
Every call is logged. A missing scope is a refusal, not a silent no-op.
How it works
POST /api/v3/containers{ "crid": "ORDER-48219" }# 201 → url, urlPreviewOne call creates the container with your own order reference.
Camille, a message travels with your gift
Someone recorded a few words for you.
When your logic says so: Livstick notifies the recipient, or your own channel unlocks the message.
ORDER-48219
Container and message states come back under your reference.
Good to know
An integration is planned against constraints, not adjectives.
A key targets exactly one platform, and the API refuses any other. Plan one per brand, one per environment.
Permissions are granted per family of operations. A read-only integration cannot create a container, by construction.
The same ceiling on v3 and 2.1. Bulk work — a print run, a nightly reconciliation — is worth pacing.
No self-serve signup and no public sandbox: keys are created, rotated and revoked by our team.
On request
ORDER-48219
The order number becomes the reference. Delivery fires when the parcel leaves the warehouse, so the video arrives with the gift.
Your system pulls each container’s PDF card or QR code for the print run, then follows activation card by card.
Example brands and messages, for illustration.
FAQ
Livstick issues it, for approved integrations. Tell us what you are building and which API you need.
No. A key targets exactly one platform, and that is enforced on every request, not left to convention.
1,000 requests per 15 minutes per key, the same on v3 and 2.1. A coarser per-IP limit applies before authentication.
Start on v3, the current API. v3.1, for V3 platforms, adds containers whose mode is fixed at creation, your own message references (mrid) and signed webhooks. The 2.1 API is still served for existing integrations, so nothing has to migrate in a hurry — but it carries the key in the URL path and its permissions are far coarser.
Not today. Each API version publishes its own OpenAPI specification, so you can generate a client in your language.