How to send event registrations to Lyyti

Videosync can automatically push each event registration to a matching Lyyti event as a participant with status: "show". This keeps the Lyyti participant list in sync with Videosync registrations, so your Lyyti reports reflect actual sign-ups without manual export/import. Participants are matched by email address, so re-registrations and edits update the existing Lyyti participant instead of creating duplicates.

This article walks through the one-time account setup, the per-event configuration, and what to do when a push fails.

1. Get your Lyyti API key

The integration uses Lyyti’s HMAC-signed REST API. You need an API key pair (public key + private key) from Lyyti.

1. Ask your Lyyti administrator (or Lyyti support) to issue an API key for the Lyyti user who owns the events you want to integrate.
2. Lyyti scopes API keys per user, so the key will only see events that user owns or has been granted access to. Make sure every event you want to push to is owned by — or shared with — that user.
3. Lyyti needs to grant the key write access to those events as well; read-only keys can list events in the Videosync dropdown but the actual participant push will fail with 403 "write access denied".
4. Lyyti will give you two strings, e.g.:
   • public_key: a hex string like 1a2b3c…
   • private_key: a hex string like 9f8e7d…

Keep the private key safe — it’s the secret half of the pair.

2. Save the Lyyti credentials to your Videosync account

The keys are stored at the account level and are reused by every event that enables the integration.

1. Open the Account settings at /admin#/account/settings.
2. Scroll to the Connect to Lyyti section.
3. Paste the Public key and Private key in the corresponding fields.
4. Click Save Lyyti credentials.

The Public key remains visible after saving, but the Private key is shown as *** — Videosync never echoes the private key back to the browser after it’s saved.

You can replace the credentials at any time by entering a new pair and saving again. Use the Remove button next to a saved key pair to clear the credentials entirely.

3. Map a Videosync event to a Lyyti event

For every Videosync event you want pushed to Lyyti:

1. Open the event in the Videosync admin.
2. Go to Build → Registration.
3. Scroll to the Send registrations to Lyyti accordion and toggle it on.
4. Expand the accordion. The Lyyti event dropdown will show the list of available active Lyyti events.
5. Pick the matching Lyyti event from the dropdown.
6. Save the event.

If the dropdown is empty, see Troubleshooting below.

To stop pushing to Lyyti for a specific event, either toggle the integration off or pick None from the Lyyti event dropdown.

4. What gets sent to Lyyti

When a viewer registers for a Videosync event with the Lyyti integration enabled, Videosync sends the following participant data to Lyyti:

Lyyti field	Source in Videosync
email	The registrant’s email
firstname	The registrant’s first name
lastname	The registrant’s last name
phonenumber	The registrant’s phone number (E.123 format recommended)
info1	All other custom registration fields, encoded as a JSON object keyed by the field label the admin set up
status	Always show
saved	Always true

Custom fields appear in Lyyti’s Additional information column. For example, if your Videosync registration form has a “Company name” field and a “Industry” select, Lyyti’s info1 will show:

{"Company name": "ACME Inc", "Industry": "Finance"}

For radio/checkbox fields the registrant’s selected choices are joined with , so the choice values are preserved.

The push happens automatically right after the registration is saved in Videosync. The registration response is not delayed by the Lyyti call — even if Lyyti is unreachable, the registrant always gets a successful registration in Videosync.

One participant per email address

Videosync identifies participants by email address. If the email already exists in the mapped Lyyti event, Videosync updates that existing participant instead of adding a second one — the name, phone number, custom fields and status are overwritten with the latest data from Videosync.

This applies to every route that can change a registration:

• the same person registering again with a different name or updated details,
• a registrant editing their own details on the event page after registering,
• a participant you added in Lyyti yourself (for example an invitee with status notreacted), who then registers through Videosync — their existing Lyyti row is updated and their status becomes show.

Two consequences worth planning for:

• The latest registration wins. If two different people register with the same email address, the second one overwrites the first in Lyyti, and only one participant exists there. Videosync itself keeps both registrations.
• Manual edits in Lyyti can be overwritten. If you edit a participant in Lyyti and that person later re-registers or edits their details in Videosync, the Videosync data replaces your edit. Fields Videosync doesn’t send (such as info2 or organiser notes) are left untouched.

5. Retry failed Lyyti syncs

If a push to Lyyti fails (wrong credentials, network issue, Lyyti rejected the participant, etc.), Videosync stores the error on the affected registration and continues normally.

To retry the failed registrations:

1. Open the Videosync event in admin.
2. Go to Build → Registration.
3. Expand the Send registrations to Lyyti accordion.
4. Click Retry failed Lyyti syncs.

You’ll see a toast summarising the result, for example: Lyyti retry: 7/9 synced, 1 skipped, 1 failed.

• synced — push succeeded on retry. Lyyti now has the participant.
• skipped — the integration was disabled or the event lacks a Lyyti event id at the moment, so nothing was sent. Re-enable / re-map and try again.
• failed — Lyyti still rejected the push. The error message is stored alongside the registration and is visible to support if needed.

You can click the button as many times as you want; rows that already synced are skipped automatically, and rows whose email already exists in Lyyti update that participant rather than creating a duplicate.

Troubleshooting

The Lyyti event dropdown is empty

Most common causes:

1. Lyyti credentials are not saved on the account. Check Account settings at /admin#/account/settings → “Connect to Lyyti”.
2. The API key’s owner doesn’t own any active events in Lyyti. Lyyti scopes API keys per user — only events that user owns or has been granted access to are returned. Ask your Lyyti administrator to share the relevant events with the key’s user.
3. The events you expect are archived in Lyyti. Only active events are listed. Unarchive the event in Lyyti, or pick a different active one.

Registrations push but Lyyti doesn’t show them

1. Wrong Lyyti event mapped. Double-check the dropdown selection — every Videosync registration goes to whichever Lyyti event id is mapped.
2. API key lacks write permission on that event. Lyyti can grant read access without write access. If you can list events but pushes fail, ask Lyyti to add write/participant permission to the key.
3. You’re looking for a second row that was never created. When the email already exists in the mapped Lyyti event, Videosync updates that participant instead of adding another one — see One participant per email address. Check the existing participant’s details rather than expecting a new row.
4. The participant was deleted in Lyyti after Videosync first synced them. Videosync remembers which Lyyti participant a registration belongs to, and Lyyti still accepts updates for a deleted participant without reporting an error — so the registration looks synced while nothing appears in your participant list. Contact support@videosync.fi with the event URL; we can reset the link so the next sync recreates the participant.

A registration shows as failed in “Retry failed Lyyti syncs”

The error is stored on the Videosync registration. Common error messages:

• 403 This event does not exist, or write access to it was denied — the API key doesn’t have permission to write participants to the mapped Lyyti event. Fix the Lyyti side.
• 400 Invalid or missing event ID — the mapped event id is no longer valid in Lyyti (deleted/archived). Pick a different Lyyti event in the dropdown.
• Missing email in registration data — the Videosync registration form has no email field, or the registrant left it blank. Email is required by Lyyti.

If you keep hitting an error you can’t resolve, contact support@videosync.fi with the event URL — we can read the stored error details.