Data & feedback
Name your consent options, collect them when people record, and pull contacts and opt-ins through the API on your schedule.
# scope: messages:readGET /api/v3/messages ?from=2026-03-01T00:00:00Z &to=2026-03-02T00:00:00Z &limit=200Authorization: Bearer liv_<prefix>_<secret>Yesterday’s contacts and the boxes they ticked, read with a key scoped to your programme.
Where it acts
A recording that ends with a form carries the sender’s contact details and an answer to each consent option you declared.
One checkbox per option you declared, in the form the sender fills in.
A credential constrained to your own programme — not a general-purpose one.
Contacts and their answers come back with the message, filtered by date range.
The archiving delay you set is also your deadline.
How it works
One box per option you named, in the recording form.
# every morning at 06:00GET /api/v3/messages ?from=…&to=… &limit=200A scheduled job reads the day’s messages with a scoped key.
Your team maps the fields once; each run creates or enriches a record.
Good to know
What the platform hands over, and the point where the hand-off stops.
Short keys declared on the programme — a newsletter one and a CRM one are the usual pair. Nothing is collected if the journey has no form.
A key restricted to your programme and to reading messages: 200 records per page, filtered on a date range. Nothing leaves on its own.
Once your archiving delay is reached, message data is erased — contact details and consent answers with it. The sync has to run inside that window.
The exact key each answer is stored under depends on the recorder generation your journey runs on.
Settled at scopingA job runs at dawn, asks for yesterday’s messages by date range and walks the pages. Every ticked CRM box creates or enriches a customer file.
The customer records a message while the gift is wrapped. Name, email and newsletter opt-in land in the loyalty database.
Example brands and messages, for illustration.
FAQ
Whatever your recording form collects — typically first name, last name and email — attached to the message itself, not to a separate export.
Every option you declare comes back as its own answer, on the same record as the contact.
Not as such. The date filter is on when a message was created, not when it was updated: a catch-up is a sliding window, not a cursor.
No. You pull it with a scoped key, on your own schedule. There is no packaged connector for a named CRM.