Connect to the SEEN Legacy API

Authorization

All requests to our API must be authenticated. In order to authenticate, please include the following header in your requests:

Name: Authorization Value: Token {auth_token}

• auth_token: We will generate an authentication token for you.

Create a new Receiver

Endpoint

POST

 <https://api.seen.io/v1/campaigns/{campaign_slug}/receivers/>

• campaign_slug: You will be given a alphanumeric campaign id, e.g. “welcome-film” for each new campaign/project.

Request Headers

Authorization: This header is common to all requests to our API. Please see the “Authorization” section.

Content-Type: We recommend that you set this to: application/json; charset=utf-8

Request Content

Here is an example of a payload. Fields can differ depending on setup.

Each request payload should be an array of JSON objects, this allows for the creating of multiple receivers at once. Fields are as follows:

• customer_id - Alphanumeric ID that will be stored in our database and sent back to you during callbacks. This is useful for matching each receiver between our database and yours. (string)
• first_name (required) - First name(s) of the new receiver. (string)
• last_name - The receiver’s last name(s), if any. (string)
• email - Email address to deliver the generated emails to, if enabled for the campaign. (string)