API v1 - Tasks
  • Dark
    Light

API v1 - Tasks

  • Dark
    Light

Overview

This is a guide to providing details on the Task API from the family of the Group API . The Task API endpoint allows users to explore and manage the Tasks created whenever an Orchestration or Transformation operation is performed in the Matillion ETL instance.

This includes:

  • Tasks created by user operations - This includes almost all operations that the user performs that generate database queries such as running a job, retrieving a sample or a row count.
  • Tasks created by the Scheduler.
  • Tasks run via the Matillion ETL API (such tasks will display as "API" in the Tasks tab).

As an overall Orchestration or Transformation task is performed (such as executing an Orchestration job) the overall Task is broken down into more granular tasks as the execution continues. Task information is immediately available in the Task panel at the bottom-right of the client interface, giving concise information on recently run tasks and how they have progressed. Whereas, Task History is available within Matillion through Project Menu Task History

Task

The Task API provides the resource details to run the job within the project group in the Matillion ETL instance. By resources here, we refer to run jobs, list running tasks, task history, and cancel the task. Task endpoint is a part of the PATH/project family with some endpoints that are combined with HTTP methods (GET, POST, and DELETE) for unique combinations to get the "resource" information for the Matillion ETL instance.

Important Information

  • This document is part of a series target="_blank">API v1 - Group and the Matillion ETL API - v1.
  • Users responsible for experimenting with Matillion ETL API services require access to the Matillion ETL instance and ought to know how to make REST API calls either employing a REST API GUI client such as Postman or employing a command-line interface like cURL.
  • Matillion ETL API endpoints require authorisation to make any REST API call, so ensure a username and password for the Matillion ETL instance is configured before making any API call.

Task API Endpoints

API Base URL

http(s)://<InstanceAddress>/rest/v1/group/name/<groupName>/project/name/<projectName>/task

API Endpoints and Function

Task endpoint API is available on standard REST-based APIs that uses HTTP or HTTPS request to GET, POST, and DELETE data. The Task endpoint API service is accessed through the Uniform Resource Identifier (URI). All following references in this document will assume the API Base URL has been specified. The available API endpoints are listed below:

Method Path URI Function
GET /running http://<InstanceAddress>/rest/v1/group/name/<groupName>/project/name/<projectName>/task/running Get the detail of the task running for the selected project.
GET /history http://<InstanceAddress>/rest/v1/group/name/<groupName>/project/name/<projectName>/task/history To export the metadata of the task history.
PATH/id/<taskId>
GET /id/<taskId> http://<InstanceAddress>/rest/v1/group/name/<groupName>/project/name/<projectName>/task/id/<taskId> To get the detail of the task using taskid.
POST /id/<taskId>/cancel http://<InstanceAddress>/rest/v1/group/name/<groupName>/project/name/<projectName>/task/id/<taskId>/cancel This will cancel the selected running task within the project using taskId.
PATH /instance http://<InstanceAddress>/rest/v1/group/name/<groupname>/project/name/<projectName>/task/instance/<taskId> To get the detail of task by instance.
PATH/filter
GET /by/none http://<InstanceAddress>/rest/v1/group/name/<groupName>/project/name/<projectName>/task/filter/by/none List all the entries in the task history.
GET by/start/after/date/<date> http://<InstanceAddress>/rest/v1/group/name/<groupName>/project/name/<projectName>/task/filter/by/start/after/date/<date> List all entries in the task history which started on or after the given date.
GET by/start/before/date/<date>/time/<time> http://<InstanceAddress>/rest/v1/group/name/<groupName>/project/name/<projectName>/task/filter/by/start/before/date/<date>/time/<time> List all entries in the task history which started before the given date/time.
GET by/start/after/date/<date>/time/<time> http://<InstanceAddress>/rest/v1/group/name/<groupName>/project/name/<projectName>/task/filter/by/start/after/date/<date>/time/<time> List all entries in the task history which started on or after the given date/time.
GET by/job/name/<jobName> http://<InstanceAddress>/rest/v1/group/name/<groupName>/project/name/<projectName>/task/filter/by/job/name/<jobName> List all entries in the task history with the given job name.
GET by/type/<type> http://<InstanceAddress>/rest/v1/group/name/<groupName>/project/name/<projectName>/task/filter/by/type/<type> List all entries in the task history with the given task type.
GET by/state/<state> http://<InstanceAddress>/rest/v1/group/name/<groupName>/project/name/<projectName>/task/filter/by/state/<state> List all entries in the task history with the given state.
GET by/start/range/date/<startDate>/time/<startTime>/to/date/<endDate>/time/<endTime> http://<InstanceAddress>/rest/v1/group/name/<groupName>/project/name/<projectName>/task/filter/by/start/range/date/<startDate>/time/<startTime>/to/date/<endDate>/time/<endTime> List all entries in the task history which started between the given date/time range.
GET /by/end/after/date/<date> http://<InstanceAddress>/rest/v1/group/name/<groupName>/project/name/<projectName>/task/filter/by/end/after/date/<date> List all entries in the task history by date/time after the given date.
GET /by/end/after/date/<date>/time/<time> http://<InstanceAddress>/rest/v1/group/name/<groupName>/project/name/<projectName>/task/filter/by/end/after/date/<date>/time//<time> List all entries in the task history by end date/time after the given date/time.
GET /by/end/range/date/<startDate>/time/<startTime>/to/date/<endDate>/time/<endTime> http://<InstanceAddress>/rest/v1/group/name/<groupName>/project/name/<projectName>/task/filter/by/end/range/date/<date>/time/<time>/to/date/<date>/time/<time> List all entries in the task history by end date/time started between the given date/time range.

Graphical Representation

To illustrate the Task API v1, endpoints and methods to the further, below is the graphical flow of the /task endpoint showing possible PATH, GET , POST, and DELETE options.

Task endpoint Flow



URL Parameters and Description

Below is the list of endpoint parameters and their brief description:

Parameters Name Description
<InstanceAddress> This is the server IP address or domain name.
<groupName> the name of the group.
<projectName> The name of the project within the group.
<task> To get the task details, created whenever an Orchestration or Transformation operation performed within the Matillion ETL instance.
<running> To get the detail of tasks running, when an Orchestration or Transformation operation performed within the project in the Matillion ETL instance.
<history> Retrieve the history of tasks within selected project of the Matillion ETL instance.
<instance> To get the instance detail where an Orchestration or Transformation operation performed.
<date> To get the detail of the task running for the specified date. The date format should be [yyyy-mm-dd].
<time> To get the detail of the task running for the specified time. The time format should be [HH:mm].
<jobName> To get the task detail of the given Job name (Orchestration or Transformation).


Endpoints and Server Response

This chapter describes the Task API endpoints along with some server response examples for reference. These APIs offer REST-based web service, offering ease of use and a flexible choice of programming language. Task API endpoints can be used to access and analyze the tasks, whenever an Orchestration or Transformation operation is performed within the Matillion ETL instance.

List of endpoints and PATHs for the /task:

Please Note

For the illustrative view of the flow of PATH/task endpoints, you can refer the section Graphical Representation of this guide.

Below is the detailed description of these endpoints with some server response examples for reference.

GET/running

This is a GET method REST API request that will provide the list of task running in the project when Orchestration or Transformation operation preformed within the instance.

  • Base URL
    http://<InstanceAddress>/rest/v1/group/name/<groupName>/project/name/<projectName>/task/running
  • Server Response
    [
    {
    "id": 63059,
    "type": "RUN_ORCHESTRATION",
    "customerID": 2052,
    "groupName": "API GROUP",
    "projectID": 4394,
    "projectName": "API PROJECT",
    "versionID": 4395,
    "versionName": "default",
    "jobID": 4461,
    "jobName": "API JOB TEST",
    "environmentID": 4398,
    "environmentName": "API PROJECT_full",
    "state": "RUNNING",
    "enqueuedTime": 1594729286893,
    "startTime": 1594729286894,
    "endTime": 0,
    "message": null,
    "originatorID": "ws_61498_7",
    "rowCount": 0,
    "tasks": [
    {
    "taskID": 1,
    "parentID": -1,
    "type": "VALIDATE_ORCHESTRATION",
    "jobID": 4461,
    "jobName": "API JOB TEST",
    "jobRevision": 2,
    "jobTimestamp": 1594714513373,
    "componentID": 4462,
    "componentName": "Start 0",
    "state": "SUCCESS",
    "rowCount": -1,
    "startTime": 1594729286896,
    "endTime": 1594729286900,
    "message": ""
    },
    ]

GET/history

This endpoint is to fetch the history of the task performed within the instance for a specific period of time.

Please Note

Task History results are subjected to the limit of 1,000 records for a single task run.

  • Base URL
    http://<InstanceAddress>/rest/v1/group/name/<groupName>/project/name/<projectName>/task/history?since=<since>
  • Where <since> takes the form yyyy-MM-dd.

  • Server Response
    [
    {
    "id": 63018,
    "type": "RUN_ORCHESTRATION",
    "customerID": 793,
    "groupName": "API GROUP",
    "projectID": 795,
    "projectName": "API PROJECT",
    "versionID": 796,
    "versionName": "default",
    "jobID": 827,
    "jobName": "Sleep",
    "environmentID": 799,
    "environmentName": "test",
    "state": "SUCCESS",
    "enqueuedTime": 1594729190954,
    "startTime": 1594729190955,
    "endTime": 1594729201024,
    "message": null,
    "originatorID": "ws_61498_7",
    "rowCount": 0,
    "tasks": [
    {
    "taskID": 1,
    "parentID": -1,
    "type": "VALIDATE_ORCHESTRATION",
    "jobID": 827,
    "jobName": "Sleep",
    "jobRevision": 2,
    "jobTimestamp": 1594714500345,
    "componentID": 828,
    "componentName": "Start 0",
    "state": "SUCCESS",
    "rowCount": -1,
    "startTime": 1594729190956,
    "endTime": 1594729190958,
    "message": ""
    },
    {
    "taskID": 2,...
    }
    ],
    "hasHistoricJobs": true,
    "jobNames": [
    "API JOB TEST"
    ]

PATH/id/<taskId>

To get the task detail of the task running for any specific Orchestration or Transformation jobs via taskId number.

PATH/id/<taskId> is the part of the PATH/task, which is further combined with HTTP methods GET and POST.

List of endpoints associated with the PATH/id/<taskId>

Below is the detailed description of these endpoints with example response from the server.

GET/id/taskId

This is a GET API call request to retrieve the task details using taskId.

  • Base URL
    http://<InstanceAddress>/rest/v1/group/name/<groupName>/project/name/<projectName>/task/id/<taskId>
  • Server Response
    {
    "id": 12345,
    "type": "RUN_ORCHESTRATION",
    "customerID": 793,
    "groupName": "API GROUP",
    "projectID": 795,
    "projectName": "API PROJECT",
    "versionID": 796,
    "versionName": "default",
    "jobID": 827,
    "jobName": "API JOB TEST",
    "environmentID": 799,
    "environmentName": "test",
    "state": "SUCCESS",
    "enqueuedTime": 1594729190954,
    "startTime": 1594729190955,
    "endTime": 1594729201024,
    "message": null,
    "originatorID": "ws_61498_7",
    "rowCount": 0,
    "tasks": [
    {
    "taskID": 1,
    "parentID": -1,
    "type": "VALIDATE_ORCHESTRATION",
    "jobID": 827,
    "jobName": "API JOB TEST",
    "jobRevision": 2,
    "jobTimestamp": 1594714500345,
    "componentID": 828,
    "componentName": "Start 0",
    "state": "SUCCESS",
    "rowCount": -1,
    "startTime": 1594729190956,
    "endTime": 1594729190958,
    "message": ""
    },
    ],
    "hasHistoricJobs": true,
    "jobNames": [
    "API JOB TEST"
    ]
    }

POST/id/taskId/cancel

This is a POST request API call that allow to cancel the task if running using the taskId.

  • Base URL
    http://<InstanceAddress>/rest/v1/group/name/<groupName>/project/name/<projectName>/task/id/<taskId>/cancel
  • Server Response
    {
    "success": true,
    "msg": "Cancel the task[12345].",
    "id": -1
    }

PATH/instance/<taskId>

To get the task detail of the operation performed by the specific Orchestration or Transfrmation job via Id number of the job. This is a GET API call request to retrieve the task details.

  • Base URL
    http://<InstanceAddress>/rest/v1/group/name/<groupName>/project/name/<projectName>/task/instance/<taskID>
  • Server Response
    {
    "id": 12345,
    "type": "RUN_ORCHESTRATION",
    "customerID": 793,
    "groupName": "API GROUP",
    "projectID": 795,
    "projectName": "API PROJECT",
    "versionID": 796,
    "versionName": "default",
    "jobID": 827,
    "jobName": "API JOB TEST",
    "environmentID": 799,
    "environmentName": "test",
    "state": "SUCCESS",
    "enqueuedTime": 1594729190954,
    "startTime": 1594729190955,
    "endTime": 1594729201024,
    "message": null,
    "originatorID": "ws_61498_7",
    "rowCount": 0,
    "tasks": [
    {
    "taskID": 1,
    "parentID": -1,
    "type": "VALIDATE_ORCHESTRATION",
    "jobID": 827,
    "jobName": "API JOB TEST",
    "jobRevision": 2,
    "jobTimestamp": 1594714500345,
    "componentID": 828,
    "componentName": "Start 0",
    "state": "SUCCESS",
    "rowCount": -1,
    "startTime": 1594729190956,
    "endTime": 1594729190958,
    "message": ""
    },
    ],
    "hasHistoricJobs": true,
    "jobNames": [
    "API JOB TEST"
    ]
    }

PATH/filter

To get the list of all task history for any specific Orchestration or Transformation jobs by the specified date/time, date/time range, by given job name or by given task type.

PATH/<filter> is the part of the PATH/task, which is further combined with number of HTTP GET methods.

List of endpoints associated with the PATH/<filter>

Below is the detailed description of these endpoints with example response from the server.

GET/by/none

This will list all the entries in task history.

  • Base URL
    http://<InstanceAddress>/rest/v1/group/name/<groupName>/project/name/<projectName>/task/filter/by/none
  • Server Response
    [
    {
    "id": 62747,
    "type": "RUN_ORCHESTRATION",
    "customerID": 953,
    "groupName": "Docs",
    "projectID": 955,
    "projectName": "Sush-test-Salesforce",
    "versionID": 956,
    "versionName": "default",
    "jobID": 1005,
    "jobName": "Salesforce-test",
    "environmentID": 959,
    "environmentName": "RS",
    "state": "SUCCESS",
    "enqueuedTime": 1601375601704,
    "startTime": 1601375601705,
    "endTime": 1601375601707,
    "message": null,
    "originatorID": "ws_61482_4",
    "rowCount": 0,
    "tasks": [
    { ...}
    ],
    "hasHistoricJobs": true,
    "jobNames": [
    "Salesforce-test"
    }
    ]

GET/by/start/after/date/<date>

List all entries in the task history which started on or after the given date. The dates should be in the format [yyyy-MM-dd] (For example: 2020-09-28).

  • Base URL
    http://<InstanceAddress>/rest/v1/group/name/<groupName>/project/name/<projectName>/task/filter/by/start/after/date/<date>
  • Server Response
    [
    {
    "id": 62747,
    "type": "RUN_ORCHESTRATION",
    "customerID": 953,
    "groupName": "Docs",
    "projectID": 955,
    "projectName": "Sush-test-Salesforce",
    "versionID": 956,
    "versionName": "default",
    "jobID": 1005,
    "jobName": "Salesforce-test",
    "environmentID": 959,
    "environmentName": "RS",
    "state": "SUCCESS",
    "enqueuedTime": 1601375601704,
    "startTime": 1601375601705,
    "endTime": 1601375601707,
    "message": null,
    "originatorID": "ws_61482_4",
    "rowCount": 0,
    "tasks": []
    

GET/by/start/before/date/<date>/time/<time>

List all entries in the task history which started before the given date/time. The dates should be in the format [yyyy-MM-dd] (For Example: 2020-09-28) and times in the format [HH:mm] (For Example: 11:43).

  • Base URL
    http://<InstanceAddress>/rest/v1/group/name/<groupName>/project/name/<projectName>/task/filter/by/start/before/date/<date>/time/<time>
  • Server Response
    [
    {
    "id": 62747,
    "type": "RUN_ORCHESTRATION",
    "customerID": 953,
    "groupName": "Docs",
    "projectID": 955,
    "projectName": "Sush-test-Salesforce",
    "versionID": 956,
    "versionName": "default",
    "jobID": 1005,
    "jobName": "Salesforce-test",
    "environmentID": 959,
    "environmentName": "RS",
    "state": "SUCCESS",
    "enqueuedTime": 1601375601704,
    "startTime": 1601375601705,
    "endTime": 1601375601707,
    "message": null,
    "originatorID": "ws_61482_4",
    "rowCount": 0,
    "tasks": []
    

GET/by/start/after/date/<date>/time/<time>

List all entries in the task history which started after the given date/time.. The dates should be in the format [yyyy-MM-dd] (For Example: 2020-09-28) and times in the format [HH:mm] (For Example: 11:43).

  • Base URL
    http://<InstanceAddress>/rest/v1/group/name/<groupName>/project/name/<projectName>/task/filter/by/start/after/date/<date>/time/<time>
  • Server Response
    [
    {
    "id": 62747,
    "type": "RUN_ORCHESTRATION",
    "customerID": 953,
    "groupName": "Docs",
    "projectID": 955,
    "projectName": "Sush-test-Salesforce",
    "versionID": 956,
    "versionName": "default",
    "jobID": 1005,
    "jobName": "Salesforce-test",
    "environmentID": 959,
    "environmentName": "RS",
    "state": "SUCCESS",
    "enqueuedTime": 1601375601704,
    "startTime": 1601375601705,
    "endTime": 1601375601707,
    "message": null,
    "originatorID": "ws_61482_4",
    "rowCount": 0,
    "tasks": []
    

GET/by/job/name/<jobName>

List all entries in the task history which started after the given date/time.. The dates should be in the format [yyyy-MM-dd] (For Example: 2020-09-28) and times in the format [HH:mm] (For Example: 11:43).

  • Base URL
    http://<InstanceAddress>/rest/v1/group/name/<groupName>/project/name/<projectName>/task/filter/by/job/name/<jobName>
  • Server Response
    [
    {
    "id": 62737,
    "type": "RUN_ORCHESTRATION",
    "customerID": 953,
    "groupName": "Docs",
    "projectID": 955,
    "projectName": "Sush-test-Salesforce",
    "versionID": 956,
    "versionName": "default",
    "jobID": 960,
    "jobName": "dim_airport_setup",
    "environmentID": 959,
    "environmentName": "RS",
    "state": "SUCCESS",
    "enqueuedTime": 1601375591924,
    "startTime": 1601375591925,
    "endTime": 1601375592100,
    "message": null,
    "originatorID": "ws_61482_4",
    "rowCount": 0,
    "tasks": [
    {
    "taskID": 1,
    "parentID": -1,
    "type": "VALIDATE_ORCHESTRATION",
    "jobID": 960,
    "jobName": "dim_airport_setup",
    "jobRevision": 2,
    "jobTimestamp": 1601338169683,
    "componentID": 976,
    "componentName": "Start 0",
    "state": "SUCCESS",
    "rowCount": -1,
    "startTime": 1601375591926,
    "endTime": 1601375591927,
    "message": ""
    },
    "hasHistoricJobs": true,
    "jobNames": [
    "dim_airport_setup"
    ]
    }
    ]
    

GET/by/type/<type>

List all entries in the task history with the given task type. For example, Task Type here is "Run Job".

  • Base URL
    http://<InstanceAddress>/rest/v1/group/name/<groupName>/project/name/<projectName>/task/filter/by/type/<type>
  • Server Response
    [
    {
    "id": 62741,
    "type": "RUN_JOB",
    "customerID": 953,
    "groupName": "Docs",
    "projectID": 955,
    "projectName": "Sush-test-Salesforce",
    "versionID": 956,
    "versionName": "default",
    "jobID": 987,
    "jobName": "dim_airports",
    "environmentID": 959,
    "environmentName": "RS",
    "state": "SUCCESS",
    "enqueuedTime": 1601375594970,
    "startTime": 1601375594971,
    "endTime": 1601375595059,
    "message": null,
    "originatorID": "ws_61482_4",
    "rowCount": 0,
    "tasks": []
    }
    ]
    

GET/by/state/<state>

List all entries in the task history with the given state. For example, State here is "success".

  • Base URL
    http://<InstanceAddress>/rest/v1/group/name/<groupName>/project/name/<projectName>/task/filter/by/state/<state>
  • Server Response
    [
    {
    "id": 62741,
    "type": "RUN_JOB",
    "customerID": 953,
    "groupName": "Docs",
    "projectID": 955,
    "projectName": "Sush-test-Salesforce",
    "versionID": 956,
    "versionName": "default",
    "jobID": 987,
    "jobName": "dim_airports",
    "environmentID": 959,
    "environmentName": "RS",
    "state": "SUCCESS",
    "enqueuedTime": 1601375594970,
    "startTime": 1601375594971,
    "endTime": 1601375595059,
    "message": null,
    "originatorID": "ws_61482_4",
    "rowCount": 0,
    "tasks": []
    }
    ]
    

GET/by/start/range/date/<startDate>/time/<startTime>/to/date/<endDate>/time/<endTime>

List all entries in the task history which started between the given date/time range.

  • Base URL
    http://<InstanceAddress>/rest/v1/group/name/<groupName>/project/name/<projectName>/task/filter/by/start/range/date/<startDate>/time/<startTime>/to/date/<endDate>/time/<endTime>
  • Server Response
    [
    {
    "id": 62737,
    "type": "RUN_ORCHESTRATION",
    "customerID": 953,
    "groupName": "Docs",
    "projectID": 955,
    "projectName": "Sush-test-Salesforce",
    "versionID": 956,
    "versionName": "default",
    "jobID": 960,
    "jobName": "dim_airport_setup",
    "environmentID": 959,
    "environmentName": "RS",
    "state": "SUCCESS",
    "enqueuedTime": 1601375591924,
    "startTime": 1601375591925,
    "endTime": 1601375592100,
    "message": null,
    "originatorID": "ws_61482_4",
    "rowCount": 0,
    "tasks": [
    {
    "taskID": 1,
    "parentID": -1,
    "type": "VALIDATE_ORCHESTRATION",
    "jobID": 960,
    "jobName": "dim_airport_setup",
    "jobRevision": 2,
    "jobTimestamp": 1601338169683,
    "componentID": 976,
    "componentName": "Start 0",
    "state": "SUCCESS",
    "rowCount": -1,
    "startTime": 1601375591926,
    "endTime": 1601375591927,
    "message": ""
    },         
    "hasHistoricJobs": true,
    "jobNames": [
    "dim_airport_setup"
    ]
    }
    ]
    

GET/by/end/after/date/<date>

List all entries in the task history by date/time after the given date.

  • Base URL
    http://<InstanceAddress>/rest/v1/group/name/<groupName>/project/name/<projectName>/task/filter/by/end/after/date/<date>
  • Server Response
    [
    {
    "id": 25697,
    "type": "RUN_ORCHESTRATION",
    "customerID": 25605,
    "groupName": "group-name",
    "projectID": 25609,
    "projectName": "project-name",
    "versionID": 25613,
    "versionName": "default",
    "jobID": 25649,
    "jobName": "job_name",
    "environmentID": 25612,
    "environmentName": "environment-name",
    "state": "SUCCESS",
    "enqueuedTime": 1639476988403,
    "startTime": 1639476988404,
    "endTime": 1639476989643,
    "message": null,
    "originatorID": "ws_25622_0",
    "rowCount": 0,
    "tasks": [
    {
    "taskID": 1,
    "parentID": -1,
    "type": "EXECUTE_ORCHESTRATION",
    "jobID": 25649,
    "jobName": "job_name",
    "jobRevision": 12,
    "jobTimestamp": 1639476972535,
    "componentID": 25654,
    "componentName": "Jira Query 0",
    "state": "SUCCESS",
    "rowCount": 0,
    "startTime": 1639476988406,
    "endTime": 1639476989624,
    "message": "",
    "taskBatchID": 25697
    }
    ],
    "hasHistoricJobs": true,
    "jobNames": [
    "job_name"
    ]
    }
    ]
    

GET/by/end/after/date/<date>/time/<time>

List all entries in the task history by end date/time after the given date/time.

  • Base URL
    http://<InstanceAddress>/rest/v1/group/name/<groupName>/project/name/<projectName>/task/filter/by/end/after/date/<date>/time//<time>
  • Server Response
    [
    {
    "id": 25697,
    "type": "RUN_ORCHESTRATION",
    "customerID": 25605,
    "groupName": "group-name",
    "projectID": 25609,
    "projectName": "project-name",
    "versionID": 25613,
    "versionName": "default",
    "jobID": 25649,
    "jobName": "job-name",
    "environmentID": 25612,
    "environmentName": "environment-name",
    "state": "SUCCESS",
    "enqueuedTime": 1639476988403,
    "startTime": 1639476988404,
    "endTime": 1639476989643,
    "message": null,
    "originatorID": "ws_25622_0",
    "rowCount": 0,
    "tasks": [
    {
    "taskID": 1,
    "parentID": -1,
    "type": "EXECUTE_ORCHESTRATION",
    "jobID": 25649,
    "jobName": "job-name",
    "jobRevision": 12,
    "jobTimestamp": 1639476972535,
    "componentID": 25654,
    "componentName": "Jira Query 0",
    "state": "SUCCESS",
    "rowCount": 0,
    "startTime": 1639476988406,
    "endTime": 1639476989624,
    "message": "",
    "taskBatchID": 25697
    }
    ],
    "hasHistoricJobs": true,
    "jobNames": [
    "job_name"
    ]
    }
    ]
    

GET/by/end/range/date/<startDate>/time/<startTime>/to/date/<endDate>/time/<endTime>

List all entries in the task history by end date/time started between the given date/time range.

  • Base URL
    http://<InstanceAddress>/rest/v1/group/name/<groupName>/project/name/<projectName>/task/filter/by/end/range/date/<date>/time/<time>/to/date/<date>/time/<time>
  • Server Response
    [
    {
    "id": 25697,
    "type": "RUN_ORCHESTRATION",
    "customerID": 25605,
    "groupName": "group-name",
    "projectID": 25609,
    "projectName": "project-name",
    "versionID": 25613,
    "versionName": "default",
    "jobID": 25649,
    "jobName": "job_name",
    "environmentID": 25612,
    "environmentName": "environment-name",
    "state": "SUCCESS",
    "enqueuedTime": 1639476988403,
    "startTime": 1639476988404,
    "endTime": 1639476989643,
    "message": null,
    "originatorID": "ws_25622_0",
    "rowCount": 0,
    "tasks": [
    {
    "taskID": 1,
    "parentID": -1,
    "type": "EXECUTE_ORCHESTRATION",
    "jobID": 25649,
    "jobName": "job_name",
    "jobRevision": 12,
    "jobTimestamp": 1639476972535,
    "componentID": 25654,
    "componentName": "Jira Query 0",
    "state": "SUCCESS",
    "rowCount": 0,
    "startTime": 1639476988406,
    "endTime": 1639476989624,
    "message": "",
    "taskBatchID": 25697
    }
    ],
    "hasHistoricJobs": true,
    "jobNames": [
    "job_name"
    ]
    }
    ]
    


Response definitions

The Task API responds by defining the queried jobs and the tasks arrayed within those jobs. The tables below explain how those resources are defined.

Key Description
id The internal ID of the job. This does not change between runs of the job.
type The type of job being run, either RUN_ORCHESTRATION or RUN_TRANSFORMATION.
customerID The internal ID of the project group this job belongs to.
groupName The name of the project group this job belongs to.
projectID The internal ID of the project this job belongs to.
projectName The name of the project this job belongs to.
versionID The project version this job belongs to.
jobID The internal ID of this job.
jobName The name of this job.
environmentID The internal ID of the environment this job has been run in.
environmentName The name of the environment this job has been run in.
state The current state of the job. In the task history, this will be SUCCESS or FAILED. For currently running jobs, the state is RUNNING.
enqueuedTime The time this job was entered into the queue (Unix/Epoch timestamp).
startTime The time this job was executed (Unix/Epoch timestamp).
endTime The time this job ended (Unix/Epoch timestamp).
message The message passed back from the job upon ending. This can include error messages or statements of successful runs, but is usually blank for jobs.
originatorID The internal ID of the websocket (ws_) or scheduler (s_) that launched the job.
rowCount The number of rows affected by this task. Jobs that do not act on rows of data will return 0 or -1.
hasHistoricJob True if this job has Historic Jobs available via the task history. False otherwise. For more information, see Historic Jobs.
jobNames If hasHistoricJob is true, the Historic Jobs's names are listed here

Tasks are individual operations that components use to perform their functions. A task is always called from a component and a component always sits inside a job. Components can call multiple tasks.

Key Description
taskID The internal ID of this task.yea
parentID The internal ID of the parent job for this task.
type A descriptive typing for the current task. Types are generally VALIDATE_, CREATE_, and EXECUTE_, followed by the resource being acted upon. For example, CREATE_VIEW.
jobID The internal ID of the job this task was called from.
jobName The name of the job this task was called from.
jobRevision The revision ID of the job that this task belongs to.
jobTimestamp The timestamp for when this task's current job revision was created (Unix/Epoch timestamp).
componentID The internal ID of the component this task was called from.
componentName The name of the component this task was called from.
state The current state of the task. In the task history, this will be SUCCESS or FAILED. For currently-running tasks, the state is RUNNING.
rowCount The number of rows affected by this task. Tasks that do not act on rows of data will return 0 or -1.
startTime The time this task began (Unix/Epoch timestamp).
endTime The time this task ended (Unix/Epoch timestamp).
message The message passed back from the task upon ending. This usually includes error messages or statements of successful runs. Can be blank.