Delighted is a survey creation and management platform that enables you to gather feedback through metrics such as Net Promoter Score (NPS) and Customer Satisfaction Score (CSAT) from your desired audience. It provides a user-friendly interface to easily create surveys, and distribute them through multiple channels such as emails and text messages. It also provides tools that allow you to gain insights into the survey responses to improve customer satisfaction, reduce churn, and increase brand loyalty.

Delighted authenticates API requests from Hevo to access your account data with HTTP Basic authentication.


  • An active Delighted account from which data is to be ingested.

  • The API Key to provide Hevo access to your Delighted account data.

  • You are logged in as an Admin or Standard user, to obtain the API key. Else, you can obtain the API key from an administrator or a standard user. Read User Types to know about the different types of user accounts in Delighted.

Obtaining the API Key

Delighted automatically provides you with the API key for authenticating Hevo on your Delighted account. The API key does not expire and can be reused for all your Pipelines.

Note: You must be logged in as an Admin or Standard user, to obtain the API key.

  1. Log in to your Delighted account.

  2. In the Delighted home page, click Integrations.

    Click Integrations

  3. Click API.

    Click API

  4. In the API documentation page, in the Your API key field, click the copy icon to copy the API key and save it securely like any other password.

    Save API Key

Configuring Delighted as a Source

Perform the following steps to configure Delighted as the Source in your Pipeline:

  1. Click PIPELINES in the Asset Palette.

  2. Click + CREATE in the Pipelines List View.

  3. In the Select Source Type page, select Delighted.

  4. In the Configure your Delighted Source page, specify the following:

    Configure your Delighted Source

    • Pipeline Name: A unique name for the Pipeline, not exceeding 255 characters.

    • API Key: The private key that you obtained from your Delighted account.

  5. Click TEST & CONTINUE.

  6. Proceed to configuring the data ingestion and setting up the Destination.

Data Replication

Default Pipeline Frequency Minimum Pipeline Frequency Maximum Pipeline Frequency Custom Frequency Range (Hrs)
1 hr 1 hr 24 hrs 1-24

Note: You must set the custom frequency in hours as an integer value. For example, 1, 2, 3 but not 1.5 or 1.75.

Hevo fetches all the objects in Full Load mode in each run of the Pipeline.

Source Considerations

  • Pagination: An API response for each Delighted object fetches one page with up to 200 records.

  • Rate Limit: Delighted does not impose a hard limit on the number of API calls that can be made in a specific time interval. Read API Rate Limits to know more about rate limits, and configure a suitable ingestion frequency for your Pipeline.

Schema and Primary Keys

Hevo uses the following schema to upload the records in the Destination:

Data Model

The following is the list of tables (objects) that are created at the Destination when you run the Pipeline:

Object Description
Unsubscribed People Contains the list of all the unsubscribed people for your account, along with the details such as person ID, name, and email ID, and the timestamp at which they unsubscribed. Unsubscribed people do not receive any surveys.
Bounced People Contains the details of all the people who did not receive surveys due to the survey emails being bounced. The details include each person’s email address, name, and the timestamp of the bounced email.
Survey Responses Contains the details of all the survey responses for your account such as the survey ID, survey type, person’s details, survey questions, survey answers, and timestamp at which the survey was created or updated.


  • Hevo currently does not support deletes. Therefore, any data deleted in the Source may continue to exist in the Destination.

  • The data is loaded in Full Load mode in each Pipeline run. As a result, you cannot load the historical data alone at any time.

Revision History

Refer to the following table for the list of key updates made to this page:

Date Release Description of Change
Jul-05-2022 1.92 New document.
Last updated on 13 Sep 2022

Tell us what went wrong