Klaviyo – SEEN Documentation

⚠ Pending update: This guide was originally created for API 1.0 (Now Legacy), adjustments may be necessary if you are using via API 2.0. For the latest information please refer to SEEN API 2.0 - Authorization & SEEN API 2.0 - Create Data or contact us.

In the following example, we will be sending users data to SEEN for video generation, and receiving a unique landing page link and a unique, personalised thumbnail back to Klaviyo for distribution.

This example uses a POST webhook in Klaviyo Flows to send data to SEEN, and an event to receive the data back to Klaviyo. The receiver’s email address is used as their unique identifier.

Send data to SEEN

Create a new Flow in Klaviyo

Choose your trigger

Add “Webhook” as the next step, give it a name, and fill it out with the following:

Destination URL ⇒ https://api.seen.io/v1/campaigns/{campaign_slug}/receivers/*

Headers

Key ⇒ Authorization

Value ⇒ Token {token}**

JSON Body

You can use the code snippet below as the starting point for the payload: ***

[
    {
        "first_name": "{{ person.first_name }}",
        "last_name": "{{ person.last_name }}",
        "customer_id": "{{ person.email }}",
        "extra_args": {
             "city": "{{ person.City }}"
        }
    }
]

* You will receive your campaign_slug from SEEN

** You will receive your token from SEEN

*** Remember to modify your payload based on your video campaign. More information about the payload structure in our documentation.

You can now test the webhook with a test profile.

Receive data back from SEEN

Share the following items with SEEN:

Name of the event you wish to use

“SEEN” in this example

Name of the event fields you wish to use

“seen_thumbnail_url” and “seen_landing_page_url” in this example

Unique ID you wish to use for your profiles

Email address in this example

Your Private API Key

SEEN will create the payload based on these details.