Dataiku DSS API
Call paths
All calls in the DSS public API are relative to the /public/api
path on the DSS server.
For example, if your DSS server is available at http://mymachine:10000/
, and you want to call the List projects API, you must make a GET request on http://mymachine:10000/public/api/projects/
Other notes
Many API calls may return additional attributes compared to the documentation. The stability of these additional attributes is not guaranteed. They may be modified or removed in future releases without notice.
All API calls will return the following two HTTP headers
DSS-API-Version
: Version of the API server handling the requestDSS-Version
: Version of the DSS backend answering the request
Project Folders ¶
Root Project Folder ¶
Get root project folderGET/project-folders/
Get the definition of the root project folder. Only the items on which the API key has the READ privilege for project folders (children) and READ_CONF for projects privilege will be listed.
Example URI
200
Definition of the root project folder
Headers
Content-Type: application/json
Body
{
"id": "Hello, world!",
"name": "Hello, world!",
"parentId": "Hello, world!",
"childrenIds": [
"Hello, world!"
],
"projectKeys": [
"Hello, world!"
]
}
Schema
{
"$schema": "http://json-schema.org/draft-04/schema#",
"type": "object",
"properties": {
"id": {
"type": "string",
"description": "ID of the project folder"
},
"name": {
"type": "string",
"description": "name of the project folder (or null if root project folder)"
},
"parentId": {
"type": "string",
"description": "the ID of the parent project folder (or null if root project folder)"
},
"childrenIds": {
"type": "array",
"description": "the list of the ID of this project folder's children"
},
"projectKeys": {
"type": "array",
"description": "the list of the project keys inside this project folder"
}
}
}
Project Folder ¶
Get a project folderGET/project-folders/{folderId}
Get the definition of a project folder. Only the items on which the API key has the READ privilege for project folders (children) and READ_CONF for projects privilege will be listed.
🔒 Required privileges : READ on this project folder
Example URI
- folderId
string
(required) Example: KdLmPU6the ID of a project folder
The folderId can be found from the get project folder API call or in the URL when accessing DSS GUI.
200
Definition of the project folder
Headers
Content-Type: application/json
Body
{
"id": "Hello, world!",
"name": "Hello, world!",
"parentId": "Hello, world!",
"childrenIds": [
"Hello, world!"
],
"projectKeys": [
"Hello, world!"
]
}
Schema
{
"$schema": "http://json-schema.org/draft-04/schema#",
"type": "object",
"properties": {
"id": {
"type": "string",
"description": "ID of the project folder"
},
"name": {
"type": "string",
"description": "name of the project folder (or null if root project folder)"
},
"parentId": {
"type": "string",
"description": "the ID of the parent project folder (or null if root project folder)"
},
"childrenIds": {
"type": "array",
"description": "the list of the ID of this project folder's children"
},
"projectKeys": {
"type": "array",
"description": "the list of the project keys inside this project folder"
}
}
}
Get project folder settingsGET/project-folders/{folderId}/settings
Get the settings of a project folder
🔒 Required privileges : ADMIN on this project folder
Example URI
- folderId
string
(required) Example: KdLmPU6the ID of a project folder
The folderId can be found from the get project folder API call or in the URL when accessing DSS GUI.
200
Settings of the project folder
Headers
Content-Type: application/json
Body
{
"name": "my folder",
"owner": "admin",
"permissions": [
{
"group": "data_scientists",
"read": true,
"writeContents": true,
"admin": false
}
]
}
Schema
{
"$schema": "http://json-schema.org/draft-04/schema#",
"type": "object",
"properties": {
"name": {
"type": "string",
"description": "name of the project folder"
},
"owner": {
"type": "string",
"description": "login of the owner of the project folder"
},
"permissions": {
"type": "array",
"description": "the list of the permissions of the project folder"
}
}
}
Update project folder settingsPUT/project-folders/{folderId}/settings
Update the settings of a project folder
🔒 Required privileges : ADMIN on this project folder
Example URI
- folderId
string
(required) Example: KdLmPU6the ID of a project folder
The folderId can be found from the get project folder API call or in the URL when accessing DSS GUI.
Headers
Content-Type: application/json
Body
{
"name": "my folder modified",
"owner": "admin",
"permissions": [
{
"group": "data_scientists",
"read": true,
"writeContents": true,
"admin": true
}
]
}
Schema
{
"$schema": "http://json-schema.org/draft-04/schema#",
"type": "object",
"properties": {
"name": {
"type": "string",
"description": "name of the project folder"
},
"owner": {
"type": "string",
"description": "login of the owner of the project folder"
},
"permissions": {
"type": "array",
"description": "the list of the permissions of the project folder"
}
}
}
204
Move a project folderPOST/project-folders/{folderId}/move{?destination}
Move a project folder into another project folder (change its parent) along with its content. You cannot move a project folder into one of its sub-folder.
🔒 Required privileges : ADMIN on this project folder, WRITE_CONTENTS on the destination project folder
Example URI
- folderId
string
(required) Example: KdLmPU6the ID of a project folder to move
The folderId can be found from the get project folder API call or in the URL when accessing DSS GUI.
- destination
string
(required) Example: dgKywsxthe ID of the destination project folder
The destination (project folder ID) can be found from the get project folder API call or in the URL when accessing DSS GUI.
204
Delete projectDELETE/project-folders/{folderId}
Permanently deletes a project folder. It must be empty: no sub-folders and no projects inside
🔒 Required privileges : ADMIN (on this project folder)
Example URI
- folderId
string
(required) Example: KdLmPU6the key of the project folder to delete
The folderId can be found from the get project folder API call or in the URL when accessing DSS GUI.
204
Create a sub-project folderPOST/project-folders/{folderId}/children{?name}
Create a sub-project folder within the current project folder.
🔒 Required privileges : WRITE_CONTENTS on the current project folder
Example URI
- folderId
string
(required) Example: KdLmPU6the ID of a project folder to move
The folderId can be found from the get project folder API call or in the URL when accessing DSS GUI.
- name
string
(required) Example: my_sub_folderthe name of the new project folder
200
Definition of the newly created project folder
Headers
Content-Type: application/json
Body
{
"id": "Hello, world!",
"name": "Hello, world!",
"parentId": "Hello, world!",
"childrenIds": [
"Hello, world!"
],
"projectKeys": [
"Hello, world!"
]
}
Schema
{
"$schema": "http://json-schema.org/draft-04/schema#",
"type": "object",
"properties": {
"id": {
"type": "string",
"description": "ID of the project folder"
},
"name": {
"type": "string",
"description": "name of the project folder (or null if root project folder)"
},
"parentId": {
"type": "string",
"description": "the ID of the parent project folder (or null if root project folder)"
},
"childrenIds": {
"type": "array",
"description": "the list of the ID of this project folder's children"
},
"projectKeys": {
"type": "array",
"description": "the list of the project keys inside this project folder"
}
}
}
Move a projectPOST/project-folders/{folderId}/projects/{projectKey}/move{?destination}
Move a project within the current project folder to another project folder
🔒 Required privileges : WRITE_CONTENTS on the destination project folder, Admin of project
Example URI
- folderId
string
(required) Example: KdLmPU6the ID of a project folder where is the project is
The folderId can be found from the get project folder API call or in the URL when accessing DSS GUI.
- projectKey
string
(required) Example: MYPROJECTthe ID of the project to move
The projectKey can be found with the list projects API call or in the URL when accessing DSS GUI.
- destination
string
(required) Example: dgKywsxthe ID of the destination project folder
The destination (project folder ID) can be found from the get project folder API call or in the URL when accessing DSS GUI.
204
Projects ¶
Projects ¶
List projectsGET/projects/{tags}
Lists the projects. Only the projects on which the API key has the READ_CONF privilege will be listed.
🔒 Required privileges : READ_CONF
Example URI
- tags
string
(optional) Default: trueComma separated list of tags. The query will only return projects having one of these tags
200
Headers
Content-Type: application/json
Body
[
{
"projectKey": "Hello, world!"
}
]
Schema
{
"$schema": "http://json-schema.org/draft-04/schema#",
"type": "array"
}
Create projectPOST/projects{?projectFolderId}
Creates a new project
🔒 Required privileges : Admin for project creation, WRITE_CONTENTS on the project folder
Example URI
- projectFolderId
string
(optional) Example: KdLmPU6the ID of the project folder in which the new project will be created (if not provided, will defaults to root project folder)
The projectFolderId can be found from the get project folder API call or in the URL when accessing DSS GUI.
A project key must match [A-Za-z_]*
Headers
Content-Type: application/json
Body
{
"projectKey": "The project key of the new project",
"name": "The name of the new project",
"owner": "The login of the owner of the new project"
}
200
Project ¶
Get project metadataGET/projects/{projectKey}/metadata
Retrieves metadata about this project.
🔒 Required privileges : ADMIN (on project)
Example URI
- projectKey
string
(required) Example: MYPROJECTthe key of a project
NB The project key is usually different than the project displayed name.
The projectKey can be found with the list projects API call or in the URL when accessing DSS GUI.
200
Headers
Content-Type: application/json
Body
{
"label" : "My first project",
"description" : "This is a sample project summary",
"shortDesc" : "sample project summary",
/* It is advised to keep tags as short words */
"tags" : [
"my tag 1",
"my tag 2",
...
],
"custom" : {
"kv" : {
"as a user" : "I can write",
"whatever" : [ "I", "want" , "here"]
}
}
}
Schema
{
"$schema": "http://json-schema.org/draft-04/schema#",
"type": "object",
"properties": {
"label": {
"type": "string",
"description": "Display name for this object"
},
"description": {
"type": "string",
"description": "Long description (Markdown) for this object"
},
"tags": {
"type": "array",
"description": "Tags of this object"
},
"custom": {
"type": "object",
"properties": {},
"description": "Custom opaque metadata"
}
}
}
Update project metadataPUT/projects/{projectKey}/metadata
Updates metadata about this project. You should only set a metadata object that has been obtained through the corresponding GET call.
🔒 Required privileges : ADMIN (on project)
Example URI
- projectKey
string
(required) Example: MYPROJECTthe key of a project
NB The project key is usually different than the project displayed name.
The projectKey can be found with the list projects API call or in the URL when accessing DSS GUI.
Headers
Content-Type: application/json
Body
{
"label" : "My first project",
"description" : "This is a sample project summary",
"shortDesc" : "sample project summary",
/* It is advised to keep tags as short words */
"tags" : [
"my tag 1",
"my tag 2",
...
],
"custom" : {
"kv" : {
"as a user" : "I can write",
"whatever" : [ "I", "want" , "here"]
}
}
}
Schema
{
"$schema": "http://json-schema.org/draft-04/schema#",
"type": "object",
"properties": {
"label": {
"type": "string",
"description": "Display name for this object"
},
"description": {
"type": "string",
"description": "Long description (Markdown) for this object"
},
"tags": {
"type": "array",
"description": "Tags of this object"
},
"custom": {
"type": "object",
"properties": {},
"description": "Custom opaque metadata"
}
}
}
204
Get project permissionsGET/projects/{projectKey}/permissions
Retrieves access permissions for this project.
🔒 Required privileges : ADMIN (on project)
Example URI
- projectKey
string
(required) Example: MYPROJECTthe key of a project
NB The project key is usually different than the project displayed name.
The projectKey can be found with the list projects API call or in the URL when accessing DSS GUI.
200
Headers
Content-Type: application/json
Body
{
"owner": "Hello, world!",
"permissions": [
{
"group": "Hello, world!",
"type": "Hello, world!"
}
]
}
Schema
{
"$schema": "http://json-schema.org/draft-04/schema#",
"type": "object",
"properties": {
"owner": {
"type": "string",
"description": "Login of the owner of the proejct"
},
"permissions": {
"type": "array",
"description": "List of group -> access level mapping"
}
}
}
Update project permissionsPUT/projects/{projectKey}/permissions
Updates access permissions for this project. You should only set a permissions object that has been obtained through the corresponding GET call.
🔒 Required privileges : ADMIN (on project)
Example URI
- projectKey
string
(required) Example: MYPROJECTthe key of a project
NB The project key is usually different than the project displayed name.
The projectKey can be found with the list projects API call or in the URL when accessing DSS GUI.
Headers
Content-Type: application/json
Body
{
"owner": "Hello, world!",
"permissions": [
{
"group": "Hello, world!",
"type": "Hello, world!"
}
]
}
Schema
{
"$schema": "http://json-schema.org/draft-04/schema#",
"type": "object",
"properties": {
"owner": {
"type": "string",
"description": "Login of the owner of the proejct"
},
"permissions": {
"type": "array",
"description": "List of group -> access level mapping"
}
}
}
204
Get project variablesGET/projects/{projectKey}/variables
Retrieves project-level variables for this project.
🔒 Required privileges : READ_CONF (on project)
Example URI
- projectKey
string
(required) Example: MYPROJECTthe key of a project
NB The project key is usually different than the project displayed name.
The projectKey can be found with the list projects API call or in the URL when accessing DSS GUI.
200
“Local” variables are not kept when deploying a project to an automation node
Headers
Content-Type: application/json
Body
{
"standard": {
"k1": "v1",
"k2": 14
},
"local": {}
}
Schema
{
"$schema": "http://json-schema.org/draft-04/schema#",
"type": "object",
"properties": {
"standard": {
"type": "object",
"properties": {},
"description": "Dictionary of \"regular\" variables for this project. Regular variables are transfered when deploying a project to the automation node"
},
"local": {
"type": "object",
"properties": {},
"description": "Dictionary of \"local\" variables for this project. Local variables are not transfered when deploying a project to the automation node. Local variables override standard variables with the same name"
}
}
}
Update project variablesPUT/projects/{projectKey}/variables
Updates project-level variables for this project. You should only set a variables object that has been obtained through the corresponding GET call.
🔒 Required privileges : WRITE_CONF (on project)
Example URI
- projectKey
string
(required) Example: MYPROJECTthe key of a project
NB The project key is usually different than the project displayed name.
The projectKey can be found with the list projects API call or in the URL when accessing DSS GUI.
“Local” variables are not kept when deploying a project to an automation node
Headers
Content-Type: application/json
Body
{
"standard": {
"k1": "v1",
"k2": 14
},
"local": {}
}
Schema
{
"$schema": "http://json-schema.org/draft-04/schema#",
"type": "object",
"properties": {
"standard": {
"type": "object",
"properties": {},
"description": "Dictionary of \"regular\" variables for this project. Regular variables are transfered when deploying a project to the automation node"
},
"local": {
"type": "object",
"properties": {},
"description": "Dictionary of \"local\" variables for this project. Local variables are not transfered when deploying a project to the automation node. Local variables override standard variables with the same name"
}
}
}
204
Delete projectDELETE/projects/{projectKey}{?dropData}
Permanently deletes a project and all its associated datasets, recipes, models, etc.
🔒 Required privileges : ADMIN (on this project)
Example URI
- projectKey
string
(required) Example: MYPROJECTthe key of the project to delete
NB The project key is usually different than the project displayed name.
The projectKey can be found with the list projects API call or in the URL when accessing DSS GUI.
- dropData
boolean
(optional) Default: falseDrop the data from any managed datasets
204
Export projectGET/projects/{projectKey}/export{?exportUploads}{?exportManaged}{?exportAnalysisModels}{?exportSavedModels}
Exports a whole project configuration and (optionally) its associated data.
Only the content of Managed Filesystem datasets and uploaded datasets can be exported.
The returned zip archive can be used in DSS import feature.
🔒 Required privileges : ADMIN (on this project)
Example URI
- projectKey
string
(required) Example: MYPROJECTthe key of a project
NB The project key is usually different than the project displayed name.
The projectKey can be found with the list projects API call or in the URL when accessing DSS GUI.
- exportUploads
boolean
(optional) Default: trueExport uploaded datasets data
- exportManaged
boolean
(optional) Default: trueExport managed Filesystem datasets data
- exportAnalysisModels
boolean
(optional) Default: trueExport trained models that are in analyses (not deployed in the flow).
- exportSavedModels
boolean
(optional) Default: trueExport saved models (deployed in the flow).
200
Headers
Content-Type: application/zip
Duplicate projectPOST/projects/{projectKey}/duplicate
Duplicate a project.
Only the content of Managed Filesystem datasets and uploaded datasets can be duplicated.
🔒 Required privileges : ADMIN (on this project)
Example URI
- projectKey
string
(required) Example: MYPROJECTthe key of a project
NB The project key is usually different than the project displayed name.
The projectKey can be found with the list projects API call or in the URL when accessing DSS GUI.
Headers
Content-Type: application/json
Body
{
"targetProjectKey": "COPYOFMYPROJECT",
"targetProjectName": "Copy+of+my+project"
"targetProjectFolderId": "KdLmPU6" /* ID of a project folder. If null, will defaults to root project folder */
"duplicationMode": "MINIMAL" /* MINIMAL, SHARING, FULL, NONE */
"exportAnalysisModels": true
"exportSavedModels": true
"exportGitRepository": true
"exportInsightsData": true
"exportUploads": true
"exportAllInputDatasets": true
"exportAllInputManagedFolders": true
"exportAllDatasets": false
"exportManagedFolders": false
"shareAllInputDatasets": false
"remapping":{
"connections":[
{
"source":"filesystem_source"
"target":"filesystem_target"
}
]
"codeEnvs":[
{
"source":"codenv_source"
"target":"codenv_target"
}
]
},
}
200
Headers
Content-Type: application/json
Body
{
"projectKey": "MYPROJECT"
"targetProjectKey": "COPYOFMYPROJECT"
"targetProjectFolderId": "KdLmPU6"
}
Push to Git remotePOST/projects/{projectKey}/actions/push-to-git-remote{?remote}
Pushes the content of a project to a previously-declared Git remote. The remote must have been added first in the “Changes” section of DSS.
DSS must be in “per-project Git” mode
🔒 Required privileges : ADMIN (on this project)
Example URI
- projectKey
string
(required) Example: MYPROJECTthe key of a project
NB The project key is usually different than the project displayed name.
The projectKey can be found with the list projects API call or in the URL when accessing DSS GUI.
- remote
string
(required) Example: originThe remote name to push to
204
Get project tagsGET/projects/{projectKey}/tags
Retrieves project-level tags for this project.
🔒 Required privileges : READ_CONF (on project)
Example URI
- projectKey
string
(required) Example: MYPROJECTthe key of a project
NB The project key is usually different than the project displayed name.
The projectKey can be found with the list projects API call or in the URL when accessing DSS GUI.
200
Headers
Content-Type: application/json
Body
{
"tags": {
"origin:sql_import": {
"color": "#ee874a"
},
"creator:admin": {
"color": "#28aadd"
},
"pg": {
"color": "#a088bd"
}
}
}
Schema
{
"$schema": "http://json-schema.org/draft-04/schema#",
"type": "object",
"properties": {
"tags": {
"type": "object",
"properties": {},
"description": "Dictionary of tags for this project."
}
}
}
Update project tagsPUT/projects/{projectKey}/tags
Updates project-level tags for this project. You should only set a tags object that has been obtained through the corresponding GET call.
🔒 Required privileges : WRITE_CONF (on project)
Example URI
- projectKey
string
(required) Example: MYPROJECTthe key of a project
NB The project key is usually different than the project displayed name.
The projectKey can be found with the list projects API call or in the URL when accessing DSS GUI.
Headers
Content-Type: application/json
Body
{
"tags": {
"origin:sql_import": {
"color": "#ee874a"
},
"creator:admin": {
"color": "#28aadd"
},
"pg": {
"color": "#a088bd"
}
}
}
Schema
{
"$schema": "http://json-schema.org/draft-04/schema#",
"type": "object",
"properties": {
"tags": {
"type": "object",
"properties": {},
"description": "Dictionary of tags for this project."
}
}
}
204
Datasets ¶
Datasets ¶
List datasetsGET/projects/{projectKey}/datasets/{?tags}{?foreign}
Lists the datasets of a project.
🔒 Required privileges : READ_CONF
Example URI
- projectKey
string
(required)the key of the project
- foreign
boolean
(optional) Default: false Example: trueIf true, also lists the datasets from other projects that are exposed to the specified project
- tags
string
(optional) Example: tag1,tag2Comma separated list of tags. The query will only return datasets having one of these tags
200
Returns an array of [Dataset] object. See GET Dataset for more information on the [Dataset] object
Headers
Content-Type: application/json
Body
[
{
"projectKey": "PKEY1",
"name": "dataset1",
"type": "Filesystem",
"params": {
"connection": "filesystem_input",
"path": "/src/dataset1"
},
"formatType": "csv",
"formatParams": {
"style": "EXCEL",
"separator": "\t"
}
}
]
Schema
{
"$schema": "http://json-schema.org/draft-04/schema#",
"type": "array"
}
Create datasetPOST/projects/{projectKey}/datasets
Creates a new dataset.
Important: most parameters and format parameters of datasets are not officially documented and may be modified in future recipes. It is recommended that you use the GET Dataset call to retrieve an existing dataset and modify it to suit your needs and create a new Dataset.
🔒 Required privileges : WRITE_CONF
Example URI
- projectKey
string
(required)the key of the project
Headers
Content-Type: application/json
Body
{
"projectKey": "PKEY1",
"name": "dataset1",
"type": "Filesystem",
"params": {
"connection": "filesystem_input",
"path": "/src/dataset1"
},
"formatType": "csv",
"formatParams": {
"style": "EXCEL",
"separator": "\t"
}
}
Schema
{
"$schema": "http://json-schema.org/draft-04/schema#",
"type": "object",
"properties": {
"projectKey": {
"type": "string",
"description": "Project key of this dataset"
},
"name": {
"type": "string",
"description": "Unique name of this dataset in its project"
},
"type": {
"type": "string",
"description": "Type of the dataset"
},
"params": {
"type": "object",
"properties": {},
"description": "Parameters of the connection to the data. The available parameters depend on the dataset type"
},
"formatType": {
"type": "string",
"description": "For file-based datasets, the name of the format"
},
"formatParams": {
"type": "object",
"properties": {},
"description": "For file-based datasets, the parameters of the format. The actual parameters depend on the format type"
},
"managed": {
"type": "boolean",
"description": "Whether this is a managed dataset. See [DSS documentation](http://doc.dataiku.com/dss/latest/concepts/#managed-and-external-datasets) for an explanation"
},
"schema": {
"type": "object",
"properties": {},
"description": "Schema of this dataset"
},
"tags": {
"type": "array",
"description": "Tags of this dataset"
}
}
}
204
Create managed datasetPOST/projects/{projectKey}/datasets/managed
Creates a new managed dataset (i.e. a dataset whose format/storage details are handled by DSS, you only need to select the name, the connection, and optionally some options).
Valid format option ids include:
-
CSV_EXCEL_GZIP
-
CSV_UNIX_GZIP
-
CSV_ESCAPING_NOGZIP_FORHIVE
-
PARQUET_HIVE
-
ORC
🔒 Required privileges : WRITE_CONF
Example URI
- projectKey
string
(required)the key of the project
Headers
Content-Type: application/json
Body
{
"name": "name_of_the_new_dataset",
"creationSettings": {
"connectionId" : "connection_where_to_store"
}
}
Or
{
"name": "name_of_the_new_dataset",
"creationSettings": {
"connectionId" : "connection_where_to_store",
"specificSettings": {
"formatOptionId": "A format option"
}
}
}
204
Dataset ¶
To build a dataset see POST job
Get dataset settingsGET/projects/{projectKey}/datasets/{datasetName}
Retrieves a Dataset object.
🔒 Required privileges : READ_CONF
Example URI
- projectKey
string
(required) Example: MYPROJECTthe key of a project
- datasetName
string
(required) Example: mydatasetthe name of a dataset
200
Headers
Content-Type: application/json
Body
{
"projectKey": "PKEY1",
"name": "dataset1",
"type": "Filesystem",
"params": {
"connection": "filesystem_input",
"path": "/src/dataset1"
},
"formatType": "csv",
"formatParams": {
"style": "EXCEL",
"separator": "\t"
}
}
Schema
{
"$schema": "http://json-schema.org/draft-04/schema#",
"type": "object",
"properties": {
"projectKey": {
"type": "string",
"description": "Project key of this dataset"
},
"name": {
"type": "string",
"description": "Unique name of this dataset in its project"
},
"type": {
"type": "string",
"description": "Type of the dataset"
},
"params": {
"type": "object",
"properties": {},
"description": "Parameters of the connection to the data. The available parameters depend on the dataset type"
},
"formatType": {
"type": "string",
"description": "For file-based datasets, the name of the format"
},
"formatParams": {
"type": "object",
"properties": {},
"description": "For file-based datasets, the parameters of the format. The actual parameters depend on the format type"
},
"managed": {
"type": "boolean",
"description": "Whether this is a managed dataset. See [DSS documentation](http://doc.dataiku.com/dss/latest/concepts/#managed-and-external-datasets) for an explanation"
},
"schema": {
"type": "object",
"properties": {},
"description": "Schema of this dataset"
},
"tags": {
"type": "array",
"description": "Tags of this dataset"
}
}
}
Update dataset settingsPUT/projects/{projectKey}/datasets/{datasetName}
Updates the settings of a Dataset.
The Dataset
object given as parameter in of a PUT call MUST have been previously obtained from a
GET dataset call at the same URL.
The object obtained with the GET method may contain undocumented attributes. You should not modify them as it could create an invalid state and thoses attributes may be removed in future releases without notice.
🔒 Required privileges : WRITE_CONF
Example URI
- projectKey
string
(required) Example: MYPROJECTthe key of a project
- datasetName
string
(required) Example: mydatasetthe name of a dataset
Headers
Content-Type: application/json
Body
{
"projectKey" : "PKEY1",
"name" : "dataset1",
"type" : "Filesystem",
"params" : {
"connection" : "filesystem_input",
"path" : "/src/dataset1"
},
"formatType" : "csv",
"formatParams" : {
"style" : "EXCEL",
"separator" : "\t"
}
...
}
Schema
{
"$schema": "http://json-schema.org/draft-04/schema#",
"type": "object",
"properties": {
"projectKey": {
"type": "string",
"description": "Project key of this dataset"
},
"name": {
"type": "string",
"description": "Unique name of this dataset in its project"
},
"type": {
"type": "string",
"description": "Type of the dataset"
},
"params": {
"type": "object",
"properties": {},
"description": "Parameters of the connection to the data. The available parameters depend on the dataset type"
},
"formatType": {
"type": "string",
"description": "For file-based datasets, the name of the format"
},
"formatParams": {
"type": "object",
"properties": {},
"description": "For file-based datasets, the parameters of the format. The actual parameters depend on the format type"
},
"managed": {
"type": "boolean",
"description": "Whether this is a managed dataset. See [DSS documentation](http://doc.dataiku.com/dss/latest/concepts/#managed-and-external-datasets) for an explanation"
},
"schema": {
"type": "object",
"properties": {},
"description": "Schema of this dataset"
},
"tags": {
"type": "array",
"description": "Tags of this dataset"
}
}
}
204
Delete datasetDELETE/projects/{projectKey}/datasets/{datasetName}{?dropData}
Deletes a dataset.
WARNING : Deleting a dataset will trigger the deletion of all associated analyses and recipes.
🔒 Required privileges : WRITE_CONF, WRITE_DATA
Example URI
- projectKey
string
(required) Example: MYPROJECTthe key of a project
- datasetName
string
(required) Example: mydatasetthe name of a dataset
- dropData
boolean
(optional) Default: false Example: false
204
Dataset metadata ¶
Get metadataGET/projects/{projectKey}/datasets/{datasetName}/metadata
Retrieves metadata about this dataset.
🔒 Required privileges : READ_METADATA on Dataset
Example URI
- projectKey
string
(required) Example: MYPROJECTthe key of a project
- datasetName
string
(required) Example: mydatasetthe name of a dataset
200
Headers
Content-Type: application/json
Body
{
"label": "dataset_name",
"tags": [
"tag1",
"tag2"
]
}
Schema
{
"$schema": "http://json-schema.org/draft-04/schema#",
"type": "object",
"properties": {
"label": {
"type": "string",
"description": "Display name for this object"
},
"description": {
"type": "string",
"description": "Long description (Markdown) for this object"
},
"tags": {
"type": "array",
"description": "Tags of this object"
},
"custom": {
"type": "object",
"properties": {},
"description": "Custom opaque metadata"
}
}
}
Sets metadataPUT/projects/{projectKey}/datasets/{datasetName}/metadata
Writes metadata about this dataset. You should only set a metadata object that has been obtained through the corresponding GET call.
🔒 Required privileges : WRITE_METADATA on Dataset
Example URI
- projectKey
string
(required) Example: MYPROJECTthe key of a project
- datasetName
string
(required) Example: mydatasetthe name of a dataset
Headers
Content-Type: application/json
Body
{
"label": "dataset_name",
"tags": [
"tag1",
"tag2"
]
}
Schema
{
"$schema": "http://json-schema.org/draft-04/schema#",
"type": "object",
"properties": {
"label": {
"type": "string",
"description": "Display name for this object"
},
"description": {
"type": "string",
"description": "Long description (Markdown) for this object"
},
"tags": {
"type": "array",
"description": "Tags of this object"
},
"custom": {
"type": "object",
"properties": {},
"description": "Custom opaque metadata"
}
}
}
200
Dataset schema ¶
Get schemaGET/projects/{projectKey}/datasets/{datasetName}/schema
Retrieves the schema of the specified dataset. The dataset’s schema is the list of its columns with their types.
🔒 Required privileges : READ_SCHEMA on Dataset
Example URI
- projectKey
string
(required)the key of a project
- datasetName
string
(required)the name of a dataset
200
The Schema
object has one attribute: columns
(an array of SchemaColumn
)
- columns array[Column]
Each SchemaColumn
has a name and a type:
-
name
string
-
type
string
-
maxLength
int
: for string type only,-1
means no maximum length
Existing types are:
-
string
-
boolean
-
tinyint, smallint, int, bigint
-
float, double
-
date
-
array, map, object
-
geopoint, geometry
Headers
Content-Type: application/json
Body
{
columns: [
{"name": "Column1", type: "string", maxLength: -1},
{"name": "Column2", type: "bigint"},
]
}
Set schemaPUT/projects/{projectKey}/datasets/{datasetName}/schema
The Schema
object given as parameter in of a PUT call MUST have been previously obtained from a
GET schema call at the same URL.
The object with the GET method may contain undocumented attributes. You should not modify them as it could create an invalid state and thoses attributes may be removed in future releases without notice.
🔒 Required privileges : WRITE_SCHEMA
Example URI
- projectKey
string
(required)the key of a project
- datasetName
string
(required)the name of a dataset
The Schema
object has one attribute: columns
(an array of SchemaColumn
)
- columns array[Column]
Each SchemaColumn
has a name and a type:
-
name
string
-
type
string
-
maxLength
int
: for string type only,-1
means no maximum length
Existing types are:
-
string
-
boolean
-
tinyint, smallint, int, bigint
-
float, double
-
date
-
array, map, object
-
geopoint, geometry
Headers
Content-Type: application/json
Body
{
columns: [
{"name": "Column1", type: "string", maxLength: -1},
{"name": "Column2", type: "bigint"},
]
}
204
Dataset data ¶
Get dataGET/projects/{projectKey}/datasets/{datasetName}/data{?format}{?formatParams}{?columns}{?partitions}{?filter}{?sampling}
Streams the content of a dataset.
🔒 Required privileges : READ_DATA on Dataset
Example URI
- projectKey
string
(required) Example: MYPROJECTthe key of a project
- datasetName
string
(required) Example: mydatasetthe name of a dataset
- format
string
(optional) Example: jsonOutput format name. Supported formats are : “json”, “tsv-excel-header” (tab-separated with header) and “tsv-excel-noheader” (tab-separated without header)
- formatParams
string
(optional)additional parameters for the chosen format, as a json string
- columns
string
(optional) Example: mycol1,mycol2List of requested columns, as a comma-separated list
- sampling
string
(optional)definition of a sampling to use when retrieving the data. By default, no sampling (returns all data)
- partitions
string
(optional) Example: 2015-07-07Partition list specification
- filter
string
(optional) Example: mycol1 > 0 && mycol3 > 0Formula to select only a subset of rows based on a boolean expression
200
The Content-Type
and the content of the request may change according to the requested format.
The default (json) output will produce an array of arrays representing the data:
Body
[
[ "a", "1"],
[ "b", "2"],
...
]
Get data - alternative versionPOST/projects/{projectKey}/datasets/{datasetName}/data
Streams the content of a dataset.
This is a variant of the previous method using POST to post large and complex requests
🔒 Required privileges : READ_DATA
Example URI
- projectKey
string
(required) Example: MYPROJECTthe key of a project
- datasetName
string
(required) Example: mydatasetthe name of a dataset
Headers
Content-Type: application/json
Body
{
"columns": [
"Hello, world!"
],
"partitions": "Hello, world!"
}
Schema
{
"$schema": "http://json-schema.org/draft-04/schema#",
"type": "object",
"properties": {
"columns": {
"type": "array",
"description": "If null, all columns are returned"
},
"partitions": {
"type": "string",
"description": "Partition spec"
}
}
}
200
The Content-Type
and the content of the request may change according to the requested format.
The default (json) output will produce an array of arrays representing the data:
Body
[
[ "a", "1"],
[ "b", "2"],
...
]
Clear dataDELETE/projects/{projectKey}/datasets/{datasetName}/data/{?partitions}
Clears the data contained in the dataset; the dataset itself is not deleted.
If a list of partition identifiers is specified, only the corresponding partitions are cleared.
🔒 Required privileges : WRITE_DATA
Example URI
- projectKey
string
(required) Example: MYPROJECTthe key of a project
- datasetName
string
(required) Example: mydatasetthe name of a dataset
- partitions
string
(optional) Example: NPList of partitions to clear, as a partitions spec
204
Dataset status ¶
List partitionsGET/projects/{projectKey}/datasets/{datasetName}/partitions
Lists the partitions of the specified dataset.
If the dataset is not partitioned, returns ["NP"]
🔒 Required privileges : READ_DATA
Example URI
- projectKey
string
(required) Example: MYPROJECTthe key of a project
- datasetName
string
(required) Example: mydatasetthe name of a dataset
200
Body
[
"2015-01-01",
"2015-01-02",
...
]
Get last metric valuesGET/projects/{projectKey}/datasets/{datasetName}/metrics/last/{?partition}
Retrieve the last values of all metrics on a given dataset (or dataset partition)
🔒 Required privileges : READ_METADATA
Example URI
- projectKey
string
(required) Example: MYPROJECTthe key of a project
- datasetName
string
(required) Example: mydatasetthe name of a dataset
- partition
string
(required) Example: 2015-02-03partition id, if the dataset is partitioned. In that case, use ALL to obtain metrics on the whole dataset
200
For each metric, a complex object is returned
Body
{
"metrics": [
{
"metric": {
"dataType": "BIGINT",
"type": "basic",
"id": "basic:SIZE",
"metricType": "SIZE"
},
"meta": {
"fullName": "Size",
"name": "Size",
"format": "filesize"
},
"partitionsWithValue": [
"2015-01-01"
],
"lastValues": [
{
"dataType": "BIGINT",
"partition": "2015-01-01",
"computed": 1461659714763,
"value": "33871"
}
]
}
]
}
Get single metric historyGET/projects/{projectKey}/datasets/{datasetName}/metrics/history/{?partition}{?metricLookup}
Retrieve the history values of a single metric on a given dataset (or dataset partition)
🔒 Required privileges : READ_METADATA
Example URI
- projectKey
string
(required) Example: MYPROJECTthe key of a project
- datasetName
string
(required) Example: mydatasetthe name of a dataset
- partition
string
(required) Example: 2015-02-03partition id, if the dataset is partitioned. In that case, use ALL to obtain metrics on the whole dataset
- metricLookup
string
(required) Example: records:COUNT_RECORDSid of the metric to get values for
200
Body
{
"lastValue": {
"partition": "2015-01-01",
"value": 33871,
"time": 1461659714763
},
"from": 1458805030618,
"to": 1461659714763,
"dataType": "BIGINT",
"metric": {
"dataType": "BIGINT",
"type": "basic",
"id": "basic:SIZE",
"metricType": "SIZE"
},
"metricId": "basic:SIZE",
"values": [
{
"partition": "2015-01-01",
"value": 33871,
"time": 1458805030618
},
{
"partition": "2015-01-01",
"value": 33871,
"time": 1458805030814
},
{
"partition": "2015-01-01",
"value": 33871,
"time": 1458805334673
}
],
"valueType": "BIGINT"
}
Actions on dataset ¶
Synchronize Hive metastorePOST/projects/{projectKey}/datasets/{datasetName}/actions/synchronizeHiveMetastore
Synchronizes the Hive table associated with the dataset, that is, updates or create the table’s so that it corresponds to the dataset’s schema.
Only makes sense on HDFS datasets
🔒 Required privileges : READ_DATA
Example URI
- projectKey
string
(required) Example: MYPROJECTthe key of a project
- datasetName
string
(required) Example: mydatasetthe name of a dataset
204
Update from Hive metastorePOST/projects/{projectKey}/datasets/{datasetName}/actions/updateFromHive
Updates the dataset from the table it’s associated with in Hive. This can change the dataset’s path, schema, partitioning scheme and format.
Only makes sense on HDFS datasets
🔒 Required privileges : READ_DATA
Example URI
- projectKey
string
(required) Example: MYPROJECTthe key of a project
- datasetName
string
(required) Example: mydatasetthe name of a dataset
204
Compute metricsPOST/projects/{projectKey}/datasets/{datasetName}/actions/computeMetrics/{?partitions}
Compute the metrics defined on the dataset. If the body is empty, the probes configured on the dataset are used; otherwise, the probes definition passed in the body are used.
🔒 Required privileges : ADMIN
Example URI
- projectKey
string
(required) Example: MYPROJECTthe key of a project
- datasetName
string
(required) Example: mydatasetthe name of a dataset
- partitions
string
(optional)List of partitions to compute metrics for, as a partitions spec
Headers
Content-Type: application/json
Body
{
"engineConfig": {
"hive": {
"active": true,
"extraConf": [
{
"key": "...",
"value": "..."
}
]
}
},
"probes": [
{
"type": "basic",
"configuration": {
"enable": "true"
}
},
{
"type": "records",
"configuration": {
"countRecords": "true"
}
}
]
}
200
Body
{
"result": {
"computed": [
{
"metricId": "basic:SIZE",
"value": "21568",
"dataType": "BIGINT"
},
{
"metricId": "COUNT_FILES",
"value": "3",
"dataType": "BIGINT"
}
]
}
}
Run checksPOST/projects/{projectKey}/datasets/{datasetName}/actions/runChecks/{?partitions}
Run the checks defined on the dataset. If the body is empty, the checks configured on the dataset are used; otherwise, the checks definition passed in the body are used.
🔒 Required privileges : ADMIN
Example URI
- projectKey
string
(required) Example: MYPROJECTthe key of a project
- datasetName
string
(required) Example: mydatasetthe name of a dataset
- partitions
string
(optional)List of partitions to run checks on, as a partitions spec
Headers
Content-Type: application/json
Body
{
"checks": [
{
"type": "numericRange",
"metricId": "basic:SIZE",
"minimum": "20000",
"minimumEnabled": true
}
]
}
200
Body
{
"result": {
"results": [
{
"check": {
"type": "numericRange",
"metricId": "basic:SIZE",
"minimum": "20000",
"minimumEnabled": true
},
"value": {
"outcome": "OK",
"message": "all good"
}
}
]
}
}
Import tables ¶
List schemasGET/projects/{projectKey}/datasets/tables-import/actions/list-schemas{?connectionName}
List schemas in a SQL connection
🔒 Required privileges : WRITE_CONF
Example URI
- projectKey
string
(required) Example: MYPROJECTthe key of a project
- connectionName
string
(required)Name of the SQL connection in which to list schemas. Use
@virtual(hive-jdbc):hivedb
for Hive.
200
Body
[
"schema1",
"schema2",
"schema3"
]
List tablesGET/projects/{projectKey}/datasets/tables-import/actions/list-tables{?connectionName}{?schemaName}
List tables in a schema of a SQL connection. If schema is empty, list tables in all schemas. Returns a reference to a future, defined by
its jobId
. If the future has no result yet, polling on the jobId
until the result is ready is needed. The list elements are
import candidates.
🔒 Required privileges : WRITE_CONF
Example URI
- projectKey
string
(required) Example: MYPROJECTthe key of a project
- connectionName
string
(required)Name of the SQL connection in which to list tables. Use
@virtual(hive-jdbc):hivedb
for Hive.- schemaName
string
(optional)Name of the schema in the SQL connection in which to list schemas.
200
Body
{
"hasResult": true,
"aborted": false,
"alive": false,
"startTime": 1561456214289,
"runningTime": 0,
"unknown": false,
"jobId": "26S2LeJw",
"result": [
{
"connectionName": "pgsql",
"table": "my_table",
"checked": false,
"datasetName": "imported_from_db",
"existingDatasetsNames": []
}
]
}
Prepare importPOST/projects/{projectKey}/datasets/tables-import/actions/prepare-from-keys
Prepare the import of selected tables (SQL or Hive). Returns a reference to a future.
🔒 Required privileges : WRITE_CONF
Example URI
- projectKey
string
(required) Example: MYPROJECTthe key of the project
Headers
Content-Type: application/json
Body
{
"keys": [
{
"connectionName": "postgres",
"name": "my_table"
},
{
"connectionName": "@virtual(hive-jdbc):hivedb",
"catalog": null,
"schema": "hivedb",
"name": "my_big_data"
}
]
}
200
Body
{
"hasResult": false,
"aborted": false,
"alive": false,
"startTime": 1561456214289,
"runningTime": 0,
"unknown": false,
"jobId": "26S2LeJw"
}
Execute importPOST/projects/{projectKey}/datasets/tables-import/actions/execute-from-candidates
Perform import from a list of table candidates (SQL or Hive). Returns a reference to a future.
🔒 Required privileges : WRITE_CONF
Example URI
- projectKey
string
(required) Example: MYPROJECTthe key of the project
Headers
Content-Type: application/json
Body
{
"sqlImportCandidates": [
{
"connectionName": "pgsql",
"table": "my_table",
"checked": false,
"datasetName": "imported_from_db",
"existingDatasetsNames": []
}
],
"hiveImportCandidates": [
{
"table": "my_big_data",
"databaseName": "hivedb",
"connectionName": "hdfs_managed",
"datasetName": "imported_from_hive",
"existingDatasetsNames": [],
"importAsHiveDataset": false,
"isView": false
}
]
}
200
Body
{
"hasResult": false,
"aborted": false,
"alive": false,
"startTime": 1561466517443,
"runningTime": 81,
"unknown": false,
"jobId": "5FmUbrN3",
"progress":
{
"states" [
{
"name": "Import tables",
"unit": "NONE",
"target": 4,
"cur": 3,
"important": false,
"depth": 9,
"startTimeStamp": 1561466517443,
"msSinceStart": 81
},
{
"name": "Create datasets",
"unit": "NONE",
"target": 1,
"cur": 0,
"important": false,
"depth": 9,
"startTimeStamp": 1561466517443,
"msSinceStart": 1
}
]
}
}
Dataset Statistics ¶
Worksheets ¶
List worksheetsGET/projects/{projectKey}/datasets/{datasetName}/statistics/worksheets/
Lists the statistics worksheets of a dataset
🔒 Required privileges : READ_CONF
Example URI
- projectKey
string
(required) Example: PKEY1Key of a project
- datasetName
string
(required) Example: dataset1Name of a dataset
200
Headers
Content-Type: application/json
Body
[
{
"projectKey": "PKEY1",
"id": "worksheet1",
"dataSpec": {
"inputDatasetSmartName": "dataset1",
"datasetSelection": {
"samplingMethod": "HEAD_SEQUENTIAL",
"maxRecords": 30000
}
},
"rootCard": {
"type": "worksheet_root",
"confidenceLevel": 0.95,
"cards": []
},
"name": "My worksheet"
}
]
Schema
{
"$schema": "http://json-schema.org/draft-04/schema#",
"type": "array"
}
Create worksheetPOST/projects/{projectKey}/datasets/{datasetName}/statistics/worksheets
Creates a new worksheet in the dataset
Important: most attributes of worksheets are not officially documented and may be modified in future releases. It is recommended that you use the GET Worksheet call to retrieve an existing worksheet and modify it to suit your needs and create a new worksheet.
🔒 Required privileges : WRITE_CONF
Example URI
- projectKey
string
(required) Example: PKEY1Key of a project
- datasetName
string
(required) Example: dataset1Name of a dataset
Headers
Content-Type: application/json
Body
{
"projectKey": "PKEY1",
"id": "worksheet1",
"dataSpec": {
"inputDatasetSmartName": "dataset1",
"datasetSelection": {
"samplingMethod": "HEAD_SEQUENTIAL",
"maxRecords": 30000
}
},
"rootCard": {
"type": "worksheet_root",
"confidenceLevel": 0.95,
"cards": []
},
"name": "My worksheet"
}
Schema
{
"$schema": "http://json-schema.org/draft-04/schema#",
"type": "object",
"properties": {
"projectKey": {
"type": "string",
"description": "Key of the project"
},
"id": {
"type": "string",
"description": "Worksheet ID"
},
"name": {
"type": "string",
"description": "Displayed name"
},
"dataSpec": {
"type": "object",
"properties": {},
"description": "Dataset and sampling settings"
},
"rootCard": {
"type": "object",
"properties": {
"id": {
"type": "string",
"description": "ID of the card"
},
"type": {
"type": "string",
"enum": [
"worksheet_root"
],
"description": "Type of the card"
},
"cards": {
"type": "string",
"description": "Cards composing the Worksheet"
}
},
"description": "Root card of the worksheet"
}
}
}
200
Get worksheetGET/projects/{projectKey}/datasets/{datasetName}/statistics/worksheets/{worksheetId}
Retrieves a worksheet object
🔒 Required privileges : READ_CONF
Example URI
- projectKey
string
(required) Example: PKEY1Key of a project
- datasetName
string
(required) Example: dataset1Name of a dataset
- worksheetId
string
(required) Example: dXs4GyID of a worksheet
200
Headers
Content-Type: application/json
Body
{
"projectKey": "PKEY1",
"id": "worksheet1",
"dataSpec": {
"inputDatasetSmartName": "dataset1",
"datasetSelection": {
"samplingMethod": "HEAD_SEQUENTIAL",
"maxRecords": 30000
}
},
"rootCard": {
"type": "worksheet_root",
"confidenceLevel": 0.95,
"cards": []
},
"name": "My worksheet"
}
Schema
{
"$schema": "http://json-schema.org/draft-04/schema#",
"type": "object",
"properties": {
"projectKey": {
"type": "string",
"description": "Key of the project"
},
"id": {
"type": "string",
"description": "Worksheet ID"
},
"name": {
"type": "string",
"description": "Displayed name"
},
"dataSpec": {
"type": "object",
"properties": {},
"description": "Dataset and sampling settings"
},
"rootCard": {
"type": "object",
"properties": {
"id": {
"type": "string",
"description": "ID of the card"
},
"type": {
"type": "string",
"enum": [
"worksheet_root"
],
"description": "Type of the card"
},
"cards": {
"type": "string",
"description": "Cards composing the Worksheet"
}
},
"description": "Root card of the worksheet"
}
}
}
Update worksheetPUT/projects/{projectKey}/datasets/{datasetName}/statistics/worksheets/{worksheetId}
Updates a worksheet
The worksheet object given as parameter in of a PUT call MUST have been previously obtained from a GET worksheet call at the same URL.
The object obtained with the GET method may contain undocumented attributes. You should not modify them as it could create an invalid state and thoses attributes may be removed in future releases without notice.
🔒 Required privileges : WRITE_CONF
Example URI
- projectKey
string
(required) Example: PKEY1Key of a project
- datasetName
string
(required) Example: dataset1Name of a dataset
- worksheetId
string
(required) Example: dXs4GyID of a worksheet
Headers
Content-Type: application/json
Body
{
"projectKey": "PKEY1",
"id": "worksheet1",
"dataSpec": {
"inputDatasetSmartName": "dataset1",
"datasetSelection": {
"samplingMethod": "HEAD_SEQUENTIAL",
"maxRecords": 30000
}
},
"rootCard": {
"type": "worksheet_root",
"confidenceLevel": 0.95,
"cards": []
},
"name": "My worksheet"
}
Schema
{
"$schema": "http://json-schema.org/draft-04/schema#",
"type": "object",
"properties": {
"projectKey": {
"type": "string",
"description": "Key of the project"
},
"id": {
"type": "string",
"description": "Worksheet ID"
},
"name": {
"type": "string",
"description": "Displayed name"
},
"dataSpec": {
"type": "object",
"properties": {},
"description": "Dataset and sampling settings"
},
"rootCard": {
"type": "object",
"properties": {
"id": {
"type": "string",
"description": "ID of the card"
},
"type": {
"type": "string",
"enum": [
"worksheet_root"
],
"description": "Type of the card"
},
"cards": {
"type": "string",
"description": "Cards composing the Worksheet"
}
},
"description": "Root card of the worksheet"
}
}
}
200
Delete worksheetDELETE/projects/{projectKey}/datasets/statistics/worksheets/{worksheetId}
Deletes a worksheet
🔒 Required privileges : WRITE_CONF
Example URI
- projectKey
string
(required) Example: MYPROJECTKey of a project
- worksheetId
string
(required) Example: dXs4GyID of a worksheet
204
Compute a worksheetPOST/projects/{projectKey}/datasets/{datasetName}/statistics/worksheets/{worksheetId}/actions/compute-worksheet
Compute worksheet results.
Returns a reference to a future, defined by its jobId
. If the future has no result yet, polling on the jobId
until the result is ready is needed.
🔒 Required privileges : READ_CONF
Example URI
- projectKey
string
(required) Example: PKEY1Key of a project
- datasetName
string
(required) Example: dataset1Name of a dataset
- worksheetId
string
(required) Example: dXs4GyID of a worksheet
200
Headers
Content-Type: application/json
Body
{
"hasResult": true,
"aborted": false,
"alive": false,
"startTime": 1561456214289,
"runningTime": 0,
"unknown": false,
"jobId": "26S2LeJw",
"result": [
{
"type": "worksheet_root",
"results": []
}
]
}
Schema
{
"$schema": "http://json-schema.org/draft-04/schema#",
"type": "object",
"properties": {}
}
Cards ¶
Compute a cardPOST/projects/{projectKey}/datasets/{datasetName}/statistics/cards/compute-card
Directly computes a card without a worksheet. Note that multiple calls will be slower than computing a worksheet because a new sample is rebuilt every time.
Returns a reference to a future, defined by its jobId
. If the future has no result yet, polling on the jobId
until the result is ready is needed.
🔒 Required privileges : READ_CONF
Example URI
- projectKey
string
(required) Example: PKEY1Key of a project
- datasetName
string
(required) Example: dataset1Name of a dataset
Headers
Content-Type: application/json
Body
{
"card": {
{
"type": "correlation_matrix",
"heatmapParams": {},
"metric": "SPEARMAN",
"columns": [
{"name": "col1", "type": "CONTINUOUS"},
{"name": "col2", "type": "CONTINUOUS"}
]
}
},
"dataSpec": {
"inputDatasetSmartName": "dataset1",
"datasetSelection": {
"samplingMethod": "HEAD_SEQUENTIAL",
"maxRecords": 30000
}
}
}
200
Headers
Content-Type: application/json
Body
{
"hasResult": true,
"aborted": false,
"alive": false,
"startTime": 1561456214289,
"runningTime": 0,
"unknown": false,
"jobId": "26S2LeJw",
"result" : [
{
"type": "correlation_matrix"
"scores": [1, 0.3, 1]
}
]
}
Schema
{
"$schema": "http://json-schema.org/draft-04/schema#",
"type": "object",
"properties": {}
}
Jobs ¶
Jobs ¶
List latest jobsGET/projects/{projectKey}/jobs{?limit}
Retrieves the list of the last jobs, as an array of JobSummary
objects as defined in in the GET job call.
🔒 Required privileges : READ_CONF
Example URI
- projectKey
string
(required) Example: MYPROJECTthe key of a project
- limit
int
(optional) Default: 0Maximum number of returned jobs, 0 for no limit.
200
Headers
Content-Type: application/json
Body
[
{
"projectKey": "Hello, world!",
"jobId": "Hello, world!",
"state": "Hello, world!"
}
]
Schema
{
"$schema": "http://json-schema.org/draft-04/schema#",
"type": "array"
}
Run jobPOST/projects/{projectKey}/jobs
Start building a list of outputs.
A successful call means that the job was successfully initilized, not that it is completed. To follow the build progress use GET job.
Returns the complete job definition, including identifier of the job
🔒 Required privileges : RUN_JOBS
Example URI
- projectKey
string
(required) Example: MYPROJECTthe key of a project
Headers
Content-Type: application/json
Body
{
"outputs": [
{
"projectKey": "Hello, world!",
"id": "Hello, world!",
"partition": "Hello, world!"
}
],
"type": "Hello, world!"
}
Schema
{
"$schema": "http://json-schema.org/draft-04/schema#",
"type": "object",
"properties": {
"outputs": {
"type": "array",
"description": "Outputs to build for the job"
},
"type": {
"type": "string",
"description": "Type of job to build. One of RECURSIVE_BUILD, NON_RECURSIVE_FORCED_BUILD, RECURSIVE_FORCED_BUILD, RECURSIVE_MISSING_ONLY_BUILD"
}
},
"required": [
"outputs"
]
}
200
Body
{
"projectKey": "Hello, world!",
"id": "Hello, world!"
}
Schema
{
"type": "object",
"properties": {
"projectKey": {
"type": "string"
},
"id": {
"type": "string"
}
},
"$schema": "http://json-schema.org/draft-04/schema#"
}
Job ¶
Get job statusGET/projects/{projectKey}/jobs/{jobId}
Retrieves the job status as a JobSummary
object summarising the state of a job and its activities.
A DSS job is a sequence of operations performed on datasets.
A job is divided into activities, each activity corresponds to a recipe run using a given set of partitions.
Example : running two recipes on 2 partitions will result in a job with 4 activities.
🔒 Required privileges : MONITOR_JOBS
Example URI
- projectKey
string
(required) Example: MYPROJECTthe key of a project
- jobId
string
(required) Example: build_something_2016_02_10_21_23_34the id of a job
200
Headers
Content-Type: application/json
Body
{
"baseStatus" : {
/* Possible status are NOT_STARTED, RUNNING, FAILED, ABORTED and DONE */
"status" : "DONE",
"jobStartTime":1442418929502,
"jobEndTime":1442418932140
}
}
AbortPOST/projects/{projectKey}/jobs/{jobId}/abort
Requests the specified job to abort.
NB It may take some time for the job to actually stop, so when the servers answers this request, the job cannot be considered stopped.
🔒 Required privileges : RUN_JOBS
Example URI
- projectKey
string
(required) Example: MYPROJECTthe key of a project
- jobId
string
(required) Example: build_something_2016_02_10_21_23_34the id of a job
204
Job logs ¶
Get job logsGET/projects/{projectKey}/jobs/{jobId}/log{?activity}
Retrieves the logs content for a job or one of its activities (if specified).
🔒 Required privileges : READ_CONF
Example URI
- projectKey
string
(required) Example: MYPROJECTthe key of a project
- jobId
string
(required) Example: build_something_2016_02_10_21_23_34the id of a job
- activity
string
(optional)Activity id from which to output the logs. If not provided return the global job logs.
200
Headers
Content-Type: text/plain
Scenarios ¶
Scenarios ¶
List scenarios of a projectGET/projects/{projectKey}/scenarios
Retrieves the list of scenarios, as an array of ScenarioWithStatus objects.
🔒 Required privileges : MONITOR_JOBS
Example URI
- projectKey
string
(required) Example: MYPROJECTthe key of a project
200
Headers
Content-Type: application/json
Body
[
{
"id": "Hello, world!",
"running": true,
"active": true
}
]
Schema
{
"$schema": "http://json-schema.org/draft-04/schema#",
"type": "array"
}
Create scenarioPOST/projects/{projectKey}/scenarios
Creates a new scenario.
Important: most parameters and format parameters of datasets are not officially documented and may be modified in future releases.
🔒 Required privileges : WRITE_CONF
Example URI
- projectKey
string
(required) Example: MYPROJECTthe key of a project
Headers
Content-Type: application/json
Body
{
"id": "scenarioId",
"active": true,
"name": "scenarioName",
"description": "",
"type": "step_based",
"params": {
"steps": []
},
"triggers": [],
"reporters": []
}
Schema
{
"$schema": "http://json-schema.org/draft-04/schema#",
"type": "object",
"properties": {
"id": {
"type": "string",
"description": "Id of the scenario"
},
"name": {
"type": "string",
"description": "Name of the scenario"
},
"type": {
"type": "string",
"description": "Type of the scenario (step_based or custom_python)"
},
"active": {
"type": "boolean",
"description": "Is this scenario active, ie responding to its triggers?"
},
"description": {
"type": "string",
"description": "Description of the scenario"
},
"params": {
"type": "object",
"properties": {},
"description": "Parameters of the scenario. Depends on the type"
},
"triggers": {
"type": "array",
"description": "Trigger definitions of the scenario"
},
"reporters": {
"type": "array",
"description": "Reporter definitions of the scenario"
}
}
}
204
Scenario ¶
To build a scenario see POST scenarios
Get a scenarioGET/projects/{projectKey}/scenarios/{scenarioId}/
Retrieves a scenario, as a Scenario object.
🔒 Required privileges : MONITOR_JOBS
Example URI
- projectKey
string
(required) Example: MYPROJECTthe key of the project of the scenario
- scenarioId
string
(required) Example: the_scenariothe id of the scenario
200
Headers
Content-Type: application/json
Body
{
"id": "scenarioId",
"active": true,
"name": "scenarioName",
"description": "",
"type": "step_based",
"params": {
"steps": []
},
"triggers": [],
"reporters": []
}
Schema
{
"$schema": "http://json-schema.org/draft-04/schema#",
"type": "object",
"properties": {
"id": {
"type": "string",
"description": "Id of the scenario"
},
"name": {
"type": "string",
"description": "Name of the scenario"
},
"type": {
"type": "string",
"description": "Type of the scenario (step_based or custom_python)"
},
"active": {
"type": "boolean",
"description": "Is this scenario active, ie responding to its triggers?"
},
"description": {
"type": "string",
"description": "Description of the scenario"
},
"params": {
"type": "object",
"properties": {},
"description": "Parameters of the scenario. Depends on the type"
},
"triggers": {
"type": "array",
"description": "Trigger definitions of the scenario"
},
"reporters": {
"type": "array",
"description": "Reporter definitions of the scenario"
}
}
}
Get the status of a scenarioGET/projects/{projectKey}/scenarios/{scenarioId}/light
Retrieves basic info and status for a scenario, as a ScenarioWithStatus object.
🔒 Required privileges : MONITOR_JOBS
Example URI
- projectKey
string
(required) Example: MYPROJECTthe key of the project of the scenario
- scenarioId
string
(required) Example: the_scenariothe id of the scenario
200
Headers
Content-Type: application/json
Body
{
"id": "Hello, world!",
"running": true,
"active": true
}
Schema
{
"$schema": "http://json-schema.org/draft-04/schema#",
"type": "object",
"properties": {
"id": {
"type": "string",
"description": "Id of the scenario"
},
"running": {
"type": "boolean",
"description": "Is this scenario currently running"
},
"active": {
"type": "boolean",
"description": "Is this scenario active, ie responding to its triggers?"
}
}
}
Get the payload of a scenario of a projectGET/projects/{projectKey}/scenarios/{scenarioId}/payload
Retrieves the “payload” of a scenario. This only makes sense for custom scenarios.
🔒 Required privileges : MONITOR_JOBS
Example URI
- projectKey
string
(required) Example: MYPROJECTthe key of the project of the scenario
- scenarioId
string
(required) Example: the_scenariothe id of the scenario
200
Headers
Content-Type: application/json
Body
{
"script": "Hello, world!"
}
Schema
{
"$schema": "http://json-schema.org/draft-04/schema#",
"type": "object",
"properties": {
"script": {
"type": "string",
"description": "Payload of the scenario"
}
}
}
Run a scenarioPOST/projects/{projectKey}/scenarios/{scenarioId}/run
Start running a scenario.
A successful call means that the job was successfully initilized, not that it is completed. To follow the build progress use the list scenario calls.
This calls takes the scenario run parameters as a JSON object body
🔒 Required privileges : RUN_JOBS
Example URI
- projectKey
string
(required) Example: MYPROJECTthe key of the project of the scenario
- scenarioId
string
(required) Example: the_scenariothe id of the scenario
Headers
Content-Type: application/json
Body
{
"triggerParam1": "value1",
"triggerParam2": 49
}
Schema
{
"$schema": "http://json-schema.org/draft-04/schema#",
"type": "object",
"properties": {}
}
200
Body
Does not return any specific answer
Abort a scenarioPOST/projects/{projectKey}/scenarios/{scenarioId}/abort
Abort a running scenario.
🔒 Required privileges : RUN_JOBS
Example URI
- projectKey
string
(required) Example: MYPROJECTthe key of the project of the scenario
- scenarioId
string
(required) Example: the_scenariothe id of the scenario
Headers
Content-Type: application/json
Body
Does not take any parameters
200
Body
Does not return any specific answer
Get last runsGET/projects/{projectKey}/scenarios/{scenarioId}/get-last-runs/{?limit}
Retrieve the last runs of this scenario
🔒 Required privileges : RUN_JOBS
Example URI
- projectKey
string
(required) Example: MYPROJECTthe key of the project of the scenario
- scenarioId
string
(required) Example: the_scenariothe id of the scenario
- limit
integer
(optional) Example: 200the number of runs to retrieve
200
Headers
Content-Type: application/json
Body
[
{
"runId": "2016-04-15-16-57-37-759",
"start": 1460732257757,
"end": 1460732282032,
"scenario": {
"name": "steps scenario",
"automationLocal": false,
"active": false,
"type": "step_based",
"id": "STEPS_SCENARIO",
"projectKey": "PROJ",
"description": "sqdsq"
},
"variables": {},
"result": {
"outcome": "SUCCESS",
"type": "SCENARIO_DONE"
}
}
]
Schema
{
"$schema": "http://json-schema.org/draft-04/schema#",
"type": "object",
"properties": {}
}
Get run from trigger runGET/projects/scenarios/get-run-for-trigger/{?triggerId}{?triggerRunId}
Retrieve the run initiated by the given run of the trigger
🔒 Required privileges : RUN_JOBS
Example URI
- triggerId
string
(required)the unique identifier of the trigger
- triggerRunId
string
(required)the identifier of the run of the trigger
200
Headers
Content-Type: application/json
Body
{
"stepRuns": [
{
"end": 1460732282031,
"start": 1460732257765,
"step": {
"type": "build_flowitem",
"id": "build_0_true_d_train_set_prepared_split_year",
"name": "build dataset train_set_prepared_split_year"
},
"result": {
"start": 1460732257767,
"end": 1460732282031,
"outcome": "SUCCESS",
"type": "STEP_DONE"
},
"additionalReportItems": [
{
"start": 1460732258480,
"end": 1460732279882,
"outcome": "SUCCESS",
"target": {
"type": "SAVED_MODEL",
"projectKey": "SCEN",
"modelId": "u4yPbO2B"
},
"warnings": {
"totalCount": 0,
"warnings": {}
},
"versionId": "1460732258821",
"type": "BUILT_MODEL"
},
{
"start": 1460732258001,
"outcome": "SUCCESS",
"end": 1460732282013,
"target": {
"type": "JOBS"
},
"jobId": "sched_build_2016-04-15T14-57-37.770",
"type": "JOB_EXECUTED"
}
],
"runId": "2016-04-15-16-57-37-766"
}
],
"scenarioRun": {
"runId": "2016-04-15-16-57-37-759"
}
}
Schema
{
"$schema": "http://json-schema.org/draft-04/schema#",
"type": "object",
"properties": {}
}
Get details for a runGET/projects/{projectKey}/scenarios/{scenarioId}/{runId}
Retrieve the details of a specific run of the scenario. The details include the outcomes of each step launched by the scenario, as well as their output if they offer one.
🔒 Required privileges : RUN_JOBS
Example URI
- projectKey
string
(required) Example: MYPROJECTthe key of the project of the scenario
- scenarioId
string
(required) Example: the_scenariothe id of the scenario
- runId
string
(required)identifier of the run
200
Headers
Content-Type: application/json
Body
{
"stepRuns": [
{
"end": 1460732282031,
"start": 1460732257765,
"step": {
"type": "build_flowitem",
"id": "build_0_true_d_train_set_prepared_split_year",
"name": "build dataset train_set_prepared_split_year"
},
"result": {
"start": 1460732257767,
"end": 1460732282031,
"outcome": "SUCCESS",
"type": "STEP_DONE"
},
"additionalReportItems": [
{
"start": 1460732258480,
"end": 1460732279882,
"outcome": "SUCCESS",
"target": {
"type": "SAVED_MODEL",
"projectKey": "SCEN",
"modelId": "u4yPbO2B"
},
"warnings": {
"totalCount": 0,
"warnings": {}
},
"versionId": "1460732258821",
"type": "BUILT_MODEL"
},
{
"start": 1460732258001,
"outcome": "SUCCESS",
"end": 1460732282013,
"target": {
"type": "JOBS"
},
"jobId": "sched_build_2016-04-15T14-57-37.770",
"type": "JOB_EXECUTED"
}
],
"runId": "2016-04-15-16-57-37-766"
}
],
"scenarioRun": {
"runId": "2016-04-15-16-57-37-759"
}
}
Schema
{
"$schema": "http://json-schema.org/draft-04/schema#",
"type": "object",
"properties": {}
}
Get a run of a triggerGET/projects/{projectKey}/scenarios/trigger/{scenarioId}/{triggerId}{?triggerRunId}
Retrieve the details of a specific run of a trigger in the scenario.
🔒 Required privileges : RUN_JOBS
Example URI
- projectKey
string
(required) Example: MYPROJECTthe key of the project of the scenario
- scenarioId
string
(required) Example: the_scenariothe id of the scenario
- triggerId
string
(required)identifier of the trigger
- triggerRunId
string
(required)identifier of the run of the trigger
200
Headers
Content-Type: application/json
Body
{
"scenarioId": "sId",
"timestamp": 1506610145253,
"trigger": {
"delay": 0,
"active": false,
"type": "manual",
"id": "manual",
"name": "API run"
},
"params": {},
"runId": "2017-09-28-16-49-05-255",
"cancelled": false,
"projectKey": "PKEY1"
}
Schema
{
"$schema": "http://json-schema.org/draft-04/schema#",
"type": "object",
"properties": {}
}
Update scenario settingsPUT/projects/{projectKey}/scenarios/{scenarioId}
Updates the settings of a Scenario.
The [Scenario
] object given as parameter in of a PUT call MUST have been previously obtained from a
[GET scenario] call at the same URL.
The object obtained with the GET method may contain undocumented attributes. You should not modify them as it could create an invalid state and thoses attributes may be removed in future releases without notice.
🔒 Required privileges : WRITE_CONF
Example URI
- projectKey
string
(required) Example: MYPROJECTthe key of the project of the scenario
- scenarioId
string
(required) Example: the_scenariothe id of the scenario
Headers
Content-Type: application/json
Body
{
"projectKey" : "PKEY1",
"name" : "scenarioId",
"type" : "step_based",
"params" : {
}
...
}
Schema
{
"$schema": "http://json-schema.org/draft-04/schema#",
"type": "object",
"properties": {
"id": {
"type": "string",
"description": "Id of the scenario"
},
"name": {
"type": "string",
"description": "Name of the scenario"
},
"type": {
"type": "string",
"description": "Type of the scenario (step_based or custom_python)"
},
"active": {
"type": "boolean",
"description": "Is this scenario active, ie responding to its triggers?"
},
"description": {
"type": "string",
"description": "Description of the scenario"
},
"params": {
"type": "object",
"properties": {},
"description": "Parameters of the scenario. Depends on the type"
},
"triggers": {
"type": "array",
"description": "Trigger definitions of the scenario"
},
"reporters": {
"type": "array",
"description": "Reporter definitions of the scenario"
}
}
}
204
Update basic scenario settingsPUT/projects/{projectKey}/scenarios/{scenarioId}/light
Updates the basic settings of a Scenario, given a BasicScenarioSettings object.
This is only useful to change the “active” status of a scenario
🔒 Required privileges : WRITE_CONF
Example URI
- projectKey
string
(required) Example: MYPROJECTthe key of the project of the scenario
- scenarioId
string
(required) Example: the_scenariothe id of the scenario
Headers
Content-Type: application/json
Body
{
"id": "Hello, world!",
"running": true,
"active": true
}
Schema
{
"$schema": "http://json-schema.org/draft-04/schema#",
"type": "object",
"properties": {
"id": {
"type": "string",
"description": "Id of the scenario"
},
"running": {
"type": "boolean",
"description": "Is this scenario currently running"
},
"active": {
"type": "boolean",
"description": "Is this scenario active, ie responding to its triggers?"
}
}
}
204
Update scenario payloadPUT/projects/{projectKey}/scenarios/{scenarioId}/payload
Updates the payload of a Scenario.
🔒 Required privileges : WRITE_CONF
Example URI
- projectKey
string
(required) Example: MYPROJECTthe key of the project of the scenario
- scenarioId
string
(required) Example: the_scenariothe id of the scenario
Headers
Content-Type: application/json
Body
{
"script": "Hello, world!"
}
Schema
{
"$schema": "http://json-schema.org/draft-04/schema#",
"type": "object",
"properties": {
"script": {
"type": "string",
"description": "Payload of the scenario"
}
}
}
204
Machine Learning - Lab ¶
Machine Learning Lab - Analysis ¶
This API allows you to create and manage visual analysis and create ML tasks in it, i.e. Machine Learning models
List analysesGET/projects/{projectKey}/lab
Lists all the visual analyses of the project.
🔒 Required privileges : READ_CONF on the project
Example URI
- projectKey
string
(required)the identifier of a project
200
Headers
Content-Type: application/json
Body
[
{
"analysisId": "Hello, world!",
"analysisName": "Hello, world!",
"inputDataset": "Hello, world!"
}
]
Schema
{
"$schema": "http://json-schema.org/draft-04/schema#",
"type": "array"
}
Create a visual analysisPOST/projects/{projectKey}/lab
Create a new visual analysis
🔒 Required privileges : WRITE_CONF on the project
Example URI
- projectKey
string
(required)the identifier of a project
Headers
Content-Type: application/json
Body
{
"analysisName": "Hello, world!",
"inputDataset": "Hello, world!"
}
Schema
{
"$schema": "http://json-schema.org/draft-04/schema#",
"type": "object",
"properties": {
"analysisName": {
"type": "string",
"description": "Name of the visual analysis"
},
"inputDataset": {
"type": "string",
"description": "Name of the dataset used as input of the visual analysis and ML Task"
}
}
}
200
Body
+ Body (application/json)
{
"id": "rqlx0Vd1"
}
Get details about analysisGET/projects/{projectKey}/lab/{analysisId}
Get all the details about a visual analysis of the project.
🔒 Required privileges : READ_CONF on the project
Example URI
- projectKey
string
(required)the identifier of a project
- analysisId
string
(required)the identifier of a analysis
200
Headers
Content-Type: application/json
Body
{
"projectKey": "PROJECT",
"id": "rqlx0Vd1",
"inputDatasetSmartName": "my_dataset",
"script": [...]
"charts": [...]
"name": "My new analysis",
"versionTag": {...},
"creationTag": {...},
"tags": [...],
"checklists": {...}
}
Update a visual analysisPUT/projects/{projectKey}/lab/{analysisId}
Update a visual analysis
🔒 Required privileges : WRITE_CONF on the project
Example URI
- projectKey
string
(required)the identifier of a project
- analysisId
string
(required)the identifier of a analysis
Headers
Content-Type: application/json
Body
{
"projectKey": "PROJECT",
"id": "rqlx0Vd1",
"inputDatasetSmartName": "my_dataset",
"script": [...]
"charts": [...]
"name": "My new analysis v2",
"versionTag": {...},
"creationTag": {...},
"tags": [...],
"checklists": {...}
}
200
Body
+ Body (application/json)
{
"msg": "Saved analysis settings for PROJECT rqlx0Vd1"
}
Delete a visual analyisDELETE/projects/{projectKey}/lab/{analysisId}
Delete a visual analysis
🔒 Required privileges : WRITE_CONF on the project
Example URI
- projectKey
string
(required)the identifier of a project
- analysisId
string
(required)the identifier of a analysis
200
Body
+ Body (application/json)
{
"msg": "Deleted analysis rqlx0Vd1 in PROJECT"
}
List ML tasksGET/projects/{projectKey}/lab/{analysisId}/models
Get all the ML task of a visual analysis.
🔒 Required privileges : READ_CONF on the project
Example URI
- projectKey
string
(required)the identifier of a project
- analysisId
string
(required)the identifier of a analysis
200
Headers
Content-Type: application/json
Body
{
"mlTasks": [
{
"analysisId": "Hello, world!",
"mlTaskId": "Hello, world!",
"analysisName": "Hello, world!",
"mlTaskName": "Hello, world!",
"taskType": "Hello, world!",
"inputDataset": "Hello, world!"
}
]
}
Schema
{
"$schema": "http://json-schema.org/draft-04/schema#",
"type": "object",
"properties": {
"mlTasks": {
"type": "array",
"description": "the references to the ML Tasks"
}
}
}
Create a new ML taskPOST/projects/{projectKey}/lab/{analysisId}/models
Create a new visual analysis
🔒 Required privileges : WRITE_CONF on the project
Example URI
- projectKey
string
(required)the identifier of a project
- analysisId
string
(required)the identifier of a analysis
Headers
Content-Type: application/json
Body
{
"analysisName": "Hello, world!",
"inputDataset": "Hello, world!"
}
Schema
{
"$schema": "http://json-schema.org/draft-04/schema#",
"type": "object",
"properties": {
"analysisName": {
"type": "string",
"description": "Name of the visual analysis"
},
"inputDataset": {
"type": "string",
"description": "Name of the dataset used as input of the visual analysis and ML Task"
}
}
}
200
Body
+ Body (application/json)
{
"analysisId": "jSEUY6wx",
"mlTaskId": "1xlwvos5"
}
Machine Learning Lab - ML tasks ¶
This API allows you to create, manage, and train ML tasks, i.e. Machine Learning model labs within a DSS visual analysis.
You can manage both Prediction and Clustering ML Tasks.
List ML TasksGET/projects/{projectKey}/models/lab
Lists all the ML Tasks of the project (together with their containing visual analysis).
🔒 Required privileges : READ_CONF on the project
Example URI
- projectKey
string
(required)the identifier of a project
200
Headers
Content-Type: application/json
Body
{
"mlTasks": [
{
"analysisId": "Hello, world!",
"mlTaskId": "Hello, world!",
"analysisName": "Hello, world!",
"mlTaskName": "Hello, world!",
"taskType": "Hello, world!",
"inputDataset": "Hello, world!"
}
]
}
Schema
{
"$schema": "http://json-schema.org/draft-04/schema#",
"type": "object",
"properties": {
"mlTasks": {
"type": "array",
"description": "the references to the ML Tasks"
}
}
}
Create a ML TaskPOST/projects/{projectKey}/models/lab
Create a new visual analysis and ML task
🔒 Required privileges : WRITE_CONF on the project
Example URI
- projectKey
string
(required)the identifier of a project
Headers
Content-Type: application/json
Body
{
"analysisName": "Hello, world!",
"inputDataset": "Hello, world!",
"taskType": "Hello, world!",
"predictionType": "Hello, world!",
"targetVariable": "Hello, world!",
"backendType": "Hello, world!",
"sparkConfig": "Hello, world!",
"guessPolicy": "Hello, world!"
}
Schema
{
"$schema": "http://json-schema.org/draft-04/schema#",
"type": "object",
"properties": {
"analysisName": {
"type": "string",
"description": "Name of the analysis to create"
},
"inputDataset": {
"type": "string",
"description": "Name of the input dataset"
},
"taskType": {
"type": "string",
"description": "one of PREDICTION or CLUSTERING"
},
"predictionType": {
"type": "string",
"description": "only for PREDICTION task. One of MULTICLASS, BINARY_CLASSIFICATION, REGRESSION"
},
"targetVariable": {
"type": "string",
"description": "Name of the target variable (only for PREDICTION)"
},
"backendType": {
"type": "string",
"description": "ML backend to use, one of PY_MEMORY, MLLIB or H2O"
},
"sparkConfig": {
"type": "string",
"description": "only if backend is Spark-enabled (MLLIB or H2O)"
},
"guessPolicy": {
"type": "string",
"description": "Policy to use for setting the default parameters. Valid values for prediction are: DEFAULT, SIMPLE_FORMULA, DECISION_TREE, EXPLANATORY and PERFORMANCE. Valid values for clustering are: KMEANS and ANOMALY_DETECTION"
}
}
}
204
Machine learning lab - MLTask ¶
Get the settings of a ML TaskGET/projects/{projectKey}/models/lab/{analysisId}/{mlTaskId}/settings
Gets the settings of a single ML task.
The exact structure of the settings may vary. The Python API client can serve as reference for importing settings.
🔒 Required privileges : READ_CONF on the project
Example URI
- projectKey
string
(required)the key of a project
- analysisId
string
(required)id of the containing visual analysis
- mlTaskId
string
(required)id of the ML task
200
Headers
Content-Type: application/json
Body
{
"taskType" : "PREDICTION",
"targetVariable" : "my_variable" /* Only for PREDICTION tasks */
"modeling" : { /* Modeling settings */ },
"preprocessing" : { /* Preprocessing settings */ }
...
}
Get the status of a ML TaskGET/projects/{projectKey}/models/lab/{analysisId}/{mlTaskId}/status
Gets the status of a single ML task. The main usage of the status is to know if the MLTask is currently being guessed (initial discovery) or trained.
The exact structure of the status may vary. The Python API client can serve as reference for importing settings.
🔒 Required privileges : READ_CONF on the project
Example URI
- projectKey
string
(required)the key of a project
- analysisId
string
(required)id of the containing visual analysis
- mlTaskId
string
(required)id of the ML task
200
Headers
Content-Type: application/json
Body
{
"training" : true,
"guessing": false,
"fullModelIds" : [
{"id": "model1", "fullModelId" : "My-Full-opaque-id", "training" :false}
]
...
}
Re-guess a ML TaskPOST/projects/{projectKey}/models/lab/{analysisId}/{mlTaskId}/guess{?predictionType}
🔒 Required privileges : WRITE_CONF on the project
Example URI
- projectKey
string
(required)the identifier of a project
- analysisId
string
(required)the identifier of a visual analysis
- mlTaskId
string
(required)the identifier of the ML task
- predictionType
string
(optional) Example: REGRESSIONthe prediction type to be used to guess the parameters
Choices:
REGRESSION
BINARY_CLASSIFICATION
MULTICLASS
200
Headers
Content-Type: application/json
Body
{
"taskType" : "PREDICTION",
"predictionType": "REGRESSION",
"targetVariable" : "my_variable" /* Only for PREDICTION tasks */
"modeling" : { /* Modeling settings */ },
"preprocessing" : { /* Preprocessing settings */ }
...
}
Start training a ML TaskPOST/projects/{projectKey}/models/lab/{analysisId}/{mlTaskId}/train
Starts training a ML Task. This call returns immediately. Poll on “Get status” afterwards to wait for training to complete.
Request body is not mandatory.
🔒 Required privileges : READ_CONF on the project
Example URI
- projectKey
string
(required)the key of a project
- analysisId
string
(required)id of the containing visual analysis
- mlTaskId
string
(required)id of the ML task
Headers
Content-Type: application/json
Body
{
"sessionName": "short-name",
"sessionDescription": "longer description of this specific training session"
}
204
Get the snippets of a set of trained modelsGET/projects/{projectKey}/models/lab/{analysisId}/{mlTaskId}/models-snippets
Gets the snippets (short summary) of a set of trained models for this MLTask. The exact structure of the snippet may vary. The Python API client can serve as reference for importing settings.
🔒 Required privileges : READ_CONF on the project
Example URI
- projectKey
string
(required)the key of a project
- analysisId
string
(required)id of the containing visual analysis
- mlTaskId
string
(required)id of the ML task
Headers
Content-Type: application/json
Body
{
"modelsIds" : [
"id-1", /* The ids must match the fullModelIds returned by the status call */
"id-2"
]
}
200
Headers
Content-Type: application/json
Body
{
"id-1" : {
/* Snippet data for model id-1 */
},
"id-2" : {
/* Snippet data for model id-2 */
}
}
Machine learning lab - Single model ¶
Get the details of a trained modelGET/projects/{projectKey}/models/lab/{analysisId}/{mlTaskId}/models/{modelFullId}/details
Gets the details of this trained model.
The exact structure of the status may vary. The Python API client can serve as reference for importing settings.
🔒 Required privileges : READ_CONF on the project
Example URI
- projectKey
string
(required)the key of a project
- analysisId
string
(required)id of the containing visual analysis
- mlTaskId
string
(required)id of the ML task
- modelFullId
string
(required)model id as returned by the get-model-snippets call
200
Headers
Content-Type: application/json
Body
{
"trainInfo" : { ... },
"userMeta" : { ... },
"perf" : { ... }
...
}
Saves user metadata for a trained modelPUT/projects/{projectKey}/models/lab/{analysisId}/{mlTaskId}/models/{modelFullId}/user-meta
Updates the user metadata of a model. You must only PUT the “userMeta” field of a previously-retrieved model-details object.
The exact structure of the user meta may vary. The Python API client can serve as reference for importing settings.
🔒 Required privileges : WRITE_CONF on the project
Example URI
- projectKey
string
(required)the key of a project
- analysisId
string
(required)id of the containing visual analysis
- mlTaskId
string
(required)id of the ML task
- modelFullId
string
(required)model id as returned by the get-model-snippets call
Headers
Content-Type: application/json
Body
{
"name": "Name",
"description" : "Description",
"clusterLabels" : [ ... ],
"tags" : ["tag1", "tag2"]
}
204
Deploy a trained model to FlowPOST/projects/{projectKey}/models/lab/{analysisId}/{mlTaskId}/models/{modelFullId}/actions/deployToFlow
Deploys a trained model from this ML Task to a saved model + train recipe in the Flow.
🔒 Required privileges : WRITE_CONF on the project
Example URI
- projectKey
string
(required)the key of a project
- analysisId
string
(required)id of the containing visual analysis
- mlTaskId
string
(required)id of the ML task
- modelFullId
string
(required)model id as returned by the get-model-snippets call
Headers
Content-Type: application/json
Body
{
"trainDatasetRef": "Name of the train dataset to use",
"testDatasetRef": "Name of the test dataset to use (if using EXPLICIT_EXTRACT splitting)",
"modelName": "Name of the saved model in Flow",
"redoOptimization": true
}
200
Headers
Content-Type: application/json
Body
{
"savedModelId": "identifier_of_the_new_saved_model",
"trainRecipeName": "name_of_the_new_train_recipe"
}
Get scoring jar of a trained modelGET/projects/{projectKey}/models/lab/{analysisId}/{mlTaskId}/models/{modelFullId}/scoring-jar{?fullClassName}{?includeLibs}
Get the scoring jar of a trained model, provided that you have the license to do so and that the model is compatible with optimized scoring.
🔒 Required privileges : READ_CONF on the project
Example URI
- projectKey
string
(required)the key of a project
- analysisId
string
(required)id of the containing visual analysis
- mlTaskId
string
(required)id of the ML task
- modelFullId
string
(required)model id as returned by the get-model-snippets call
- fullClassName
string
(optional) Example: model.Modelthe fully-qualified Java class name for the model
- includeLibs
boolean
(optional) Example: falsewether to include scoring libraries in the jar
200
Headers
Content-Type: application/java-archive
Get scoring PMML of a trained modelGET/projects/{projectKey}/models/lab/{analysisId}/{mlTaskId}/models/{modelFullId}/scoring-pmml
Get the scoring PMML of a trained model, provided that you have the license to do so and that the model is compatible with PMML scoring.
🔒 Required privileges : READ_CONF on the project
Example URI
- projectKey
string
(required)the key of a project
- analysisId
string
(required)id of the containing visual analysis
- mlTaskId
string
(required)id of the ML task
- modelFullId
string
(required)model id as returned by the get-model-snippets call
200
Headers
Content-Type: application/xml
Compute subpopulation analyses of a trained modelPOST/projects/{projectKey}/models/lab/{analysisId}/{mlTaskId}/models/{modelFullId}/subpopulation-analyses
Launch computation of subpopulation analyses for a trained model. Returns a reference to a future.
🔒 Required privileges : WRITE_CONF on the project
Example URI
- projectKey
string
(required)the key of a project
- analysisId
string
(required)id of the containing visual analysis
- mlTaskId
string
(required)id of the ML task
- modelFullId
string
(required)model id as returned by the get-model-snippets call
Headers
Content-Type: application/json
Body
{
"features": ["my_col1", "my_col2"],
"computationParams": { // optional
"sample_size": 10000, // optional, default value is 10000
"random_state": 1337, // optional, default value is 1337
"n_jobs": 1, // optional, default value is 1
"debug_mode": false, // optional, default value is false
}
}
200
Headers
Content-Type: application/json
Body
{
"hasResult": false,
"aborted": false,
"alive": true,
"startTime": 1561456214289,
"runningTime": 0,
"unknown": false,
"jobId": "26S2LeJw"
}
Get subpopulation analyses of a trained modelGET/projects/{projectKey}/models/lab/{analysisId}/{mlTaskId}/models/{modelFullId}/subpopulation-analyses
Get all subpopulation analyses computed for this trained model.
🔒 Required privileges : READ_CONF on the project
Example URI
- projectKey
string
(required)the key of a project
- analysisId
string
(required)id of the containing visual analysis
- mlTaskId
string
(required)id of the ML task
- modelFullId
string
(required)model id as returned by the get-model-snippets call
200
Headers
Content-Type: application/json
Body
{
'allDataset': {
'nbRecords': 10000,
'weightedNbRecords': 10000.0,
'randomState': 1337,
'onSample': true,
'perf': { ... perf ... }
},
'subpopulationAnalyses': [
{
'computed_as_type': 'CATEGORY',
'feature': 'my_col1',
'isDate': false,
'sameNumRowsAsSplit': true,
'nbRecords': 10000,
'weightedNbRecords': 10000.0,
'onSample': true,
'randomState': 1337,
'modalities': [
{
'value': 'modality 1',
'count': 2489,
'weightedCount': 2489.0
'excluded': false,
'missing_values': false,
'perf': { ... perf ... },
...
},
{
'value': 'modality 2',
'count': 2329,
'weightedCount': 2329.0
'excluded': true,
'reason': 'ONECLASS'
'missing_values': false,
...
},
{
'value': 'modality 3',
'count': 1428,
'weightedCount': 1428.0
'excluded': false,
'missing_values': false,
'perf': { ... perf ... },
...
},
...
],
},
]
}
Compute partial dependencies of a trained modelPOST/projects/{projectKey}/models/lab/{analysisId}/{mlTaskId}/models/{modelFullId}/partial-dependencies
Launch computation of partial dependencies for a trained model. Returns a reference to a future.
🔒 Required privileges : WRITE_CONF on the project
Example URI
- projectKey
string
(required)the key of a project
- analysisId
string
(required)id of the containing visual analysis
- mlTaskId
string
(required)id of the ML task
- modelFullId
string
(required)model id as returned by the get-model-snippets call
Headers
Content-Type: application/json
Body
{
"features": ["my_col1", "my_col2"],
"computationParams": { // optional
"sample_size": 10000, // optional, default value is 10000
"random_state": 1337, // optional, default value is 1337
"n_jobs": 1, // optional, default value is 1
"debug_mode": false, // optional, default value is false
}
}
200
Headers
Content-Type: application/json
Body
{
"hasResult": false,
"aborted": false,
"alive": true,
"startTime": 1561456214289,
"runningTime": 0,
"unknown": false,
"jobId": "26S2LeJw"
}
Get partial dependencies of a trained modelGET/projects/{projectKey}/models/lab/{analysisId}/{mlTaskId}/models/{modelFullId}/partial-dependencies
Get all partial dependencies computed for this trained model.
🔒 Required privileges : READ_CONF on the project
Example URI
- projectKey
string
(required)the key of a project
- analysisId
string
(required)id of the containing visual analysis
- mlTaskId
string
(required)id of the ML task
- modelFullId
string
(required)model id as returned by the get-model-snippets call
200
Headers
Content-Type: application/json
Body
{
"partialDependencies": [
{
'feature': 'EDU',
'nbRecords': 500,
'onSample': true,
'randomState': 1337,
'categories': ...,
'data': ...,
'distribution': ...,
...
},
...
]
}
Machine Learning - Saved models ¶
Saved models ¶
This API allows you to manage and get status of saved models. To create a saved model, deploy it from a ML Task.
You can manage both Prediction and Clustering Saved models.
List saved modelsGET/projects/{projectKey}/savedmodels
Lists all the saved models of the project
🔒 Required privileges : READ_CONF on the project
Example URI
- projectKey
string
(required)The key of the project
200
Headers
Content-Type: application/json
Body
[
{
"id" :"sq210wq2"
"type" : "PREDICTION"
},
...
]
Saved model ¶
List versionsGET/projects/{projectKey}/savedmodels/{savedModelId}/versions
Lists all versions of a saved model.
🔒 Required privileges : READ_CONF on the project
Example URI
- projectKey
string
(required)The key of the project
- savedModelId
string
(required)Identifier of the saved model
200
Headers
Content-Type: application/json
Body
[
{
"id" : "1235012190392",
"active" : true,
"trainDate" : 1230944860592
},
...
]
Saved model version ¶
Get snippet of a versionGET/projects/{projectKey}/savedmodels/{savedModelId}/versions/{versionId}/snippet
Gets snippet (short summary) of a single version.
The exact structure of the snippet may vary. The Python API client can serve as reference for importing settings.
🔒 Required privileges : READ_CONF on the project
Example URI
- projectKey
string
(required)The key of the project
- savedModelId
string
(required)Identifier of the saved model
- versionId
string
(required)Version identifier
200
Headers
Content-Type: application/json
Body
{
/* Snippet data */
}
Get details of a versionGET/projects/{projectKey}/savedmodels/{savedModelId}/versions/{versionId}/details
Gets details of a single version. The exact structure of the details may vary. The Python API client can serve as reference for importing settings.
🔒 Required privileges : READ_CONF on the project
Example URI
- projectKey
string
(required)The key of the project
- savedModelId
string
(required)Identifier of the saved model
- versionId
string
(required)Version identifier
200
Headers
Content-Type: application/json
Body
{
"trainInfo" : { ... },
"userMeta" : { ... },
"perf" : { ... }
...
}
Set a version as activePOST/projects/{projectKey}/savedmodels/{savedModelId}/versions/{versionId}/actions/setActive
Sets a version as the active scoring version.
🔒 Required privileges : READ_CONF on the project
Example URI
- projectKey
string
(required)The key of the project
- savedModelId
string
(required)Identifier of the saved model
- versionId
string
(required)Version identifier
204
Set a version user metaPUT/projects/{projectKey}/savedmodels/{savedModelId}/versions/{versionId}/user-meta
Updates the user metadata of a model version. You must only PUT the “userMeta” field of a previously-retrieved model-details object.
The exact structure of the user meta may vary. The Python API client can serve as reference for importing settings.
🔒 Required privileges : WRITE_CONF on the project
Example URI
- projectKey
string
(required)The key of the project
- savedModelId
string
(required)Identifier of the saved model
- versionId
string
(required)Version identifier
Headers
Content-Type: application/json
Body
{
"name": "Name",
"description" : "Description",
"clusterLabels" : [ ... ],
"tags" : ["tag1", "tag2"]
}
204
Get scoring jar of a versionGET/projects/{projectKey}/savedmodels/{savedModelId}/versions/{versionId}/scoring-jar{?fullClassName}{?includeLibs}
Get the scoring jar of a single version, provided that you have the license to do so and that the model is compatible with optimized scoring.
🔒 Required privileges : READ_CONF on the project
Example URI
- projectKey
string
(required)The key of the project
- savedModelId
string
(required)Identifier of the saved model
- versionId
string
(required)Version identifier
- fullClassName
string
(optional) Example: model.Modelthe fully-qualified Java class name for the model
- includeLibs
boolean
(optional) Example: falsewether to include scoring libraries in the jar
200
Headers
Content-Type: application/java-archive
Get scoring PMML of a versionGET/projects/{projectKey}/savedmodels/{savedModelId}/versions/{versionId}/scoring-pmml
Get the scoring PMML of a single version, provided that you have the license to do so and that the model is compatible with PMML scoring.
🔒 Required privileges : READ_CONF on the project
Example URI
- projectKey
string
(required)The key of the project
- savedModelId
string
(required)Identifier of the saved model
- versionId
string
(required)Version identifier
200
Headers
Content-Type: application/xml
Compute subpopulation analyses of a versionPOST/projects/{projectKey}/savedmodels/{savedModelId}/versions/{versionId}/subpopulation-analyses
Launch computation of subpopulation analyses for a version. Returns a reference to a future.
🔒 Required privileges : WRITE_CONF on the project
Example URI
- projectKey
string
(required)The key of the project
- savedModelId
string
(required)Identifier of the saved model
- versionId
string
(required)Version identifier
Headers
Content-Type: application/json
Body
{
"features": ["my_col1", "my_col2"],
"computationParams": { // optional
"sample_size": 10000, // optional, default value is 10000
"random_state": 1337, // optional, default value is 1337
"n_jobs": 1, // optional, default value is 1
"debug_mode": false, // optional, default value is false
}
}
200
Headers
Content-Type: application/json
Body
{
"hasResult": false,
"aborted": false,
"alive": true,
"startTime": 1561456214289,
"runningTime": 0,
"unknown": false,
"jobId": "26S2LeJw"
}
Get subpopulation analyses of a versionGET/projects/{projectKey}/savedmodels/{savedModelId}/versions/{versionId}/subpopulation-analyses
Get all subpopulation analyses computed for a version.
🔒 Required privileges : READ_CONF on the project
Example URI
- projectKey
string
(required)The key of the project
- savedModelId
string
(required)Identifier of the saved model
- versionId
string
(required)Version identifier
200
Headers
Content-Type: application/json
Body
{
'allDataset': {
'nbRecords': 10000,
'weightedNbRecords': 10000.0,
'randomState': 1337,
'onSample': true,
'perf': { ... perf ... }
},
'subpopulationAnalyses': [
{
'computed_as_type': 'CATEGORY',
'feature': 'my_col1',
'isDate': false,
'sameNumRowsAsSplit': true,
'nbRecords': 10000,
'weightedNbRecords': 10000.0,
'onSample': true,
'randomState': 1337,
'modalities': [
{
'value': 'modality 1',
'count': 2489,
'weightedCount': 2489.0
'excluded': false,
'missing_values': false,
'perf': { ... perf ... },
...
},
{
'value': 'modality 2',
'count': 2329,
'weightedCount': 2329.0
'excluded': true,
'reason': 'ONECLASS'
'missing_values': false,
...
},
{
'value': 'modality 3',
'count': 1428,
'weightedCount': 1428.0
'excluded': false,
'missing_values': false,
'perf': { ... perf ... },
...
},
...
],
},
]
}
Compute partial dependencies of a versionPOST/projects/{projectKey}/savedmodels/{savedModelId}/versions/{versionId}/partial-dependencies
Launch computation of partial dependencies for a version. Returns a reference to a future.
🔒 Required privileges : WRITE_CONF on the project
Example URI
- projectKey
string
(required)The key of the project
- savedModelId
string
(required)Identifier of the saved model
- versionId
string
(required)Version identifier
Headers
Content-Type: application/json
Body
{
"features": ["my_col1", "my_col2"],
"computationParams": { // optional
"sample_size": 10000, // optional, default value is 10000
"random_state": 1337, // optional, default value is 1337
"n_jobs": 1, // optional, default value is 1
"debug_mode": false, // optional, default value is false
}
}
200
Headers
Content-Type: application/json
Body
{
"hasResult": false,
"aborted": false,
"alive": true,
"startTime": 1561456214289,
"runningTime": 0,
"unknown": false,
"jobId": "26S2LeJw"
}
Get partial dependencies of a versionGET/projects/{projectKey}/savedmodels/{savedModelId}/versions/{versionId}/partial-dependencies
Get all partial dependencies computed for a version.
🔒 Required privileges : READ_CONF on the project
Example URI
- projectKey
string
(required)The key of the project
- savedModelId
string
(required)Identifier of the saved model
- versionId
string
(required)Version identifier
200
Headers
Content-Type: application/json
Body
{
"partialDependencies": [
{
'feature': 'EDU',
'nbRecords': 500,
'onSample': true,
'randomState': 1337,
'categories': ...,
'data': ...,
'distribution': ...,
...
},
...
]
}
Managed Folders ¶
Managed folders ¶
List Managed foldersGET/projects/{projectKey}/managedfolders/
Lists the managed folders of a project.
🔒 Required privileges : READ_CONF
Example URI
- projectKey
string
(required)the identifier of a project
200
See GET managed folder for more information
Headers
Content-Type: application/json
Body
[
{
"projectKey": "Hello, world!",
"id": "Hello, world!",
"name": "Hello, world!",
"path": "Hello, world!",
"tags": [
"Hello, world!"
]
}
]
Schema
{
"$schema": "http://json-schema.org/draft-04/schema#",
"type": "array"
}
Create managed folderPOST/projects/{projectKey}/managedfolders
Create a new managed folder.
Important: it is recommended that you use the GET ManagedFolder call to retrieve an existing managed folder and modify it to suit your needs and create a new managed folder.
🔒 Required privileges : WRITE_CONF
Example URI
- projectKey
string
(required)the identifier of a project
Headers
Content-Type: application/json
Body
{
"projectKey": "Hello, world!",
"id": "Hello, world!",
"name": "Hello, world!",
"path": "Hello, world!",
"tags": [
"Hello, world!"
]
}
Schema
{
"$schema": "http://json-schema.org/draft-04/schema#",
"type": "object",
"properties": {
"projectKey": {
"type": "string",
"description": "Project key of this managed folder"
},
"id": {
"type": "string",
"description": "Unique identifier of this managed folder in its project"
},
"name": {
"type": "string",
"description": "Name of this managed folder in its project"
},
"path": {
"type": "string",
"description": "Path to the actual filesystem folder of this managed folder"
},
"tags": {
"type": "array",
"description": "Tags of this managed folder"
}
}
}
204
Managed folder ¶
To create a managed folder see POST managedfolders
Get managed folder settingsGET/projects/{projectKey}/managedfolders/{folderId}
Retrieves a Managed Folder object
🔒 Required privileges : READ_CONF
Example URI
- projectKey
string
(required) Example: MYPROJECTthe key of the project of the managed folder
- folderId
string
(required) Example: b21ed09athe unique identifier of the managed folder
200
Headers
Content-Type: application/json
Body
{
"projectKey": "Hello, world!",
"id": "Hello, world!",
"name": "Hello, world!",
"path": "Hello, world!",
"tags": [
"Hello, world!"
]
}
Schema
{
"$schema": "http://json-schema.org/draft-04/schema#",
"type": "object",
"properties": {
"projectKey": {
"type": "string",
"description": "Project key of this managed folder"
},
"id": {
"type": "string",
"description": "Unique identifier of this managed folder in its project"
},
"name": {
"type": "string",
"description": "Name of this managed folder in its project"
},
"path": {
"type": "string",
"description": "Path to the actual filesystem folder of this managed folder"
},
"tags": {
"type": "array",
"description": "Tags of this managed folder"
}
}
}
Update managed folder settingsPUT/projects/{projectKey}/managedfolders/{folderId}
Updates the settings of a Managed Folder.
The ManagedFolder
object given as parameter in of a PUT call MUST have been previously obtained from a
GET managedfolder call at the same URL.
The object obtained with the GET method may contain undocumented attributes. You should not modify them as it could create an invalid state and those attributes may be removed in future releases without notice.
Note : the path to the managed folder cannot be changed
🔒 Required privileges : WRITE_CONF
Example URI
- projectKey
string
(required) Example: MYPROJECTthe key of the project of the managed folder
- folderId
string
(required) Example: b21ed09athe unique identifier of the managed folder
Headers
Content-Type: application/json
Body
{
"projectKey": "Hello, world!",
"id": "Hello, world!",
"name": "Hello, world!",
"path": "Hello, world!",
"tags": [
"Hello, world!"
]
}
Schema
{
"$schema": "http://json-schema.org/draft-04/schema#",
"type": "object",
"properties": {
"projectKey": {
"type": "string",
"description": "Project key of this managed folder"
},
"id": {
"type": "string",
"description": "Unique identifier of this managed folder in its project"
},
"name": {
"type": "string",
"description": "Name of this managed folder in its project"
},
"path": {
"type": "string",
"description": "Path to the actual filesystem folder of this managed folder"
},
"tags": {
"type": "array",
"description": "Tags of this managed folder"
}
}
}
204
Delete managed folderDELETE/projects/{projectKey}/managedfolders/{folderId}
Deletes a managed folder.
WARNING : Deleting a managed folder will trigger the deletion of all associated recipes.
🔒 Required privileges : WRITE_CONF
Example URI
- projectKey
string
(required) Example: MYPROJECTthe key of the project of the managed folder
- folderId
string
(required) Example: b21ed09athe unique identifier of the managed folder
204
Managed folder contents ¶
List files in managed folderGET/projects/{projectKey}/managedfolders/{folderId}/contents/
Lists the contents of a managed folder
🔒 Required privileges : READ_DATA
Example URI
- projectKey
string
(required) Example: MYPROJECTthe key of the project of the managed folder
- folderId
string
(required) Example: b21ed09athe unique identifier of the managed folder
200
Headers
Content-Type: application/json
Body
{
"items": [
{
"path": "Hello, world!",
"size": 1,
"lastModified": 1
}
]
}
Schema
{
"$schema": "http://json-schema.org/draft-04/schema#",
"type": "object",
"properties": {
"items": {
"type": "array",
"description": "list of the files in the folder"
}
}
}
Download file from managed folderGET/projects/{projectKey}/managedfolders/{folderId}/contents/{path}
Downloads the file with the specified relative path in the folder
🔒 Required privileges : READ_DATA
Example URI
- projectKey
string
(required) Example: MYPROJECTthe key of the project of the managed folder
- folderId
string
(required) Example: b21ed09athe unique identifier of the managed folder
- path
string
(required)the path to the file from the root of the folder
200
Body
The file's contents, as a stream
Delete a file from managed folderDELETE/projects/{projectKey}/managedfolders/{folderId}/contents/{path}
Deletes the file with the specified relative path in the folder
🔒 Required privileges : WRITE_DATA
Example URI
- projectKey
string
(required) Example: MYPROJECTthe key of the project of the managed folder
- folderId
string
(required) Example: b21ed09athe unique identifier of the managed folder
- path
string
(required)the path to the file from the root of the folder
204
Upload file to managed folderPOST/projects/{projectKey}/managedfolders/{folderId}/contents/
Uploads a file to the root of the folder. The file is sent as a multipart file.
🔒 Required privileges : WRITE_DATA
Example URI
- projectKey
string
(required) Example: MYPROJECTthe key of the project of the managed folder
- folderId
string
(required) Example: b21ed09athe unique identifier of the managed folder
204
Recipes ¶
Recipes ¶
List recipesGET/projects/{projectKey}/recipes/
Lists the recipes of a project.
🔒 Required privileges : READ_CONF
Example URI
- projectKey
string
(required)the key of the project
200
Returns an array of [Recipe] object. See GET Recipe for more information on the [Recipe] object
Headers
Content-Type: application/json
Body
[
{
"projectKey": "PKEY1",
"name": "recipe1",
"type": "sync",
"params": {},
"inputs": {
"main": {
"items": [
{
"ref": "dataset1"
},
{
"ref": "dataset2"
}
]
}
},
"outputs": {
"main": {
"items": [
{
"ref": "dataset3"
}
]
}
}
}
]
Schema
{
"$schema": "http://json-schema.org/draft-04/schema#",
"type": "array"
}
Create recipePOST/projects/{projectKey}/recipes
Creates a new recipe.
Important: this call creates a recipe with the basic setup. To further configure it, use the GET Recipe and PUT Recipe calls.
🔒 Required privileges : WRITE_CONF
Example URI
- projectKey
string
(required)the key of the project
Headers
Content-Type: application/json
Body
{
"recipePrototype": {
"projectKey": "PKEY1",
"name": "recipe1",
"type": "join",
"params": {},
"inputs": {
"main": {
"items": [
{
"ref": "inputDataset1"
},
{
"ref": "inputDataset2"
}
]
}
},
"outputs": {
"main": {
"items": [
{
"ref": "outputDataset"
}
]
}
}
},
"creationSettings": {}
}
Schema
{
"$schema": "http://json-schema.org/draft-04/schema#",
"type": "object",
"properties": {
"name": {
"type": "string",
"description": "Desired name of the recipe in its project"
},
"type": {
"type": "string",
"description": "Type of the recipe"
},
"params": {
"type": "object",
"properties": {},
"description": "Parameters of the recipe. The exact parameters depend on the recipe type"
},
"inputs": {
"type": "object",
"properties": {},
"description": "Inputs of the recipe."
},
"outputs": {
"type": "object",
"properties": {},
"description": "Outputs of the recipe."
}
}
}
200
Returns the final unique name of the recipe
Headers
Content-Type: application/json
Body
{
"name" : "recipe1",
}
Recipe ¶
To build a recipe see POST recipes
Get recipe settingsGET/projects/{projectKey}/recipes/{recipeName}
Retrieves a Recipe object.
🔒 Required privileges : READ_CONF
Example URI
- projectKey
string
(required) Example: MYPROJECTthe key of a project
- recipeName
string
(required) Example: myrecipethe name of a recipe
200
Headers
Content-Type: application/json
Body
{
"recipe": {
"projectKey": "PKEY1",
"name": "recipe1",
"type": "sync",
"params": {}
},
"payload": "payload of the recipe"
}
Schema
{
"$schema": "http://json-schema.org/draft-04/schema#",
"type": "object",
"properties": {
"recipe": {
"type": "object",
"properties": {
"projectKey": {
"type": "string",
"description": "Project key of this recipe"
},
"name": {
"type": "string",
"description": "Unique name of this recipe in its project"
},
"type": {
"type": "string",
"description": "Type of the recipe"
},
"params": {
"type": "object",
"properties": {},
"description": "Parameters of the recipe. The available parameters depend on the recipe type"
},
"inputs": {
"type": "object",
"properties": {},
"description": "Inputs of the recipe."
},
"outputs": {
"type": "object",
"properties": {},
"description": "Outputs of the recipe."
}
},
"description": "Recipe definition"
},
"payload": {
"type": "string",
"description": "Payload of the recipe. The content depends on the recipe type"
}
}
}
Update recipe settingsPUT/projects/{projectKey}/recipes/{recipeName}
Updates the settings of a Recipe.
The RecipeAndPayload
object given as parameter in of a PUT call MUST have been previously obtained from a
GET recipe call at the same URL.
The object obtained with the GET method may contain undocumented attributes. You should not modify them as it could create an invalid state and thoses attributes may be removed in future releases without notice.
🔒 Required privileges : WRITE_CONF
Example URI
- projectKey
string
(required) Example: MYPROJECTthe key of a project
- recipeName
string
(required) Example: myrecipethe name of a recipe
Headers
Content-Type: application/json
Body
{
"recipe": {
"projectKey": "PKEY1",
"name": "recipe1",
"type": "sync",
"params": {}
},
"payload": "payload of the recipe"
}
Schema
{
"$schema": "http://json-schema.org/draft-04/schema#",
"type": "object",
"properties": {
"projectKey": {
"type": "string",
"description": "Project key of this recipe"
},
"name": {
"type": "string",
"description": "Unique name of this recipe in its project"
},
"type": {
"type": "string",
"description": "Type of the recipe"
},
"params": {
"type": "object",
"properties": {},
"description": "Parameters of the recipe. The available parameters depend on the recipe type"
},
"inputs": {
"type": "object",
"properties": {},
"description": "Inputs of the recipe."
},
"outputs": {
"type": "object",
"properties": {},
"description": "Outputs of the recipe."
}
}
}
204
Delete recipeDELETE/projects/{projectKey}/recipes/{recipeName}
Deletes a recipe.
🔒 Required privileges : WRITE_CONF
Example URI
- projectKey
string
(required) Example: MYPROJECTthe key of a project
- recipeName
string
(required) Example: myrecipethe name of a recipe
204
Recipe metadata ¶
Get metadataGET/projects/{projectKey}/recipes/{recipeName}/metadata
Retrieves metadata about this recipe.
🔒 Required privileges : READ_METADATA on Project
Example URI
- projectKey
string
(required) Example: MYPROJECTthe key of a project
- recipeName
string
(required) Example: myrecipethe name of a recipe
200
Headers
Content-Type: application/json
Body
{
"label": "recipe_name",
"tags": [
"tag1",
"tag2"
]
}
Schema
{
"$schema": "http://json-schema.org/draft-04/schema#",
"type": "object",
"properties": {
"label": {
"type": "string",
"description": "Display name for this object"
},
"description": {
"type": "string",
"description": "Long description (Markdown) for this object"
},
"tags": {
"type": "array",
"description": "Tags of this object"
},
"custom": {
"type": "object",
"properties": {},
"description": "Custom opaque metadata"
}
}
}
Sets metadataPUT/projects/{projectKey}/recipes/{recipeName}/metadata
Writes metadata about this recipe. You should only set a metadata object that has been obtained through the corresponding GET call.
🔒 Required privileges : WRITE_METADATA on Project
Example URI
- projectKey
string
(required) Example: MYPROJECTthe key of a project
- recipeName
string
(required) Example: myrecipethe name of a recipe
Headers
Content-Type: application/json
Body
{
"label": "recipe_name",
"tags": [
"tag1",
"tag2"
]
}
Schema
{
"$schema": "http://json-schema.org/draft-04/schema#",
"type": "object",
"properties": {
"label": {
"type": "string",
"description": "Display name for this object"
},
"description": {
"type": "string",
"description": "Long description (Markdown) for this object"
},
"tags": {
"type": "array",
"description": "Tags of this object"
},
"custom": {
"type": "object",
"properties": {},
"description": "Custom opaque metadata"
}
}
}
200
Webapps ¶
Webapps ¶
List webappsGET/projects/{projectKey}/webapps/
Lists the webapps in a project.
🔒 Required privileges : READ_CONF
Example URI
- projectKey
string
(required)the key of the project
200
Returns an array of WebappListingItem
object.
Headers
Content-Type: application/json
Body
[
{
"backendRunning": false,
"type": "SHINY",
"projectKey": "VSCODEPLUGIN",
"id": "49K1IT7",
"name": "shiny_webapp",
"tags": [],
"lastModifiedBy": {
"login": "api:ltJQh2d0JRFmMZKl",
"displayName": "api:ltJQh2d0JRFmMZKl (deleted)"
},
"lastModifiedOn": 1558532240221,
"createdBy": {
"login": "api:ltJQh2d0JRFmMZKl",
"displayName": "api:ltJQh2d0JRFmMZKl (deleted)"
},
"createdOn": 1554386952201
}
]
Schema
{
"$schema": "http://json-schema.org/draft-04/schema#",
"type": "array"
}
Webapp ¶
Get webappGET/projects/{projectKey}/webapps/{webappId}
Get a webapp
🔒 Required privileges : READ_CONF
Example URI
- projectKey
string
(required)the key of the project
- webappId
string
(required)the id of the webapp
200
Returns Webapp
object.
Headers
Content-Type: application/json
Body
{
"type": "SHINY",
"hasLegacyBackendURL": false,
"projectKey": "MYPROJECT",
"id": "49K1IT7",
"storageFile": "projects/MYPROJECT/web_apps/49K1IT7.json",
"params": {
"ui": "ui code",
"server": "server side code",
"autoStartBackend": false,
"envSelection": {
"envMode": "INHERIT"
}
},
"config": {},
"name": "my_shiny_webapp",
"versionTag": {
"versionNumber": 15,
"lastModifiedBy": {
"login": "api:ltJQh2d0JRFmMZKl"
},
"lastModifiedOn": 1559049788289
},
"creationTag": {
"versionNumber": 6,
"lastModifiedBy": {
"login": "api:ltJQh2d0JRFmMZKl"
},
"lastModifiedOn": 1554386952201
},
"tags": [],
"checklists": {
"checklists": []
},
"customFields": {}
}
Schema
{
"$schema": "http://json-schema.org/draft-04/schema#",
"type": "object",
"properties": {
"projectKey": {
"type": "string",
"description": "Project key of this recipe"
},
"id": {
"type": "string",
"description": "Unique id of this webapp in the project"
},
"name": {
"type": "string",
"description": "Name of this webapp"
},
"type": {
"type": "string",
"description": "Type of the webapp"
},
"backendRunning": {
"type": "boolean",
"description": "Is the backend running"
},
"outputs": {
"type": "object",
"properties": {},
"description": "Outputs of the recipe."
},
"tags": {
"type": "array",
"description": "Tags of this object"
},
"hasLegacyBackendURL": {
"type": "boolean"
},
"storageFile": {
"type": "string",
"description": "Webapp file path in the DSS instance"
},
"params": {
"type": "object",
"properties": {},
"description": "Depends of the webapp type"
},
"versionTag": {
"type": "object",
"properties": {
"versionNumber": {
"type": "number"
},
"lastModifiedBy": {
"type": "object",
"properties": {
"login": {
"type": "string"
},
"displayName": {
"type": "string"
}
}
},
"lastModifiedOn": {
"type": "number"
}
},
"description": "Current version tag"
},
"creationTag": {
"type": "object",
"properties": {
"versionNumber": {
"type": "number"
},
"lastModifiedBy": {
"type": "object",
"properties": {
"login": {
"type": "string"
},
"displayName": {
"type": "string"
}
}
},
"lastModifiedOn": {
"type": "number"
}
},
"description": "Creation version tag"
}
}
}
Update webappPUT/projects/{projectKey}/webapps/{webappId}
Update a webapp.
The Webapp
object given as parameter of a PUT call MUST have been previously obtained from a
GET webapp call at the same URL.
🔒 Required privileges : WRITE_CONF
Example URI
- projectKey
string
(required)the key of the project
- webappId
string
(required)the id of the webapp
Headers
Content-Type: application/json
Body
{
"type": "SHINY",
"hasLegacyBackendURL": false,
"projectKey": "MYPROJECT",
"id": "49K1IT7",
"storageFile": "projects/MYPROJECT/web_apps/49K1IT7.json",
"params": {
"ui": "ui code",
"server": "server side code",
"autoStartBackend": false,
"envSelection": {
"envMode": "INHERIT"
}
},
"config": {},
"name": "my_shiny_webapp",
"versionTag": {
"versionNumber": 15,
"lastModifiedBy": {
"login": "api:ltJQh2d0JRFmMZKl"
},
"lastModifiedOn": 1559049788289
},
"creationTag": {
"versionNumber": 6,
"lastModifiedBy": {
"login": "api:ltJQh2d0JRFmMZKl"
},
"lastModifiedOn": 1554386952201
},
"tags": [],
"checklists": {
"checklists": []
},
"customFields": {}
}
Schema
{
"$schema": "http://json-schema.org/draft-04/schema#",
"type": "object",
"properties": {
"projectKey": {
"type": "string",
"description": "Project key of this recipe"
},
"id": {
"type": "string",
"description": "Unique id of this webapp in the project"
},
"name": {
"type": "string",
"description": "Name of this webapp"
},
"type": {
"type": "string",
"description": "Type of the webapp"
},
"backendRunning": {
"type": "boolean",
"description": "Is the backend running"
},
"outputs": {
"type": "object",
"properties": {},
"description": "Outputs of the recipe."
},
"tags": {
"type": "array",
"description": "Tags of this object"
},
"hasLegacyBackendURL": {
"type": "boolean"
},
"storageFile": {
"type": "string",
"description": "Webapp file path in the DSS instance"
},
"params": {
"type": "object",
"properties": {},
"description": "Depends of the webapp type"
},
"versionTag": {
"type": "object",
"properties": {
"versionNumber": {
"type": "number"
},
"lastModifiedBy": {
"type": "object",
"properties": {
"login": {
"type": "string"
},
"displayName": {
"type": "string"
}
}
},
"lastModifiedOn": {
"type": "number"
}
},
"description": "Current version tag"
},
"creationTag": {
"type": "object",
"properties": {
"versionNumber": {
"type": "number"
},
"lastModifiedBy": {
"type": "object",
"properties": {
"login": {
"type": "string"
},
"displayName": {
"type": "string"
}
}
},
"lastModifiedOn": {
"type": "number"
}
},
"description": "Creation version tag"
}
}
}
200
Returns the id of the updated web app
Headers
Content-Type: application/json
Body
{
"webAppId": "49K1IT7"
}
Schema
{
"$schema": "http://json-schema.org/draft-04/schema#",
"type": "object",
"properties": {}
}
Restart webapp backendPUT/projects/{projectKey}/webapps/{webappId}/backend/actions/restart
Restart the webapp backend. If the backend was running, stop it and relaunch it. Returns a reference to a future.
🔒 Required privileges : WRITE_CONF
Example URI
- projectKey
string
(required)the key of the project
- webappId
string
(required)id of the web app
200
Returns a future
Headers
Content-Type: application/json
Body
{
"hasResult": false,
"aborted": false,
"alive": true,
"startTime": 1570632529065,
"runningTime": 0,
"unknown": false,
"jobId": "mEEdUTIM"
}
Schema
{
"$schema": "http://json-schema.org/draft-04/schema#",
"type": "object",
"properties": {}
}
Stop webapp backendPUT/projects/{projectKey}/webapps/{webappId}/backend/actions/stop
Stop the webapp backend.
🔒 Required privileges : WRITE_CONF
Example URI
- projectKey
string
(required)the key of the project
- webappId
string
(required)id of the web app
200
Retrieve webapp backend stateGET/projects/{projectKey}/webapps/{webappId}/backend/state
Retrieve the current backend state. If backend is not running, will only returns a JSON object with the projectKey and the webAppId.
🔒 Required privileges : READ_CONF
Example URI
- projectKey
string
(required)the key of the project
- webappId
string
(required)id of the web app
200
Headers
Content-Type: application/json
Body
{
"projectKey": "WEBAPPS",
"webAppId": "VCMN2ra",
"futureId": "DGNHG1Rk",
"futureInfo": {
"hasResult": false,
"aborted": false,
"alive": true,
"startTime": 1570700616662,
"runningTime": 2836,
"unknown": false,
"jobId": "DGNHG1Rk",
"jobDisplayName": "Backend for Web app",
"payload": {
"targets": [
{
"objectType": "WEB_APP",
"projectKey": "WEBAPPS",
"objectId": "VCMN2ra",
"name": "PYTHON_BACKEND"
}
],
"displayName": "Backend for Web app",
"extras": {
"crashCount": 0,
"pid": 44245
}
},
"progress": {
"states": []
},
"owner": "api:RINmQ0CtCiK1PjiS"
},
"currentLogTail": {
"totalLines": 4,
"lines": [
"2019-10-10 11:43:38,736 INFO Starting Webapp backend",
"2019-10-10 11:43:38,736 INFO Starting backend for web app: WEBAPPS.VCMN2ra",
"2019-10-10 11:43:38,744 INFO Started backend on port 57154",
"2019-10-10 11:43:38,935 INFO 127.0.0.1 - - [10/Oct/2019 11:43:38] \"GET /__ping HTTP/1.1\" 200 -"
],
"status": [
1,
1,
1,
1
],
"maxLevel": 1
},
"port": 57154
}
Schema
{
"$schema": "http://json-schema.org/draft-04/schema#",
"type": "object",
"properties": {}
}
Macros ¶
Macros ¶
List macrosGET/projects/{projectKey}/runnables
Retrieves the list of the last jobs, as an array of objects.
🔒 Required privileges : READ_CONF
Example URI
- projectKey
string
(required) Example: MYPROJECTthe key of a project
200
Headers
Content-Type: application/json
Body
array[Macro]
Schema
{
"$schema": "http://json-schema.org/draft-04/schema#",
"type": "array"
}
Macro ¶
Get macro definitionGET/projects/{projectKey}/runnables/{runnableType}
Retrieves the definition as a Macro
object summarising the macro.
🔒 Required privileges : READ_CONF
Example URI
- projectKey
string
(required) Example: MYPROJECTthe key of a project
- runnableType
string
(required) Example: MACRO_IDthe identifier of a macro
200
Headers
Content-Type: application/json
Body
{
"runnableType": "MACRO_ID",
"ownerPluginId": "PLUGIN_ID",
"meta": {
"label": "my awesome macro"
},
"longDescription": "some markdown describing in detail the macro",
"resultType": "HTML",
"extension": "html",
"mimeType": "application/html",
"resultLabel": "THE RESULT",
"params": [
{
"name": "param1",
"type": "STRING"
},
{
"name": "param2",
"type": "INT"
}
],
"adminParams": []
}
RunPOST/projects/{projectKey}/runnables/{runnableType}{?wait}
Starts a run of the macro. The result contains a run identifier to pass to abort, get-result or get-status requests.
🔒 Required privileges : READ_CONF
Example URI
- projectKey
string
(required) Example: MYPROJECTthe key of a project
- runnableType
string
(required) Example: MACRO_IDthe identifier of a macro
- wait
boolean
(required) Example: truewhether the call should block until the run is finished
200
Headers
Content-Type: application/json
Body
{
"runId": "identifier_of_the_run"
}
AbortPOST/projects/{projectKey}/runnables/{runnableType}/abort/{run}
Requests the specified macro run to abort.
🔒 Required privileges : READ_CONF
Example URI
- projectKey
string
(required) Example: MYPROJECTthe key of a project
- runnableType
string
(required) Example: MACRO_IDthe identifier of a macro
- run
string
(required) Example: RUN_IDthe identifier of the macro run
204
Poll stateGET/projects/{projectKey}/runnables/{runnableType}/state/{run}
Get the status of a run of the macro. If the macro is still running, then the result of the call contains true for running, and potentially a progress field with a stack of progress info. If the run is finished but failed, either resultError or storedError will contain details on the failure; otherwise the type field will be filled.
🔒 Required privileges : READ_CONF
Example URI
- projectKey
string
(required) Example: MYPROJECTthe key of a project
- runnableType
string
(required) Example: MACRO_IDthe identifier of a macro
- run
string
(required) Example: RUN_IDthe identifier of the macro run
200
Headers
Content-Type: application/json
Body
{
"exists": true,
"running": false,
"empty": false,
"type": "HTML",
"progress": {},
"resultError": {},
"storedError": {}
}
Retrieve resultGET/projects/{projectKey}/runnables/{runnableType}/result/{run}
Download the result of the run of the macro.
🔒 Required privileges : READ_CONF
Example URI
- projectKey
string
(required) Example: MYPROJECTthe key of a project
- runnableType
string
(required) Example: MACRO_IDthe identifier of a macro
- run
string
(required) Example: RUN_IDthe identifier of the macro run
200
Long tasks ¶
Tasks running in the instance ¶
List tasks in progressGET/futures/{?allUsers}{?withScenarios}
Retrieves the list of tasks running.
Example URI
- allUsers
boolean
(required) Example: falsewhether to list tasks independently of who launched them or just the ones launched by the caller
- withScenarios
boolean
(required) Example: falsewhether to include running scenarios in the list
200
Headers
Content-Type: application/json
Body
[
{
"jobId": "8sdf8ze",
"hasResult": false,
"aborted": false,
"alive": false,
"owner": "taskLauncher",
"runningTime": 3135131,
"progress": [
{
"name": "Doing something...",
"unit": "SIZE",
"target": 21513,
"cur": 153
}
]
}
]
Get status of a running taskGET/futures/{jobId}{?peek}
Get the state of a running task.
Example URI
- jobId
string
(required) Example: 6qsaz81the identifier of the task
- peek
boolean
(required) Example: falsewhether to get the full status, with the result if it’s ready
200
Headers
Content-Type: application/json
Body
{
"jobId": "8sdf8ze",
"hasResult": true,
"result": {
"any": "thing"
},
"aborted": false,
"alive": false,
"owner": "taskLauncher",
"runningTime": 3135131,
"progress": [
{
"name": "Doing something...",
"unit": "SIZE",
"target": 21513,
"cur": 153
}
]
}
Abort a taskGET/futures/{jobId}
Abort a running task
Example URI
- jobId
string
(required) Example: 6qsaz81the identifier of the task
200
Meanings ¶
Meanings ¶
List meaningsGET/meanings/
Lists all user-defined meanings.
🔒 Required privileges : Admin
Example URI
200
See GET meaning for more information
Headers
Content-Type: application/json
Body
[
{
"id": "meaning1",
"label": "Meaning 1",
"type": "VALUES_MAPPING",
"mappings": [
{"from": "value_1", "to": "value_a"},
{"from": "value_2", "to": "value_b"}
],
"normalizationMode": "NORMALIZED",
"description": "This is a sample meaning description.",
"detectable": False
}
]
Schema
{
"$schema": "http://json-schema.org/draft-04/schema#",
"type": "array"
}
Create meaningPOST/meanings
Creates a new meaning.
🔒 Required privileges : Admin
Example URI
Headers
Content-Type: application/json
Body
{
"id": "meaning1",
"label": "Meaning 1",
"type": "VALUES_MAPPING",
"mappings": [
{"from": "value_1", "to": "value_a"},
{"from": "value_2", "to": "value_b"}
],
"normalizationMode": "NORMALIZED",
"description": "This is a sample meaning description.",
"detectable": False
}
Schema
{
"$schema": "http://json-schema.org/draft-04/schema#",
"type": "object",
"properties": {
"id": {
"type": "string",
"description": "ID of the meaning"
},
"label": {
"type": "string",
"description": "Label of the meaning"
},
"type": {
"type": "string",
"description": "Type of the meaning. One of `DECLARATIVE`, `VALUES_LIST`, `VALUES_MAPPING`, `PATTERN`"
},
"description": {
"type": "string",
"description": "Description of the meaning"
},
"values": {
"type": "array",
"description": "For `VALUES_LIST` meanings, the valid values"
},
"mappings": {
"type": "array",
"description": "For `VALUES_MAPPING` meanings, the valid mappings"
},
"pattern": {
"type": "array",
"description": "For `PATTERN` meanings, the pattern"
},
"normalizationMode": {
"type": "string",
"description": "String normalization mode used to match values. One of `EXACT`, `LOWERCASE`, `NORMALIZED` (remove accents) for types `VALUES_LIST` and `VALUES_MAPPING`. One of `EXACT`, `LOWERCASE` for `PATTERN`"
},
"detectable": {
"type": "boolean",
"description": "Whether DSS should consider assigning the meaning to columns set to Auto-detect"
}
}
}
204
Meaning ¶
Get meaning definitionGET/meanings/{meaningId}
Retrieves a meaning object.
🔒 Required privileges : Admin
Example URI
- meaningId
string
(required) Example: dept_codethe ID of a meaning
200
Headers
Content-Type: application/json
Body
{
"id": "meaning1",
"label": "Meaning 1",
"type": "VALUES_MAPPING",
"mappings": [
{"from": "value_1", "to": "value_a"},
{"from": "value_2", "to": "value_b"}
],
"normalizationMode": "NORMALIZED",
"description": "This is a sample meaning description.",
"detectable": False
}
Schema
{
"$schema": "http://json-schema.org/draft-04/schema#",
"type": "object",
"properties": {
"id": {
"type": "string",
"description": "ID of the meaning"
},
"label": {
"type": "string",
"description": "Label of the meaning"
},
"type": {
"type": "string",
"description": "Type of the meaning. One of `DECLARATIVE`, `VALUES_LIST`, `VALUES_MAPPING`, `PATTERN`"
},
"description": {
"type": "string",
"description": "Description of the meaning"
},
"values": {
"type": "array",
"description": "For `VALUES_LIST` meanings, the valid values"
},
"mappings": {
"type": "array",
"description": "For `VALUES_MAPPING` meanings, the valid mappings"
},
"pattern": {
"type": "array",
"description": "For `PATTERN` meanings, the pattern"
},
"normalizationMode": {
"type": "string",
"description": "String normalization mode used to match values. One of `EXACT`, `LOWERCASE`, `NORMALIZED` (remove accents) for types `VALUES_LIST` and `VALUES_MAPPING`. One of `EXACT`, `LOWERCASE` for `PATTERN`"
},
"detectable": {
"type": "boolean",
"description": "Whether DSS should consider assigning the meaning to columns set to Auto-detect"
}
}
}
Update meaning definitionPUT/meanings/{meaningId}
Updates the definition of a Meaning.
🔒 Required privileges : Admin
Example URI
- meaningId
string
(required) Example: dept_codethe ID of a meaning
Headers
Content-Type: application/json
Body
{
"id": "meaning1",
"label": "Meaning 1",
"type": "VALUES_MAPPING",
"mappings": [
{"from": "value_1", "to": "value_a"},
{"from": "value_2", "to": "value_b"}
],
"normalizationMode": "NORMALIZED",
"description": "This is a sample meaning description.",
"detectable": False
}
Schema
{
"$schema": "http://json-schema.org/draft-04/schema#",
"type": "object",
"properties": {
"id": {
"type": "string",
"description": "ID of the meaning"
},
"label": {
"type": "string",
"description": "Label of the meaning"
},
"type": {
"type": "string",
"description": "Type of the meaning. One of `DECLARATIVE`, `VALUES_LIST`, `VALUES_MAPPING`, `PATTERN`"
},
"description": {
"type": "string",
"description": "Description of the meaning"
},
"values": {
"type": "array",
"description": "For `VALUES_LIST` meanings, the valid values"
},
"mappings": {
"type": "array",
"description": "For `VALUES_MAPPING` meanings, the valid mappings"
},
"pattern": {
"type": "array",
"description": "For `PATTERN` meanings, the pattern"
},
"normalizationMode": {
"type": "string",
"description": "String normalization mode used to match values. One of `EXACT`, `LOWERCASE`, `NORMALIZED` (remove accents) for types `VALUES_LIST` and `VALUES_MAPPING`. One of `EXACT`, `LOWERCASE` for `PATTERN`"
},
"detectable": {
"type": "boolean",
"description": "Whether DSS should consider assigning the meaning to columns set to Auto-detect"
}
}
}
204
Plugins ¶
Plugins ¶
List Installed pluginsGET/plugins/
Lists the plugins installed on the instance (including dev plugins)
🔒 Required privileges : ADMIN
Example URI
200
Headers
Content-Type: application/json
Body
[
{
"id": "mini-audit",
"version": "v1.0",
"isDev": false,
"meta": {
"label": "Auditing a dataset",
"description": "This plugin computes simple metrics on a dataset"
}
}
]
Schema
{
"$schema": "http://json-schema.org/draft-04/schema#",
"type": "array"
}
Upload a new pluginPOST/plugins/actions/installFromZip
Uploads a file as the zip of a plugin and installs it. Fails if the plugin is already installed.
🔒 Required privileges : ADMIN
Example URI
Headers
Content-Type: multipart
Body
Multipart file: the plugin zip file
204
Installs a plugin from the storePOST/plugins/actions/installFromStore
Installs a plugin from the store. Fails if the plugin is already installed.
🔒 Required privileges : ADMIN
Example URI
Headers
Content-Type: application/json
Body
{
"pluginId": "id of the plugin in the store"
}
204
Installs a plugin from GitPOST/plugins/actions/installFromGit
Checks out a plugin from a Git repository and installs it. Fails if the plugin is already installed.
The path in the Git repository must contain at least a “plugin.json” file
🔒 Required privileges : ADMIN
Example URI
Headers
Content-Type: application/json
Body
{
"gitRepositoryUrl" : "URL of a Git remote",
"gitCheckout": "branch/tag/SHA1 to commit" /* For example, "master" */,
"gitSubpath": "optional, path within the repository to use as Git"
}
204
Plugin ¶
Download a pluginGET/plugins/{pluginId}/download
Downloads a development plugin as a zip file.
🔒 Required privileges : ADMIN
Example URI
- pluginId
string
(required)the identifier of a plugin
200
Update a plugin from a Zip archivePOST/plugins/{pluginId}/actions/updateFromZip
Uploads a file as the zip of a plugin and re-installs it. Fails if the plugin is not already installed.
🔒 Required privileges : ADMIN
Example URI
- pluginId
string
(required)the identifier of a plugin
Headers
Content-Type: multipart
Body
Multipart file
204
Update a plugin from the storePOST/plugins/{pluginId}/actions/updateFromStore
Updates a plugin from the Dataiku Store
🔒 Required privileges : ADMIN
Example URI
- pluginId
string
(required)the identifier of a plugin
204
Update a plugin from GitPOST/plugins/actions/updateFromGit
Checks out a plugin from a Git repository and updates it. Fails if the plugin is not already installed.
The path in the Git repository must contain at least a “plugin.json” file
🔒 Required privileges : ADMIN
Example URI
Headers
Content-Type: application/json
Body
{
"gitRepositoryUrl" : "URL of a Git remote",
"gitCheckout": "branch/tag/SHA1 to commit" /* For example, "master" */,
"gitSubpath": "optional, path within the repository to use as Git"
}
204
Get plugin settingsGET/plugins/{pluginId}/settings
Gets the settings of a plugin
🔒 Required privileges : ADMIN
Example URI
- pluginId
string
(required)the identifier of a plugin
200
Headers
Content-Type: application/json
Body
{
"config" : {
/* Dictionary of the plugins's settings parameters
}
"codeEnvName": "Name of the code env to use"
}
Set plugin settingsPOST/plugins/{pluginId}/settings
Updates the settings of a plugin. You should only set settings that you previously obtained through the GET call
🔒 Required privileges : ADMIN
Example URI
- pluginId
string
(required)the identifier of a plugin
Headers
Content-Type: application/json
Body
{
"config" : {
/* Dictionary of the plugins's settings parameters
}
"codeEnvName": "Name of the code env to use"
}
204
Create the code env of a pluginPOST/plugins/{pluginId}/code-env/actions/create
Creates the code env of a plugin. Returns a reference to a future
🔒 Required privileges : ADMIN
Example URI
- pluginId
string
(required)the identifier of a plugin
Headers
Content-Type: application/json
Body
{
"conda": false
"pythonInterpreter": "a Python interpreter" /* PYTHON27, PYTHON35, PYTHON36 */
}
200
Headers
Content-Type: application/json
Body
{
"jobId": "job id"
}
Update the code env of a pluginPOST/plugins/{pluginId}/code-env/actions/update
Updates the code env of a plugin. Returns a reference to a future
🔒 Required privileges : ADMIN
Example URI
- pluginId
string
(required)the identifier of a plugin
200
Headers
Content-Type: application/json
Body
{
"jobId": "job id"
}
Move a plugin to dev environmentPOST/plugins/{pluginId}/actions/moveToDev
Moves a plugin to the development environment for edition in the plugin editor.
🔒 Required privileges : ADMIN
Example URI
- pluginId
string
(required)the identifier of a plugin
204
Development plugins ¶
Create a new development pluginsPOST/plugins/actions/createDev
Creates a new development plugin
🔒 Required privileges : Develop plugins
Example URI
Headers
Content-Type: application/json
Body
{
"pluginId": "identifier of the plugin",
"creationMode": "EMPTY or GIT_CLONE or GIT_EXPORT",
"gitRepository": "If Git, a Git repository URL",
"gitCheckout": "If Git, a Git checkoutable (branch, tag, hash)",
"gitSubpath": "If GIT_EXPORT, subpath within the repositor of the plugin"
}
204
Get Git remote infoGET/plugins/{pluginId}/gitRemote
Gets the information about the Git remote for this plugin.
🔒 Required privileges : Develop plugins
Example URI
- pluginId
string
(required)the identifier of a plugin
200
Body
{
"repositoryUrl": "a git URL or null if no remote is declared"
}
Set Git remote infoPOST/plugins/{pluginId}/gitRemote
Sets the information about the Git remote for this plugin.
🔒 Required privileges : Develop plugins
Example URI
- pluginId
string
(required)the identifier of a plugin
Headers
Content-Type: application/json
Body
{
"repositoryUrl": "a git URL"
}
200
Delete Git remote infoDELETE/plugins/{pluginId}/gitRemote
Deletes the information about the Git remote for this plugin.
🔒 Required privileges : Develop plugins
Example URI
- pluginId
string
(required)the identifier of a plugin
200
List Git branchesPOST/plugins/{pluginId}/gitBranches
Gets information about the Git branches for this plugin
🔒 Required privileges : Develop plugins
Example URI
- pluginId
string
(required)the identifier of a plugin
200
Body
[
"branch1",
"branch2"
]
Push to Git remotePOST/plugins/{pluginId}/actions/push
Pushes the content of a plugin to a previously-declared Git remote. The remote must have been added first in DSS.
🔒 Required privileges : Develop plugins
Example URI
- pluginId
string
(required)the identifier of a plugin
200
Pull from Git remotePOST/plugins/{pluginId}/actions/pullRebase
Pulls (and rebases) the content of a plugin from a previously-declared Git remote. The remote must have been added first in DSS.
🔒 Required privileges : Develop plugins
Example URI
- pluginId
string
(required)the identifier of a plugin
200
Fetch from Git remotePOST/plugins/{pluginId}/actions/fetch
Fetches the content of a plugin from a previously-declared Git remote. The remote must have been added first in DSS.
🔒 Required privileges : Develop plugins
Example URI
- pluginId
string
(required)the identifier of a plugin
200
Reset to local HEAD statePOST/plugins/{pluginId}/actions/resetToLocalHeadState
🔒 Required privileges : Develop plugins
Example URI
- pluginId
string
(required)the identifier of a plugin
200
Reset to remote HEAD statePOST/plugins/{pluginId}/actions/resetToRemoteHeadState
The remote must have been added first in DSS.
🔒 Required privileges : Develop plugins
Example URI
- pluginId
string
(required)the identifier of a plugin
200
Plugin contents for dev plugins ¶
For development plugins, it is possible to list, get and set files inside the plugin.
List files in pluginGET/plugins/{pluginId}/contents/
Lists the contents of a plugin
🔒 Required privileges : ADMIN
Example URI
- pluginId
string
(required)the identifier of a plugin
200
Headers
Content-Type: application/json
Body
[
{
"name": "Hello, world!",
"path": "Hello, world!",
"mimeType": "Hello, world!",
"size": 1
}
]
Schema
{
"$schema": "http://json-schema.org/draft-04/schema#",
"type": "array"
}
Download file from pluginGET/plugins/{pluginId}/contents/{path}
Downloads the file with the specified relative path in the plugin.
🔒 Required privileges : ADMIN
Example URI
- pluginId
string
(required)the identifier of a plugin
- path
string
(required)the path to the file from the root of the plugin
200
Body
The file's contents, as a stream
Get file detail from pluginGET/plugins/{pluginId}/details/{path}
Example URI
- pluginId
string
(required)the identifier of a plugin
- path
string
(required)the path to the file from the root of the plugin (can not be a folder)
200
Body
{
"name": "my-file.py",
"path": "folder/my-file.py",
"mimeType": "application/octet-stream",
"size": 10,
"hasData": false,
"readOnly": false,
"lastModified": 1558532121000
}
Upload file to pluginPOST/plugins/{pluginId}/contents/{path}
Uploads a file to the plugin. The file is sent as the body of the request
🔒 Required privileges : ADMIN
Example URI
- pluginId
string
(required)the identifier of a plugin
- path
string
(required)the path to the file from the root of the plugin
204
Delete file from pluginDELETE/plugins/{pluginId}/contents/{path}
Deletes a file from the plugin
🔒 Required privileges : ADMIN
Example URI
- pluginId
string
(required)the identifier of a plugin
- path
string
(required)the path to the file from the root of the plugin
204
Add folder to pluginPOST/plugins/{pluginId}/folders/{path}
Add a folder to the plugin.
🔒 Required privileges : ADMIN
Example URI
- pluginId
string
(required)the identifier of a plugin
- path
string
(required)the path to the folder from the root of the plugin
200
API Services ¶
API Services ¶
List API ServicesGET/projects/{projectKey}/apiservices/
Lists the API services of a project.
🔒 Required privileges : READ_CONF
Example URI
- projectKey
string
(required)the key of a project
200
Headers
Content-Type: application/json
Body
[
{
"id": "my-service",
"publicAccess": "true",
"endpoints": [
{
"id": "predict-revenue",
"type": "STD_PREDICTION"
},
{
"id": "predict-churn",
"type": "CUSTOM_PREDICTION"
}
]
}
]
List packagesGET/projects/{projectKey}/apiservices/{serviceId}/packages/
Lists the generated packages of an API service.
🔒 Required privileges : READ_CONF
Example URI
- projectKey
string
(required)the key of a project
- serviceId
string
(required)the id of a service in this project
200
Headers
Content-Type: application/json
Body
[
{
"id": "v1",
"createdOn": 1445265534000
},
{
"id": "v2",
"createdOn": 1445878484000
}
]
Download package archiveGET/projects/{projectKey}/apiservices/{serviceId}/packages/{packageId}/archive
Download a package archive of an API service.
🔒 Required privileges : READ_CONF, READ_DATA
Example URI
- projectKey
string
(required)the key of a project
- serviceId
string
(required)the id of a service in this project
- packageId
string
(required)the id of a package in this service
200
Headers
Content-Type: application/zip
Content-Disposition: attachment; filename={serviceId}_{packageId}.zip
Generate packagePOST/projects/{projectKey}/apiservices/{serviceId}/packages/{packageId}
Generate a package of an API service.
🔒 Required privileges : WRITE_CONF
Example URI
- projectKey
string
(required)the key of a project
- serviceId
string
(required)the id of a service in this project
- packageId
string
(required)the id of the new package
200
Headers
Content-Type: text/plain
Body
Created package {packageId}
Delete packageDELETE/projects/{projectKey}/apiservices/{serviceId}/packages/{packageId}
Delete a package of an API service.
🔒 Required privileges : WRITE_CONF
Example URI
- projectKey
string
(required)the key of a project
- serviceId
string
(required)the id of a service in this project
- packageId
string
(required)the id of a package in this service
200
Headers
Content-Type: text/plain
Body
Deleted package {packageId}
Bundles, Design-side ¶
Bundles of a project ¶
List exported bundlesGET/projects/{projectKey}/bundles/exported
Retrieves the list of exported bundles for a project
🔒 Required privileges : ADMIN (on project)
Example URI
- projectKey
string
(required) Example: MYPROJECTthe key of a project
200
Headers
Content-Type: application/json
Body
{
"bundles": [
{
"bundleId": "v1",
"contentSummary": {},
"exportManifest": {}
}
]
}
Get details about a bundleGET/projects/{projectKey}/bundles/exported/{bundleId}
🔒 Required privileges : ADMIN (on project)
Example URI
- projectKey
string
(required) Example: MYPROJECTthe key of a project
- bundleId
string
(required) Example: v1the id of the bundle
200
Headers
Content-Type: application/json
Body
{
"bundles": [
{
"bundleId": "v1",
"contentSummary": {},
"exportManifest": {},
"changelog": {}
}
]
}
Download a bundleGET/projects/{projectKey}/bundles/exported/{bundleId}/archive
Downloads a bundle
🔒 Required privileges : ADMIN (on project)
Example URI
- projectKey
string
(required) Example: MYPROJECTthe key of a project
- bundleId
string
(required) Example: v1Identifier of the bundle to activate for this project
200
Headers
Content-Type: application/zip
Create a new bundlePUT/projects/{projectKey}/bundles/exported/
Create a new bundle
🔒 Required privileges : ADMIN (on project)
Example URI
- projectKey
string
(required) Example: MYPROJECTthe key of a project
- bundleId:
v1
(string) - the id of the new bundle
- bundleId:
204
Bundles, Automation-side ¶
Bundles of a project ¶
List imported bundlesGET/projects/{projectKey}/bundles/imported
Retrieves the list of imported bundles for a project
🔒 Required privileges : ADMIN (on project)
Example URI
- projectKey
string
(required) Example: MYPROJECTthe key of a project
200
Headers
Content-Type: application/json
Body
{
"bundles": [
{
"bundleId": "v1",
"contentSummary": {},
"exportManifest": {}
}
]
}
Import bundle from archive filePOST/projects/{projectKey}/bundles/imported/actions/importFromArchive{?archivePath}
Retrieves the list of imported bundles for a project
🔒 Required privileges : ADMIN (on project)
Example URI
- projectKey
string
(required) Example: MYPROJECTthe key of a project
- archivePath
string
(required) Example: /home/data/import/bundle-v1.zipthe absolute path on the Automation node host, where the bundle resides
204
Preload a bundlePOST/projects/{projectKey}/bundles/imported/{bundleId}/actions/preload
Preloads a bundle, creating the necessary code environments
🔒 Required privileges : ADMIN (on project)
Example URI
- projectKey
string
(required) Example: MYPROJECTthe key of a project
- bundleId
string
(required) Example: v1Identifier of the bundle to preload for this project
204
Activate a bundlePOST/projects/{projectKey}/bundles/imported/{bundleId}/actions/activate
Activates a bundle
🔒 Required privileges : ADMIN (on project)
Example URI
- projectKey
string
(required) Example: MYPROJECTthe key of a project
- bundleId
string
(required) Example: v1Identifier of the bundle to activate for this project
204
New project ¶
Create project from a bundlePOST/projectsFromBundle{?projectFolderId}
Creates a project from a bundle. The bundle Zip content must be sent using multipart, as a “file” part
🔒 Required privileges : ADMIN (global)
Example URI
- projectFolderId
string
(optional) Example: KdLmPU6the ID of the project folder in which the new project will be created (if not provided, will defaults to root project folder)
The projectFolderId can be found from the get project folder API call or in the URL when accessing DSS GUI.
204
Create project from a bundlePOST/projectsFromBundle/fromArchive{?archivePath,projectFolderId}
Creates a project from a bundle. The bundle Zip must already be present as a file on the Automation node host
🔒 Required privileges : ADMIN (global)
Example URI
- archivePath
string
(required)Absolute path to the location of the bundle on the Automation node host
- projectFolderId
string
(optional) Example: KdLmPU6the ID of the project folder in which the new project will be created (if not provided, will defaults to root project folder)
The projectFolderId can be found from the get project folder API call or in the URL when accessing DSS GUI.
204
Wiki ¶
Wiki ¶
Get wikiGET/projects/{projectKey}/wiki/
Get wiki properties (taxonomy, home article)
🔒 Required privileges : READ_CONF
Example URI
- projectKey
string
(required)the key of the project
200
Returns a [Wiki] object.
Headers
Content-Type: application/json
Body
{
"projectKey": "WIKITEST",
"homeArticleId": "Homepage",
"taxonomy": [
{
"id": "Page 1",
"children": [
{
"id": "Page 2",
"children": []
}
]
},
{
"id": "Homepage",
"children": []
}
]
}
Schema
{
"$schema": "http://json-schema.org/draft-04/schema#",
"type": "object",
"properties": {
"projectKey": {
"type": "string",
"description": "Project key of the wiki"
},
"homeArticleId": {
"type": "string",
"description": "The article ID that is used as homepage"
},
"taxonomy": {
"type": "array",
"description": "Taxonomy of the articles"
}
}
}
Update wikiPUT/projects/{projectKey}/wiki/
Update the wiki properties (taxonomy, home article).
🔒 Required privileges : WRITE_CONF
Example URI
- projectKey
string
(required)the key of the project
Headers
Content-Type: application/json
Body
{
"projectKey": "WIKITEST",
"homeArticleId": "Page 1",
"taxonomy": [
{
"id": "Page 1",
"children": [
{
"id": "Page 2",
"children": []
}
]
},
{
"id": "Homepage",
"children": []
}
]
}
Schema
{
"$schema": "http://json-schema.org/draft-04/schema#",
"type": "object",
"properties": {
"projectKey": {
"type": "string",
"description": "Project key of the wiki"
},
"homeArticleId": {
"type": "string",
"description": "The article ID that is used as homepage"
},
"taxonomy": {
"type": "array",
"description": "Taxonomy of the articles"
}
}
}
200
Returns the updated [Wiki] object.
Headers
Content-Type: application/json
Body
{
"projectKey": "WIKITEST",
"homeArticleId": "Page 1",
"taxonomy": [
{
"id": "Page 1",
"children": [
{
"id": "Page 2",
"children": []
}
]
},
{
"id": "Homepage",
"children": []
}
]
}
Schema
{
"$schema": "http://json-schema.org/draft-04/schema#",
"type": "object",
"properties": {
"projectKey": {
"type": "string",
"description": "Project key of the wiki"
},
"homeArticleId": {
"type": "string",
"description": "The article ID that is used as homepage"
},
"taxonomy": {
"type": "array",
"description": "Taxonomy of the articles"
}
}
}
Create articlePOST/projects/{projectKey}/wiki/
Create an article (metadata).
🔒 Required privileges : WRITE_CONF
Example URI
- projectKey
string
(required)the key of the project
Headers
Content-Type: application/json
Body
{
"projectKey": "WIKITEST",
"id": "New page",
"parent": "Page 1"
}
Schema
{
"$schema": "http://json-schema.org/draft-04/schema#",
"type": "object",
"properties": {}
}
200
Returns the corresponding [ArticleWithPayload] object.
Headers
Content-Type: application/json
Body
{
"article": {
"projectKey": "WIKITEST",
"id": "New page",
"layout": "WIKI_ARTICLE",
"attachments": [],
"tags": []
},
"payload": ""
}
Article ¶
Get articleGET/projects/{projectKey}/wiki/{articleId}
Get an article (metadata, payload)
🔒 Required privileges : READ_CONF
Example URI
- projectKey
string
(required)the key of the project
- articleId
string
(required)the article ID
200
Returns a [ArticleWithPayload] object.
Headers
Content-Type: application/json
Body
{
"article": {
"projectKey": "WIKITEST",
"id": "Page 1",
"layout": "WIKI_ARTICLE",
"attachments": [
{
"attachmentType": "DSS_OBJECT",
"taggableType": "DATASET",
"projectKey": "WIKITEST",
"id": "dataset1"
}
],
"tags": [
"tag1",
"tag2"
]
},
"payload": "# Page 1 article\n\nContent"
}
Schema
{
"$schema": "http://json-schema.org/draft-04/schema#",
"type": "object",
"properties": {
"article": {
"type": "object",
"properties": {
"projectKey": {
"type": "string",
"description": "Project key of this article"
},
"id": {
"type": "string",
"description": "Article id"
},
"layout": {
"type": "string",
"description": "Article layout (WIKI_ARTICLE or FOLDER)"
},
"attachments": {
"type": "array",
"description": "Attachments of the article"
},
"tags": {
"type": "array",
"description": "Tags of the article"
}
},
"description": "Article metadata"
},
"payload": {
"type": "string",
"description": "Content of article"
}
}
}
Update articlePUT/projects/{projectKey}/wiki/{articleId}
Update article (metadata, payload)
🔒 Required privileges : WRITE_CONF
Example URI
- projectKey
string
(required)the key of the project
- articleId
string
(required)the article ID
Note: payload uses markdown syntax.
Headers
Content-Type: application/json
Body
{
"article": {
"projectKey": "WIKITEST",
"id": "Page 1",
"layout": "FOLDER",
"attachments": [
{
"attachmentType": "DSS_OBJECT",
"taggableType": "DATASET",
"projectKey": "WIKITEST",
"id": "dataset1"
}
],
"tags": [
"tag1",
"tag2 (edited)"
]
},
"payload": "# Page 1 article\n\nContent (edited)"
}
Schema
{
"$schema": "http://json-schema.org/draft-04/schema#",
"type": "object",
"properties": {
"article": {
"type": "object",
"properties": {
"projectKey": {
"type": "string",
"description": "Project key of this article"
},
"id": {
"type": "string",
"description": "Article id"
},
"layout": {
"type": "string",
"description": "Article layout (WIKI_ARTICLE or FOLDER)"
},
"attachments": {
"type": "array",
"description": "Attachments of the article"
},
"tags": {
"type": "array",
"description": "Tags of the article"
}
},
"description": "Article metadata"
},
"payload": {
"type": "string",
"description": "Content of article"
}
}
}
200
Returns the corresponding [ArticleAndPayload] object.
Headers
Content-Type: application/json
Body
{
"article": {
"projectKey": "WIKITEST",
"id": "Page 1",
"layout": "FOLDER",
"attachments": [
{
"attachmentType": "DSS_OBJECT",
"taggableType": "DATASET",
"projectKey": "WIKITEST",
"id": "dataset1"
}
],
"tags": [
"tag1",
"tag2 (edited)"
]
},
"payload": "# Page 1 article\n\nContent (edited)"
}
Discussions ¶
Discussions ¶
Get discussionsGET/projects/{projectKey}/discussions/{objectType}/{objectId}/
Get discussions on an object
🔒 Required privileges : READ_DASHBOARD
Example URI
- projectKey
string
(required)the key of the project
- objectType
string
(required)the DSS object type
- objectId
string
(required)the DSS object ID
200
Returns an array of [Discussion] objects.
Headers
Content-Type: application/json
Body
[
{
"projectKey": "DISCUTEST",
"id": "L8gkpoI6",
"objectType": "PROJECT",
"objectId": "DISCUTEST",
"objectDisplayName": "Discussion project",
"topic": "Project infos",
"lastReplyTime": 1517245249936,
"users": {
"user1": {
"login": "user1",
"lastReplyTime": 1517245249936,
"lastReadTime": 1517245249936
}
},
"closedOn": 0,
"closedBy": ""
},
{
"projectKey": "DISCUTEST",
"id": "AZgd6ds0",
"objectType": "PROJECT",
"objectId": "DISCUTEST",
"objectDisplayName": "Discussion project",
"topic": "Project deletion",
"lastReplyTime": 1517218351503,
"users": {
"user1": {
"login": "user1",
"lastReplyTime": 1517218351503,
"lastReadTime": 1517218351503
}
},
"closedOn": 1517218351503,
"closedBy": "user1"
}
]
Schema
{
"$schema": "http://json-schema.org/draft-04/schema#",
"type": "array"
}
Create discussionPOST/projects/{projectKey}/discussions/{objectType}/{objectId}/
Create a discussion on an object
🔒 Required privileges : READ_DASHBOARD
Example URI
- projectKey
string
(required)the key of the project
- objectType
string
(required)the DSS object type
- objectId
string
(required)the DSS object ID
Note: the reply uses markdown syntax.
Headers
Content-Type: application/json
Body
{
"topic": "An interesting discussion",
"reply": "Discussion content here"
}
Schema
{
"$schema": "http://json-schema.org/draft-04/schema#",
"type": "object",
"properties": {}
}
200
Returns the newly created [Discussion].
Headers
Content-Type: application/json
Body
{
"projectKey": "DISCUTEST",
"id": "Ed6Fgi89",
"objectType": "PROJECT",
"objectId": "DISCUTEST",
"objectDisplayName": "Discussion project",
"topic": "An interesting discussion",
"lastReplyTime": 1517322182967,
"users": {
"user1": {
"login": "user1",
"lastReplyTime": 1517322182967,
"lastReadTime": 1517322182967
}
},
"closedOn": 0,
"closedBy": "",
"replies": [
{
"id": "Ja8Stes4",
"text": "Discussion content here",
"author": "user1",
"time": 1517322182967,
"editedOn": 0
}
]
}
Schema
{
"$schema": "http://json-schema.org/draft-04/schema#",
"type": "object",
"properties": {
"projectKey": {
"type": "string",
"description": "Key of the project"
},
"id": {
"type": "string",
"description": "the discussion ID"
},
"objectType": {
"type": "string",
"description": "DSS object type"
},
"objectId": {
"type": "string",
"description": "DSS object ID"
},
"topic": {
"type": "string",
"description": "the discussion topic"
},
"lastReplyTime": {
"type": "number",
"description": "the timestamp of the last reply"
},
"users": {
"type": "object",
"properties": {},
"description": "the map of participants"
},
"closedOn": {
"type": "number",
"description": "the timestamp when the discussion has been closed or 0"
},
"closedBy": {
"type": "string",
"description": "the login of the user that closed the discussion or empty"
},
"replies": {
"type": "array"
}
}
}
Discussion ¶
Get discussionGET/projects/{projectKey}/discussions/{objectType}/{objectId}/{discussionId}
Get discussion
🔒 Required privileges : READ_DASHBOARD
Example URI
- projectKey
string
(required)the key of the project
- objectType
string
(required)the DSS object type
- objectId
string
(required)the DSS object ID
- discussionId
string
(required)the discussion ID
200
Returns the discussion with its replies.
Headers
Content-Type: application/json
Body
{
"projectKey": "DISCUTEST",
"id": "L8gkpoI6",
"objectType": "PROJECT",
"objectId": "DISCUTEST",
"objectDisplayName": "Discussion project",
"topic": "Project infos",
"lastReplyTime": 1517322182967,
"users": {
"user1": {
"login": "user1",
"lastReplyTime": 1517322182967,
"lastReadTime": 1517322182967
}
},
"closedOn": 0,
"closedBy": "",
"replies": [
{
"id": "Ja8Stes4",
"text": "What is the topic?",
"author": "user1",
"time": 1517322182967,
"editedOn": 0
}
]
}
Schema
{
"$schema": "http://json-schema.org/draft-04/schema#",
"type": "object",
"properties": {
"projectKey": {
"type": "string",
"description": "Key of the project"
},
"id": {
"type": "string",
"description": "the discussion ID"
},
"objectType": {
"type": "string",
"description": "DSS object type"
},
"objectId": {
"type": "string",
"description": "DSS object ID"
},
"topic": {
"type": "string",
"description": "the discussion topic"
},
"lastReplyTime": {
"type": "number",
"description": "the timestamp of the last reply"
},
"users": {
"type": "object",
"properties": {},
"description": "the map of participants"
},
"closedOn": {
"type": "number",
"description": "the timestamp when the discussion has been closed or 0"
},
"closedBy": {
"type": "string",
"description": "the login of the user that closed the discussion or empty"
},
"replies": {
"type": "array"
}
}
}
Update discussionPUT/projects/{projectKey}/discussions/{objectType}/{objectId}/{discussionId}
Update discussion (change DSS object inside same project, edit topic)
🔒 Required privileges : READ_DASHBOARD
Example URI
- projectKey
string
(required)the key of the project
- objectType
string
(required)the DSS object type
- objectId
string
(required)the DSS object ID
- discussionId
string
(required)the discussion ID
Headers
Content-Type: application/json
Body
{
"projectKey": "DISCUTEST",
"id": "L8gkpoI6",
"objectType": "PROJECT",
"objectId": "DISCUTEST",
"topic": "Project infos (edited)",
"lastReplyTime": 1517322182967,
"closedOn": 1517322182967,
"closedBy": "user1"
}
Schema
{
"$schema": "http://json-schema.org/draft-04/schema#",
"type": "object",
"properties": {
"projectKey": {
"type": "string",
"description": "Key of the project"
},
"id": {
"type": "string",
"description": "the discussion ID"
},
"objectType": {
"type": "string",
"description": "DSS object type"
},
"objectId": {
"type": "string",
"description": "DSS object ID"
},
"topic": {
"type": "string",
"description": "the discussion topic"
},
"lastReplyTime": {
"type": "number",
"description": "the timestamp of the last reply"
},
"users": {
"type": "object",
"properties": {},
"description": "the map of participants"
},
"closedOn": {
"type": "number",
"description": "the timestamp when the discussion has been closed or 0"
},
"closedBy": {
"type": "string",
"description": "the login of the user that closed the discussion or empty"
},
"replies": {
"type": "array"
}
}
}
200
Returns the discussion with its replies.
Headers
Content-Type: application/json
Body
{
"projectKey": "DISCUTEST",
"id": "L8gkpoI6",
"objectType": "PROJECT",
"objectId": "DISCUTEST",
"objectDisplayName": "Discussion project",
"topic": "Project infos (edited)",
"lastReplyTime": 1517322182967,
"users": {
"user1": {
"login": "user1",
"lastReplyTime": 1517322182967,
"lastReadTime": 1517322182967
}
},
"closedOn": 1517322182967,
"closedBy": "user1",
"replies": [
{
"id": "Ja8Stes4",
"text": "What is the topic?",
"author": "user1",
"time": 1517322182967,
"editedOn": 0
}
]
}
Schema
{
"$schema": "http://json-schema.org/draft-04/schema#",
"type": "object",
"properties": {
"projectKey": {
"type": "string",
"description": "Key of the project"
},
"id": {
"type": "string",
"description": "the discussion ID"
},
"objectType": {
"type": "string",
"description": "DSS object type"
},
"objectId": {
"type": "string",
"description": "DSS object ID"
},
"topic": {
"type": "string",
"description": "the discussion topic"
},
"lastReplyTime": {
"type": "number",
"description": "the timestamp of the last reply"
},
"users": {
"type": "object",
"properties": {},
"description": "the map of participants"
},
"closedOn": {
"type": "number",
"description": "the timestamp when the discussion has been closed or 0"
},
"closedBy": {
"type": "string",
"description": "the login of the user that closed the discussion or empty"
},
"replies": {
"type": "array"
}
}
}
Discussion replies ¶
ReplyPOST/projects/{projectKey}/discussions/{objectType}/{objectId}/{discussionId}/replies/
Reply to a discussion
🔒 Required privileges : READ_DASHBOARD
Example URI
- projectKey
string
(required)the key of the project
- objectType
string
(required)the DSS object type
- objectId
string
(required)the DSS object ID
- discussionId
string
(required)the discussion ID
Note: the reply uses markdown syntax.
Headers
Content-Type: application/json
Body
{
"reply": "A new reply"
}
Schema
{
"$schema": "http://json-schema.org/draft-04/schema#",
"type": "object",
"properties": {}
}
200
Returns the discussion with its replies.
Headers
Content-Type: application/json
Body
{
"projectKey": "DISCUTEST",
"id": "L8gkpoI6",
"objectType": "PROJECT",
"objectId": "DISCUTEST",
"objectDisplayName": "Discussion project",
"topic": "Project infos",
"lastReplyTime": 1517322234567,
"users": {
"user1": {
"login": "user1",
"lastReplyTime": 1517322234567,
"lastReadTime": 1517322182967
}
},
"closedOn": 0,
"closedBy": "",
"replies": [
{
"id": "Ja8Stes4",
"text": "What is the topic?",
"author": "user1",
"time": 1517322182967,
"editedOn": 0
},
{
"id": "v43SD98c",
"text": "A new reply",
"author": "user1",
"time": 1517322234567,
"editedOn": 0
}
]
}
Schema
{
"$schema": "http://json-schema.org/draft-04/schema#",
"type": "object",
"properties": {
"projectKey": {
"type": "string",
"description": "Key of the project"
},
"id": {
"type": "string",
"description": "the discussion ID"
},
"objectType": {
"type": "string",
"description": "DSS object type"
},
"objectId": {
"type": "string",
"description": "DSS object ID"
},
"topic": {
"type": "string",
"description": "the discussion topic"
},
"lastReplyTime": {
"type": "number",
"description": "the timestamp of the last reply"
},
"users": {
"type": "object",
"properties": {},
"description": "the map of participants"
},
"closedOn": {
"type": "number",
"description": "the timestamp when the discussion has been closed or 0"
},
"closedBy": {
"type": "string",
"description": "the login of the user that closed the discussion or empty"
},
"replies": {
"type": "array"
}
}
}
SQL queries ¶
SQL queries ¶
Start a queryPOST/sql/queries
Start the execution of a query.
This call starts the execution of the query and returns the result’s schema, along with an identifier for the query.
🔒 Required privileges : RUN_CODE
Example URI
Headers
Content-Type: application/json
Body
{
"connection": "Hello, world!",
"datasetFullName": "Hello, world!",
"database": "Hello, world!",
"query": "Hello, world!",
"preQueries": [
"Hello, world!"
],
"postQueries": [
"Hello, world!"
],
"type": "Hello, world!"
}
Schema
{
"$schema": "http://json-schema.org/draft-04/schema#",
"type": "object",
"properties": {
"connection": {
"type": "string",
"default": "empty"
},
"datasetFullName": {
"type": "string",
"default": "empty"
},
"database": {
"type": "string",
"default": "empty"
},
"query": {
"type": "string"
},
"preQueries": {
"type": "array",
"default": [
"empty"
],
"description": "A list of queries to run before the actual query"
},
"postQueries": {
"type": "array",
"default": [
"empty"
],
"description": "A list of queries to run after the actual query"
},
"type": {
"type": "string",
"default": "sql"
}
}
}
200
Headers
Content-Type: application/json
Body
{
"queryId" : "e98f95f2-678b-4277-ac01-c5ff52b8cd9a",
"hasResults" : true,
"schema" : [
{
"name" : "col_1",
"type": "string"
},
{
"name" : "col_2",
"type": "int"
},
...
]
}
Schema
{
"$schema": "http://json-schema.org/draft-04/schema#",
"type": "object",
"properties": {}
}
Stream the dataGET/sql/queries/{queryId}/stream{?format}{?formatParams}
Streams the results of a query.
🔒 Required privileges : RUN_CODE
Example URI
- queryId
string
(required)Identifier returned by the start-streaming call
- format
string
(optional) Default: json- formatParams
object
(optional)Output format parameters (depends on the format)
200
The Content-Type
and the content of the request may change according to the requested format.
The default (json) output will produce an array of arrays representing the data:
Body
[
[ "a", "1"],
[ "b", "2"],
...
]
Verify a queryGET/sql/queries/{queryId}/finish-streaming
Start the execution of a query
🔒 Required privileges : RUN_CODE
Example URI
- queryId
string
(required)Identifier returned by the start-streaming call
200
Verifies that the query identified by queryId
finished successfully on the server side. If not, returns the exception and a 500 status code.
Headers
Content-Type: application/text
Body
exception
Connections ¶
Connections ¶
List connectionsGET/admin/connections
List all the connections available on the DSS instance.
This call retrieves a dictionary of Connection
objects as defined in GET connection.
🔒 Required privileges : Admin
Example URI
200
Headers
Content-Type: application/json
Body
{
"my-connection": {
"name" : "my-connection",
"type" : "Vertica",
"allowWrite" : true,
"allowManagedDatasets" : true,
"usableBy" : "ALL",
"allowedGroups" : [],
"params" : {
"db" : "dbname",
"properties" : {},
"user" : "dbadmin",
"host" : "127.0.0.1",
"password" : "thedbpassword"
},
}
}
Create connectionPOST/admin/connections
Creates a connection on DSS.
The parameters of a connection are specific to each type of connection. It is recommended that you have a look at the parameters of a similar connection to create your own.
🔒 Required privileges : Admin
Example URI
Headers
Content-Type: application/json
Body
{
"name": "new-connection",
"type": "PostgreSQL",
"params": {
"db": "dbname",
"user": "myuser",
"host": "127.0.0.1",
"password": "thedbpassword"
}
}
200
Connection ¶
🔒 Required privileges : Admin
Get connectionGET/admin/connections/{connectionName}
Gets a connection
WARNING : The returned object may contain other attributes but you should not rely on them since they could be modified or removed in future releases without notice.
Example URI
- connectionName
string
(required)the name of a connection in DSS
200
Headers
Content-Type: application/json
Body
{
"name": "Hello, world!",
"type": "Hello, world!",
"allowWrite": true,
"allowManagedDatasets": true,
"usableBy": "Hello, world!",
"allowedGroups": [
"Hello, world!"
]
}
Schema
{
"$schema": "http://json-schema.org/draft-04/schema#",
"type": "object",
"properties": {
"name": {
"type": "string"
},
"type": {
"type": "string"
},
"allowWrite": {
"type": "boolean"
},
"allowManagedDatasets": {
"type": "boolean",
"description": "Set to true to allow the connection to provide [Managed datasets](http://doc.dataiku.com/dss/latest/concepts/#managed-and-external-datasets)"
},
"usableBy": {
"type": "string",
"description": "\"ALL\" or \"ALLOWED\", who may use this connection"
},
"allowedGroups": {
"type": "array",
"description": "Ignored if usableBy is ALL"
}
}
}
Update connectionPUT/admin/connections/{connectionName}
The Connection
object given as parameter in of a PUT call MUST have been previously obtained from a
GET connection call at the same URL.
**WARNING : ** the type and names attributes may not be modified. The object obtained with the GET method may contain undocumented attributes. You should not modify them as it could create an invalid state and thoses attributes may be removed in future releases without notice.
🔒 Required privileges : Admin
Example URI
- connectionName
string
(required)the name of a connection in DSS
Headers
Content-Type: application/json
Body
{
"type": "MySQL",
"name": "LocalMySQL",
"allowWrite": true,
"allowManagedDatasets": true,
"usableBy": "ALL",
"allowedGroups": [],
"params": {
"db": "dbname",
"user": "myuser",
"host": "127.0.0.1",
"password": "thedbpassword"
}
}
204
Delete connectionDELETE/admin/connections/{connectionName}
Removes the connection from DSS.
WARNING : No check is performed to ensure that the connection is not in use for a dataset.
🔒 Required privileges : Admin
Example URI
- connectionName
string
(required)the name of a connection in DSS
204
Security ¶
Users ¶
List usersGET/admin/users/{?connected}
Retrieves the list of DSS users as a list of User
objects as defined in GET user.
**WARNING : ** the connected status of the users is detected using WebSockets. If the WebSockets are disabled (for example if your firewall blocks them), some or all of the connected users may not be listed as connected.
🔒 Required privileges : Global admin
Example URI
- connected
boolean
(optional) Default: false
200
Headers
Content-Type: application/json
Body
[
{
"login": "Hello, world!",
"sourceType": "Hello, world!",
"displayName": "Hello, world!",
"groups": [
"Hello, world!"
],
"codeAllowed": "Hello, world!"
}
]
Schema
{
"$schema": "http://json-schema.org/draft-04/schema#",
"type": "array"
}
Create userPOST/admin/users
Adds a user account on DSS.
Example URI
Headers
Content-Type: application/json
Body
{
"login": "newlogin",
"displayName": "The new user",
"groups": [
"data_scientists"
],
"sourceType": "LOCAL",
"password": "unencrypted password"
}
201
User ¶
Get userGET/admin/users/{login}
Retrieves a User object describing a DSS user
WARNING : The returned object may contain other attributes but you should not rely on them since they could be modified or removed in future releases without notice.
🔒 Required privileges : Admin
Example URI
- login
string
(required)the login of a DSS user
200
Headers
Content-Type: application/json
Body
{
"login": "Hello, world!",
"sourceType": "Hello, world!",
"displayName": "Hello, world!",
"groups": [
"Hello, world!"
],
"codeAllowed": "Hello, world!"
}
Schema
{
"$schema": "http://json-schema.org/draft-04/schema#",
"type": "object",
"properties": {
"login": {
"type": "string"
},
"sourceType": {
"type": "string"
},
"displayName": {
"type": "string"
},
"groups": {
"type": "array"
},
"codeAllowed": {
"type": "string",
"description": "True if the user is allowed to write native code"
}
}
}
Update userPUT/admin/users/{login}
The User
object given as body of the PUT call MUST have been previously obtained from a
GET user call at the same URL.
The object obtained with the GET method may contain undocumented attributes. You should not modify them as it could create an invalid state and thoses attributes may be removed in future releases without notice.
🔒 Required privileges : Admin
Example URI
- login
string
(required)the login of a DSS user
Headers
Content-Type: application/json
Body
{
"login": "mattsco",
"displayName": "Matthieu Modified",
"groups": [
"administrators",
"data_scientists"
],
"codeAllowed": true
}
204
Delete userDELETE/admin/users/{login}
Deletes a DSS user
🔒 Required privileges : Admin
Example URI
- login
string
(required)the login of a DSS user
204
Groups ¶
List groupsGET/admin/groups
Retrieves the list of DSS groups as a list of Group
objects as defined in GET group.
🔒 Required privileges : Admin
Example URI
200
Headers
Content-Type: application/json
Body
[
{
"name": "administrators",
"description": "DSS administrators",
"admin": true,
"sourceType": "LOCAL"
}
]
Create groupPOST/admin/groups
Add a user group to DSS
🔒 Required privileges : Admin
Example URI
Headers
Content-Type: application/json
Body
{
"name": "New Group for business",
"admin": false,
"description": "This group is for business users"
}
201
Group ¶
Get groupGET/admin/groups/{groupname}
Retrieves a Group
object describing a DSS user group, used for access control on connections and projects.
WARNING : The returned object may contain other attributes but you should not rely on them since they could be modified or removed in future releases without notice.
🔒 Required privileges : Admin
Example URI
- groupname
string
(required)the name of a DSS group
200
Headers
Content-Type: application/json
Body
{
"name": "Hello, world!",
"description": "Hello, world!",
"admin": true,
"sourceType": "Hello, world!"
}
Schema
{
"$schema": "http://json-schema.org/draft-04/schema#",
"type": "object",
"properties": {
"name": {
"type": "string"
},
"description": {
"type": "string"
},
"admin": {
"type": "boolean",
"description": "Whether this group gives administrative rights on DSS"
},
"sourceType": {
"type": "string"
}
}
}
Update groupPUT/admin/groups/{groupname}
The Group
object given as parameter in of a PUT call MUST have been previously obtained from a
GET group call at the same URL.
The object with the GET method may contain undocumented attributes. You should not modify them as it could create an invalid state and thoses attributes may be removed in future releases without notice.
🔒 Required privileges : Admin
Example URI
- groupname
string
(required)the name of a DSS group
Headers
Content-Type: application/json
Body
{
"name": "ANALYSTS",
"admin": false,
"description": "This group is suited for business analysts"
}
204
Delete groupDELETE/admin/groups/{groupname}
Deletes a DSS users group
🔒 Required privileges : Admin
Example URI
- groupname
string
(required)the name of a DSS group
204
Code envs ¶
List code envsGET/admin/code-envs
Retrieves the list of DSS code environments as a list
🔒 Required privileges : Admin
Example URI
200
Headers
Content-Type: application/json
Body
[
{
"kernelSpecName": "py-dku-venv-basic_external",
"envLang": "PYTHON",
"envName": "basic_external",
"canUpdateCodeEnv": false,
"owner": "admin",
"isUptodate": false,
"unknownKernelSpecStatus": false,
"deploymentMode": "EXTERNAL_CONDA_NAMED"
}
]
Code env ¶
Create code envPOST/admin/code-envs/{envLang}/{envName}
Add a code environment to DSS
🔒 Required privileges : Admin
Example URI
- envLang
string
(required)the type of code environment (python or r)
- envName
string
(required)the name of the code environment
Headers
Content-Type: application/json
Body
{
"deploymentMode" : "DESIGN_MANAGED",
"pythonInterpreter" : PYTHON27,
"installCorePackages" : true,
"installJupyterSupport" : true
}
200
Headers
Content-Type: application/json
Body
{
"envName": "testapi3",
"messages": {
"anyMessage": false,
"warning": false,
"messages": [],
"success": false,
"error": false
}
}
Get code envGET/admin/code-envs/{envLang}/{envName}
Retrieves a Code env
object describing a DSS code environment.
WARNING : The returned object may contain other attributes but you should not rely on them since they could be modified or removed in future releases without notice.
🔒 Required privileges : Admin
Example URI
- envLang
string
(required)the type of code environment (python or r)
- envName
string
(required)the name of the code environment
200
Headers
Content-Type: application/json
Body
{
"deploymentMode": "DESIGN_MANAGED",
"envName": "basic_managed",
"kernelSpecName": "py-dku-venv-basic_managed",
"owner": "admin",
"permissions": [],
"usableByAll": true,
"specPackageList": "",
"specCondaEnvironment": "",
"actualCondaEnvironment": "",
"mandatoryCondaEnvironment": "",
"actualPackageList": "arrow==0.10.0\nbackports-abc==0.5\nbackports.shutil-get-terminal-size==1.0.0\ncertifi==2017.7.27.1\ndateparser==0.6.0\ndecorator==4.0.11\nenum34==1.1.6\nipykernel==4.6.1\nipython==5.4.1\nipython-genutils==0.1.0\njupyter-client==4.4.0\njupyter-core==4.2.1\nmoment==0.8.2\nnumpy==1.13.1\npandas==0.20.3\npathlib2==2.3.0\npexpect==4.2.1\npickleshare==0.7.4\nprompt-toolkit==1.0.15\nptyprocess==0.5.1\nPygments==2.2.0\npython-dateutil==2.5.3\npytz==2016.10\npyzmq==16.0.2\nregex==2017.7.28\nrequests==2.12.5\nruamel.ordereddict==0.4.13\nruamel.yaml==0.15.33\nscandir==1.5\nsimplegeneric==0.8.1\nsingledispatch==3.4.0.3\nsix==1.10.0\ntabulate==0.7.7\nterminado==0.6\ntimes==0.7\ntornado==4.4.2\ntraitlets==4.3.1\ntzlocal==1.4\nwcwidth==0.1.7\n",
"mandatoryPackageList": "\npandas==0.20.3\nrequests==2.12.5\npython-dateutil==2.5.3\npytz==2016.10\n\ndecorator==4.0.11\npyzmq>=16.0\nipykernel==4.6.1\nipython_genutils==0.1.0\njupyter_client==4.4.0\njupyter_core==4.2.1\npexpect==4.2.1\npickleshare==0.7.4\nptyprocess==0.5.1\nsimplegeneric==0.8.1\ntraitlets==4.3.1\nterminado==0.6\ntornado==4.4.2",
"desc": {
"usableByAll": true,
"owner": "admin",
"permissions": [],
"deploymentMode": "DESIGN_MANAGED",
"installCorePackages": true,
"installJupyterSupport": true,
"conda": false,
"pythonInterpreter": "PYTHON27",
"yarnPythonBin": "some/python/on/yarn",
"basePackagesInstallMethod": "PRE_BUILT"
}
}
Schema
{
"$schema": "http://json-schema.org/draft-04/schema#",
"type": "object",
"properties": {
"deploymentMode": {
"type": "string"
},
"envLang": {
"type": "string"
},
"envName": {
"type": "string"
},
"owner": {
"type": "string"
},
"usableByAll": {
"type": "boolean"
},
"permissions": {
"type": "array"
}
}
}
Update code envPUT/admin/code-envs/{envLang}/{envName}
The Code env
object given as parameter in of a PUT call MUST have been previously obtained from a
[GET code-env] call at the same URL.
The object with the GET method may contain undocumented attributes. You should not modify them as it could create an invalid state and thoses attributes may be removed in future releases without notice.
🔒 Required privileges : Admin
Example URI
- envLang
string
(required)the type of code environment (python or r)
- envName
string
(required)the name of the code environment
Headers
Content-Type: application/json
Body
{
"deploymentMode": "DESIGN_MANAGED",
"envName": "basic_managed",
"kernelSpecName": "py-dku-venv-basic_managed",
"owner": "admin",
"permissions": [],
"usableByAll": true,
"specPackageList": "",
"specCondaEnvironment": "",
"actualCondaEnvironment": "",
"mandatoryCondaEnvironment": "",
"actualPackageList": "arrow==0.10.0\nbackports-abc==0.5\nbackports.shutil-get-terminal-size==1.0.0\ncertifi==2017.7.27.1\ndateparser==0.6.0\ndecorator==4.0.11\nenum34==1.1.6\nipykernel==4.6.1\nipython==5.4.1\nipython-genutils==0.1.0\njupyter-client==4.4.0\njupyter-core==4.2.1\nmoment==0.8.2\nnumpy==1.13.1\npandas==0.20.3\npathlib2==2.3.0\npexpect==4.2.1\npickleshare==0.7.4\nprompt-toolkit==1.0.15\nptyprocess==0.5.1\nPygments==2.2.0\npython-dateutil==2.5.3\npytz==2016.10\npyzmq==16.0.2\nregex==2017.7.28\nrequests==2.12.5\nruamel.ordereddict==0.4.13\nruamel.yaml==0.15.33\nscandir==1.5\nsimplegeneric==0.8.1\nsingledispatch==3.4.0.3\nsix==1.10.0\ntabulate==0.7.7\nterminado==0.6\ntimes==0.7\ntornado==4.4.2\ntraitlets==4.3.1\ntzlocal==1.4\nwcwidth==0.1.7\n",
"mandatoryPackageList": "\npandas==0.20.3\nrequests==2.12.5\npython-dateutil==2.5.3\npytz==2016.10\n\ndecorator==4.0.11\npyzmq>=16.0\nipykernel==4.6.1\nipython_genutils==0.1.0\njupyter_client==4.4.0\njupyter_core==4.2.1\npexpect==4.2.1\npickleshare==0.7.4\nptyprocess==0.5.1\nsimplegeneric==0.8.1\ntraitlets==4.3.1\nterminado==0.6\ntornado==4.4.2",
"desc": {
"usableByAll": true,
"owner": "admin",
"permissions": [],
"deploymentMode": "DESIGN_MANAGED",
"installCorePackages": true,
"installJupyterSupport": true,
"conda": false,
"pythonInterpreter": "PYTHON27",
"yarnPythonBin": "some/python/on/yarn",
"basePackagesInstallMethod": "PRE_BUILT"
}
}
204
Delete code-envDELETE/admin/code-envs/{envLang}/{envName}
Deletes a DSS code environement
🔒 Required privileges : Admin
Example URI
- envLang
string
(required)the type of code environment (python or r)
- envName
string
(required)the name of the code environment
200
Headers
Content-Type: application/json
Body
{
"messages": {
"anyMessage": false,
"error": false,
"messages": [],
"success": false,
"warning": false
}
}
Update code-env packagedPOST/packages
Update the packages in a DSS code environement
🔒 Required privileges : Admin
Example URI
200
Headers
Content-Type: application/json
Body
{
"messages": {
"anyMessage": false,
"error": false,
"messages": [],
"success": false,
"warning": false
}
}
Update jupyter integrationPOST/jupyter{?active}
Update the integration to jupyter of a DSS code environement.
🔒 Required privileges : Admin
Example URI
- active
string
(required)whether to activate or deactivate the in+ Response 204
200
Headers
Content-Type: application/json
Body
{
"messages": {
"anyMessage": false,
"error": false,
"messages": [],
"success": false,
"warning": false
}
}
DSS administration ¶
Global settings ¶
Get general settingsGET/admin/general-settings
This calls retrieves the object representing DSS settings.
🔒 Required privileges : Admin
Example URI
200
Headers
Content-Type: application/json
DSS-API-Version: Version of the API server handling the request
DSS-Version: Version of the DSS backend answering the request
Body
{
"ldapSettings" : { ... },
"hiveSettings" : { ... },
...
}
Save general settingsPUT/admin/general-settings
This calls saves the DSS settings. You must only PUT an object that you acquired previously via the corresponding GET call
🔒 Required privileges : Admin
Example URI
Headers
Content-Type: application/json
Body
{
"ldapSettings" : { ... },
"hiveSettings" : { ... },
...
}
204
Platform logs ¶
List logsGET/admin/logs
DSS uses a number of log files, for example for the web server, the notebooks or the core backend plateform.
This call list all the available logs but NOT the logs generated during the jobs execution.
For these, see the Jobs section.
🔒 Required privileges : Admin
Example URI
200
Headers
Content-Type: application/json
DSS-API-Version: Version of the API server handling the request
DSS-Version: Version of the DSS backend answering the request
Body
{
"logs" : [
{
"name" : "access.log",
"totalSize" : 571166942,
"lastModified" : 1435840900000
},
...
]
}
Log ¶
Get log contentGET/admin/logs/{name}
Retrieves the log file with the specified name.
🔒 Required privileges : Admin
Example URI
- name
string
(required)the name of a log file
200
Headers
Content-Type: text/plain
DSS-API-Version: Version of the API server handling the request
DSS-Version: Version of the DSS backend answering the request
Audit trail ¶
Trigger new audit trail log itemPOST/admin/audit/{customMsgType}
Appends an entry to the audit trail. The JSON object given as the request body
is put as customMsgParams
in the created audit trail log entry.
🔒 Required privileges : Run safe code
Example URI
- customMsgType
string
(required)the
customMsgType
for the audit trail log entry
Headers
Content-Type: application/json
Body
{
"arbitraryKey1" : { ... },
...
}
200
Headers
Content-Type: text/plain
Global variables ¶
List variablesGET/admin/variables
Retrieves the DSS instance global variable as a dictionary.
🔒 Required privileges : Admin
Example URI
200
Headers
Content-Type: application/json
Body
{
"variable_1": "value",
...
}
Save variablesPUT/admin/variables
Save the global variables for the DSS instance.
WARNING : this will overwrite all previous variables, so to update or add only some variables, you should first list the current variables with a GET call.
🔒 Required privileges : Admin
Example URI
Headers
Content-Type: application/json
Body
{
"variable_1": "value",
...
}
204
Licensing ¶
List current license informationsGET/admin/licensing/status
Retrieve various informations about your license (expiration date, limits, feature scope, etc.)
🔒 Required privileges : Admin
Example URI
200
Headers
Content-Type: application/json
Body
{
"base": {
"licenseContent": {
"licensee": {
"email": "john.doe@yourmail.com",
"company": "ACME Inc.",
"name": "John Doe"
},
"dssMode": "ON_PREMISE_DISCONNECTED",
"instanceId": "ab7cdefg",
"licenseKind": "COMMUNITY",
"licenseId": "iJKLMnoP4qrSTUvw",
"properties": {
"automationFeaturesVersion": "2018-1"
},
"communityEdition": "true"
},
"hasLicense": true,
"valid": true,
"expired": false,
"expiresOn": 0,
"ceEntrepriseTrial": false,
"ceEntrepriseTrialUntil": 0,
"community": true,
"wasCEEntrepriseTrial": false,
"ceInstanceId": "sg7jbvoz",
"ceRegistrationEmail": "john.doe@yourmail.com",
"userProfiles": [
"DESIGNER"
]
},
"limits": {
"licensedProfiles": {
"DESIGNER": {
"profile": "DESIGNER",
"demotesFrom": [],
"licensedLimit": 3,
"mayAdmin": true,
"mayPython": true,
"mayScala": true,
"mayR": true,
"mayVisualML": true,
"mayReadProjectContent": true,
"mayWriteProjectContent": true,
"mayWriteDashboards": true
}
},
"profileLimits": {
"DESIGNER": {
"profile": "DESIGNER",
"licensed": {
"profile": "DESIGNER",
"demotesFrom": [],
"licensedLimit": 3,
"mayAdmin": true,
"mayPython": true,
"mayScala": true,
"mayR": true,
"mayVisualML": true,
"mayReadProjectContent": true,
"mayWriteProjectContent": true,
"mayWriteDashboards": true
},
"directCount": 1,
"demotedToOther": 0,
"countWithDemotedTo": 1,
"demotedTo": [],
"demotedFromOther": 0,
"demotedFrom": [],
"limitWithDemoted": 0,
"overQuota": 0
}
},
"fallbackProfile": "DESIGNER"
},
"features": {
"limitedEditionString": "Free Edition",
"allowedDatasetTypes": [
"S3",
"SCP",
"FTP",
"Greenplum",
"PostgreSQL",
"Cassandra",
"Netezza",
"Twitter",
"ElasticSearch",
"MySQL",
"Snowflake",
"JDBC",
"StatsDB",
"Filesystem",
"Oracle",
"UploadedFiles",
"FilesInFolder",
"Azure",
"BigQuery",
"JobsDB",
"HDFS",
"SFTP",
"HTTP",
"Inline",
"Teradata",
"Redshift",
"hiveserver2",
"GCS",
"SAPHANA",
"Vertica",
"MongoDB",
"SQLServer"
],
"allowedConnectionTypes": [
"FTP",
"Greenplum",
"PostgreSQL",
"Cassandra",
"Netezza",
"Twitter",
"ElasticSearch",
"EC2",
"MySQL",
"Snowflake",
"JDBC",
"StatsDB",
"Filesystem",
"Oracle",
"UploadedFiles",
"FilesInFolder",
"Azure",
"BigQuery",
"JobsDB",
"HDFS",
"SSH",
"HTTP",
"Inline",
"Teradata",
"Redshift",
"hiveserver2",
"GCS",
"SAPHANA",
"Vertica",
"MongoDB",
"SQLServer"
],
"ldapAllowed": false,
"ssoAllowed": false,
"userSecurityAllowed": false,
"multiUserSecurityAllowed": false,
"sparkAllowed": false,
"sparkMLLibAllowed": false,
"apiNodeAllowed": false,
"lockedTracking": false,
"forbiddenTracking": false,
"bundlesAllowed": false,
"advancedScenarioStepsAllowed": true,
"temporalTriggerAllowed": false,
"allScenarioTriggersAllowed": false,
"allScenarioReportersAllowed": false,
"advancedMetricsChecksAllowed": false,
"modelsRawSQLExport": false,
"modelsPMMLExport": false,
"modelsJarExport": false
}
Internal Metrics ¶
Internal Metrics ¶
List internal metricsGET/internal-metrics{?name}{?type}
Retrieves the DSS instance internal metrics as a dictionary.
🔒 Required privileges : Admin
Example URI
- name
string
(optional) Example: my.metric.namename of the metric
- type
string
(optional) Example: gaugestype of the metric. Can be gauges, counters, histograms, meters, timers
200
Headers
Content-Type: application/json
Body
{
"counters": {
"metric.dotted.name": {
"variable_1": value,
...
}
},
"gauges": {
...
},
"histograms": {
...
},
"meters": {
...
},
"timers": {
...
},
"version": "3.0.0"
}