Delighted is a customer feedback and survey platform that helps businesses gather feedback from their customers and measure customer satisfaction.
Power end-to-end data operations for your Delighted API with Nexla. Our bi-directional Delighted connector is purpose-built for Delighted, making it simple to ingest data, sync it across systems, and deliver it anywhere — all with no coding required. Nexla turns API-sourced data into ready-to-use, reusable data products and makes it easy to send data to Delighted or any other destination. With comprehensive monitoring, lineage tracking, and access controls, Nexla keeps your Delighted workflows fast, secure, and fully governed.
Features
Type: API
SourceDestination
Seamless API Integration: Connect to any endpoint as source or destination without coding, with automatic data product creation
Visual Composition & Chaining: Build complex integrations using visual templates, chain API calls, and compose workflows with data validation and filtering
API Proxy: Expose curated slices of your data securely with a secure and customizable API proxy that validates and transforms data on the fly
Request optimization with intelligent batching, retry, and caching to minimize API calls and costs
Before creating a Delighted credential, you need to obtain a personal API key from your Delighted account. The API key is required to authenticate with the Delighted API.
To obtain your API key, you need to have a Delighted account with API access enabled. Once you have access to your account, you can generate a personal API key from your Delighted account settings. The API key is linked to your account and is used to authenticate all API requests to the Delighted API. The API key is sent as the username in HTTP Basic Authentication, with an empty password, for all API requests to the Delighted API. For detailed information about API key setup and authentication, refer to the Delighted API documentation.
After selecting the data source/destination type, click the Add Credential tile to open the Add New Credential overlay.
New Credential Overlay – Delighted
Enter a name for the credential in the Credential Name field and a short, meaningful description in the Credential Description field.
Enter your Delighted personal API key in the API Key field. This is the personal API key you obtained from your Delighted account settings. The API key is sent as the username in HTTP Basic Authentication, with an empty password, for all API requests to the Delighted API.
Keep your API key secure and do not share it publicly. The API key provides access to your Delighted account and should be treated as sensitive information. The API key is sent as the username in HTTP Basic Authentication, with an empty password, for all API requests to the Delighted API. For detailed information about obtaining and managing API keys, see the Delighted API documentation.
Click the Save button at the bottom of the overlay. The newly added credential will now appear in a tile on the Authenticate screen during data source/destination creation.
To create a new data flow, navigate to the Integrate section, and click the New Data Flow button. Select the Delighted connector tile, then select the credential that will be used to connect to the Delighted instance, and click Next; or, create a new Delighted credential for use in this flow.
Nexla provides pre-built templates that can be used to rapidly configure data sources to ingest data from common Delighted endpoints. Select the endpoint from which this source will fetch data from the Endpoint pulldown menu. Available endpoint templates are listed in the expandable boxes below.
List Survey Responses
This endpoint retrieves all survey responses for the user account. Use this endpoint when you need to access survey response data, customer feedback, or survey results from your Delighted account.
This endpoint automatically retrieves all survey responses from your Delighted account. No additional configuration is required beyond selecting this endpoint template.
The endpoint uses GET requests to https://api.delighted.com/v1/survey_responses.json. The endpoint URL is automatically constructed based on the Delighted API base URL.
The endpoint does not use pagination and returns all survey responses in a single request.
The endpoint will return all survey responses for your account. The response data is extracted from the root-level array in the API response ($[*]), with each survey response record processed individually.
This endpoint returns all survey responses for your Delighted account. The endpoint uses a static URL (iteration.type: paging.incrementing but isPaginated: false) and does not require pagination. The response data path is $[*], which extracts all items from the root-level array in the API response. For detailed information about listing survey responses, see the Delighted API documentation.
Get Metrics
This endpoint retrieves metrics for the user account. Use this endpoint when you need to access account metrics, performance data, or analytics information from your Delighted account.
This endpoint automatically retrieves metrics from your Delighted account. No additional configuration is required beyond selecting this endpoint template.
The endpoint uses GET requests to https://api.delighted.com/v1/metrics.json. The endpoint URL is automatically constructed based on the Delighted API base URL.
The endpoint does not use pagination and returns the complete metrics in a single request.
The endpoint will return metrics for your account. The response data is extracted from the root-level object in the API response ($), and Nexla will process the entire response structure.
This endpoint returns account metrics for your Delighted account. The endpoint uses a static URL (iteration.type: static) and does not require pagination. The response data path is $, which extracts the entire root-level object from the API response. For detailed information about getting metrics, see the Delighted API documentation.
List people
This endpoint retrieves all people in the user account. Use this endpoint when you need to access people data, contact information, or person records from your Delighted account.
This endpoint automatically retrieves all people from your Delighted account. No additional configuration is required beyond selecting this endpoint template.
The endpoint uses GET requests to https://api.delighted.com/v1/people.json. The endpoint URL is automatically constructed based on the Delighted API base URL.
The endpoint uses Link header pagination, automatically fetching additional pages as needed. When a response includes a Link header with a next page URL, Nexla automatically uses it as the URL for the subsequent request to fetch the next page of results.
The endpoint will return all people in your account. The response data is extracted from the root-level array in the API response ($[*]), with each person record processed individually.
This endpoint supports pagination through the Link header mechanism. When a response includes a Link header with a next page URL, Nexla automatically uses it as the URL for the subsequent request to fetch the next page of results. The endpoint uses Link header pagination (iteration.type: link.header) through the Link header mechanism. The response data path is $[*], which extracts all items from the root-level array in the API response. For detailed information about listing people, see the Delighted API documentation.
Once the selected endpoint template has been configured, click the Test button to the right of the endpoint selection menu to retrieve a sample of the data that will be fetched. Sample data will be displayed in the Endpoint Test Result panel on the right, allowing you to verify that the source is configured correctly before saving.
Delighted data sources can also be manually configured to ingest data from any valid Delighted API endpoint, including endpoints not covered by the pre-built templates or requiring chained API calls or custom request parameters. Select the Advanced tab at the top of the configuration screen, and follow the instructions in Connect to Any API to configure the API method, endpoint URL, date/time and lookup macros, path to data, metadata, and request headers.
Delighted API endpoints typically follow the pattern https://api.delighted.com/v1/{endpoint_path}.json. The endpoint requires Basic Authentication with your API key as the username, which is handled automatically by your credential configuration. Delighted API responses may use different structures like root-level arrays or objects depending on the endpoint, so the Path to Data field should be set accordingly (for example, $[*] or $).
Once all of the relevant settings have been configured, click the Save button to save your data source configuration. Nexla will now begin ingesting data from the configured endpoint according to the configured schedule and will organize any data that it finds into one or more Nexsets.
Click the + icon on the Nexset that will be sent to the Delighted destination, and select the Send to Destination option from the menu. Select the Delighted connector from the list of available destination connectors, then select the credential that will be used to connect to the Delighted organization, and click Next; or, create a new Delighted credential for use in this flow.
Nexla provides pre-built templates that can be used to rapidly configure destinations to send data to common Delighted endpoints. Select the endpoint to which data will be sent from the Endpoint pulldown menu. Then, click on the template in the list below to expand it, and follow the instructions to configure additional endpoint settings.
Unsubscribe people
This endpoint adds a person to the user's unsubscribe list. Use this endpoint when you need to unsubscribe people from surveys or remove them from your mailing list in your Delighted account from your data sources.
This endpoint automatically unsubscribes people from your Delighted account. No additional configuration is required beyond selecting this endpoint template.
The endpoint uses POST requests to https://api.delighted.com/v1/unsubscribes.json. The endpoint URL is automatically constructed based on the Delighted API base URL.
The endpoint sends data from your Nexset as the request body in JSON format. Each record in your Nexset will be sent as a JSON object containing the unsubscribe data. The request body should follow the Delighted API specification for unsubscribing people, including required fields and field names.
Batch mode is disabled by default for this endpoint. Each record in your Nexset will be sent as a separate API request to unsubscribe a person. If you need to unsubscribe multiple people, you can send multiple records, but each will be processed as a separate request.
This endpoint automatically creates a data source to track the responses received from the Delighted API after each call.
The request body must be properly formatted JSON that matches the Delighted API specification for unsubscribing people. The endpoint requires Basic Authentication with your API key as the username, which is handled automatically by your credential configuration. The Content-Type: application/json header is automatically included in requests. Batch mode is disabled by default (batch.mode: false), so each record will be sent as a separate request. This endpoint automatically creates a data source (create.datasource: true) to track responses. For detailed information about unsubscribing people, including required fields, field names, and request formats, see the Delighted API documentation.
Schedule a survey
This endpoint creates or updates a person and schedules a survey email. Use this endpoint when you need to create or update people in your Delighted account and send them survey emails from your data sources.
This endpoint automatically creates or updates people and schedules survey emails in your Delighted account. No additional configuration is required beyond selecting this endpoint template.
The endpoint uses POST requests to https://api.delighted.com/v1/people.json. The endpoint URL is automatically constructed based on the Delighted API base URL.
The endpoint sends data from your Nexset as the request body in JSON format. Each record in your Nexset will be sent as a JSON object containing the person data and survey scheduling information. The request body should follow the Delighted API specification for sending to people, including required fields and field names.
Batch mode is disabled by default for this endpoint. Each record in your Nexset will be sent as a separate API request to create or update a person and schedule a survey. If you need to schedule surveys for multiple people, you can send multiple records, but each will be processed as a separate request.
This endpoint automatically creates a data source to track the responses received from the Delighted API after each call.
The request body must be properly formatted JSON that matches the Delighted API specification for sending to people. The endpoint requires Basic Authentication with your API key as the username, which is handled automatically by your credential configuration. The Content-Type: application/json header is automatically included in requests. Batch mode is disabled by default (batch.mode: false), so each record will be sent as a separate request. This endpoint automatically creates a data source (create.datasource: true) to track responses. For detailed information about sending to people and scheduling surveys, including required fields, field names, and request formats, see the Delighted API documentation.
Delete people By email address
This endpoint deletes people by email and all information related to them. Use this endpoint when you need to delete people from your Delighted account by their email address from your data sources.
Enter the dataset attribute that corresponds to the email address that must be deleted in the Email address dataset attribute field. This should be the name of the attribute in your Nexset that contains the email address of the person you want to delete.
The endpoint uses POST requests to https://api.delighted.com/v1/people.json/email:{email} where {email} is the email address from the dataset attribute you specify. The endpoint URL is automatically constructed based on the Delighted API base URL and the email address from your Nexset data.
The endpoint sends data from your Nexset as the request body in JSON format. Each record in your Nexset will be sent as a JSON object containing any additional deletion data. The request body should follow the Delighted API specification for deleting people, including required fields and field names.
Batch mode is disabled by default for this endpoint. Each record in your Nexset will be sent as a separate API request to delete a person. If you need to delete multiple people, you can send multiple records, but each will be processed as a separate request.
This endpoint automatically creates a data source to track the responses received from the Delighted API after each call.
The email address dataset attribute should match the name of the attribute in your Nexset that contains the email address. The endpoint uses the email address from your Nexset data to construct the URL path. The request body must be properly formatted JSON that matches the Delighted API specification for deleting people. The endpoint requires Basic Authentication with your API key as the username, which is handled automatically by your credential configuration. The Content-Type: application/json header is automatically included in requests. Batch mode is disabled by default (batch.mode: false), so each record will be sent as a separate request. This endpoint automatically creates a data source (create.datasource: true) to track responses. For detailed information about deleting people, including required fields, field names, and request formats, see the Delighted API documentation.
Delighted destinations can also be manually configured to send data to any valid Delighted API endpoint, including endpoints not covered by the pre-built templates or requiring custom request parameters. Select the Advanced tab at the top of the configuration screen, and follow the instructions in Connect to Any API to configure the API method, data format, endpoint URL, request headers, and request body.
Delighted API endpoints typically follow the pattern https://api.delighted.com/v1/{endpoint_path}.json, and the API primarily uses POST requests for data-writing operations. The endpoint requires Basic Authentication with your API key as the username, which is handled automatically by your credential configuration, and the Content-Type: application/json header is set automatically for JSON request bodies.
Once all configuration steps have been completed, click the Save button to save and create the destination. To send the data to the configured Delighted endpoint, open the destination resource menu, and select Activate.
The Nexset data will not be sent to the Delighted endpoint until the destination is activated. Destinations can be activated immediately or at a later time, providing full control over data movement.
