Common JSON format across all the results
All the results returned by the REST API are nested within theResponse object’s entity field as follows:
All responses are contained within a
Response object. The entity field contains the actual response data. The status field contains the HTTP status code of the response. The responses may contain additional data from the Response object.Response’s status field is set to 500):
Endpoints and responses
The following matrix outlines the different endpoints and the information their response contains.Enhanced Drillthrough endpoints and responses
Here are the endpoints exposed by the Enhanced Drillthrough component of the Extraction Engine:Response examples
Below are examples for the different endpoints.Submit calls
The methodssubmitOrders and submitTemplateOrders return the list of task ids (String) as a result.
Example response for submitOrders:
Template calls
The methodsaddTemplateOrder and removeTemplateOrder do not return any specific value.
Clean-up calls
The methodclearOldCompletedTasks returns the number of tasks cleared.
Example response:
Check if task(s) is completed
The methodsisTaskCompleted and isTaskListCompleted simply return a boolean.
Example response for isTaskCompleted:
Status calls
The methodsgetTaskStatus, getTaskListStatus, cancelTask and cancelTaskList return a result based on the DeeTaskInfoDTO and DeeResultFileInfoDTO classes.
Below are examples of JSON response DTO objects:
JSON status call result format
Enhanced Drillthrough REST responses
Execute search facts query
Returns a list of Object[] representing the extracted attributes for each fact that fell into the query scope.Execute Enhanced Drillthrough query
Returns no content, just an ok or error status.Retrieve Enhanced Drillthrough result
The REST service returns a JSON object following theEnhancedDrillthroughTaskInfoDTO definition.
Example of output:
Cancel Enhanced Drillthrough
The REST service returns a JSON object following theEnhancedDrillthroughTaskInfoDTO definition.
Example of output: