Skip to main content

What’s New

Qrvey 8.5
Version 8.5 (LTS) of the Qrvey platform is now available to customers. This version includes several new features and performance improvements.
Learn More
End-of-life Schedule
We've added a new article that lists the features and endpoints that have been scheduled for deprecation. All features and endpoints will be supported for (1) year after the release date of the LTS version that contains the alternative.
Learn More
NodeJS Deprecation
AWS has announced that it is deprecating NodeJS 12, 14, and 16. To avoid any issues as a result of this deprecation, upgrade your instances of the Qrvey platform as described in this announcement.
Learn More
Version: 8.5

Creating a Dataset Using the Qrvey API

This article describes how to create a dataset from scratch using the Qrvey endpoint, Create Dataset. This endpoint enables you to set the properties of all dataset elements that you want to create. To learn more about how datasets work in Qrvey Composer, see Overview of Datasets.

Note: The endpoint Create Dataset creates a dataset from scratch, including creating the connection. If a connection already exists, you would use the endpoint, Create a Dataset from Existing Connection. To learn more about how connections work in Qrvey Composer, see Overview of Connections. To learn how to use the API to create a connection, see Creating a Connection Using the Qrvey API.

Before you begin, review the Qrvey documentation for the following endpoints:

Note: The endpoints described in this article require authentication tokens in the header. For more information, see Generating Security Tokens.

Gather the information needed for the required parameters in Create Dataset. At a minimum, obtain the following:

  • name. The name of the dataset that you will create.
  • The name of the connection that the dataset will use.
  • connectionId. The ID of the connection that the dataset will use.
  • connectorType. The type of connection used by the Dataset.
  • columns. Object that defines each column, datatype, column name, etc.

If you’d like to familiarize yourself with the structure of an existing dataset, use the Get Dataset endpoint to obtain the structure. For example, You can use Get Dataset to help determine if a datasetId is already taken. However, you can avoid potential naming conflicts by using the UUID function in your code when calling Create Dataset. For more information on UUIDs, see the following article on Wikipedia: Universally unique identifier.

When creating a dataset, define the following three structures:

  • The dataset object
  • The data sources associated with the datasets
  • The columns of each data source

The following sections describe how to define these structures.

Create the dataset object

The dataset object is the shell that defines the name of the dataset and contains all the parameters used to create the dataset. Use the following syntax:

"name": "NameForNewDataset"

Create the data sources associated with the datasets

Create a child object that defines all of the data sources in the dataset. Each data source is linked to a connection identified by a connectionID. Note that the connectionID alone does not specify which database/table to associate with the dataset. You need to define that information as well.

The dataSourceId should identify the connection, the database name, and the table/view name. You can use any UUID as long as you don't have the same datasourceID inside the same dataset. For example, you can have two datasets, each using the same dataSourceId but different datasetIds.

The following example creates a data source using one connection:

"datasources": [
"name": "Test",
"connectionId": "84b500d7-71c8-4b1f-adf4-f1eb0000973d",
"datasourceId": "f54dd925-2599-432c-9567-403230bdafed",
"database": "SomeDatabaseNameThatexistsInTheConnection",
"tableName": "SomeTableNameThatexistsInTheDatabase",
"connectorType": "MSSQL_LIVE",

Create the columns of each data source

Define the columns for each data source that you intend to use in the dataset. For example:

"columns": [
"appId": "TheIDofTheAPPthatcontainsThisDataset",
"connectionId": "TheiDOftheConnection,
"columnType": "NUMBER",
"columnName": "TheNameofThecolumn",
"userId": "string",
"origColumnType": "NUMBER",

The above example provides the minimum information. You can provide additional child objects such as dataSync.