Export results allow users to acquire task data by applying specific filters. This endpoint supports two processing modes: direct export (returns file immediately) and background export (queued processing with notification via export-log).
Export Limits:
Processing Modes:
background=false): File returned immediately in response. Best for small datasets (< 10,000 records)background=true): Export queued for processing. Monitor status via GET /tasks/export-log. Best for large datasetsImportant Notes:
exportConfigId to apply predefined export templates with custom fields and flowsUse a valid Bearer token to authenticate.
Request body containing export parameters. Use filters to narrow down the dataset and fields parameter to select specific columns.
Request body schema for exporting tasks. Use filters to narrow down the dataset and customize the export output.
File type that user want to download. There are 2 types of download:
enum: json,xlsx
Example: xlsx
json, xlsx Fields is for selecting the specific fields that you can choose by multiples to show in the response using a string with a comma delimiter.
Example: startTime,endTime,hubId,createdBy,flow,status
Name of user that completing the task.
Example: Leandro
User email for a given task.
Example: leandro@mile.app
Status of task according to task's data condition. There are 3 types of status:
enum: UNASSIGNED,ONGOING,DONE
Example: UNASSIGNED
UNASSIGNED, ONGOING, DONE The identifier for the flow that generated by system. Use GET /flows API to get the list of flow id.
Comma (,) delimiter for filter multiple flow.
Example: 63d8c9b0dbd5ef20a627dd86,73d8c9b0dbd5ef20a627dd87
The identifier for the hub that generated by system. Use GET /hubs API to get the list of Hub IDs.
Example: 621dd813eb3ebf16b94d6969
Pagination of tasks result list.
Example: 2.
Default: 1
Limit of tasks result list.
Example: 10.
Default: 30
sortBy is used to sort the result-set in ascending or descending order according to selected field. The value of this param is one of available fields on task objects.
Example: flow, assignee, status, hubId, etc.
Default: createdTime
sortOrder is to decide ascending or descending order
Example: asc or desc.
Default: desc
asc, desc If the user sets the background parameter to true, the export process will utilize background processing, and the results will be available at GET /tasks/export-log API. If the user sets the background parameter to false, the export process will run directly, and the results will be immediately available in the response.
Example: true.
Default: false
Unique identifier for the export config for allow user to export data using their own configuration. Use GET /export-configs endpoint to get the list of Export Config IDs.
Example: 634e98498ce07d29474a7e29
Success - Export completed or queued
Status of response.
Message of API response.
Total number of tasks successfully exported.
ID of the last task that was successfully exported.
Name of the last field that was successfully exported.
Export file information. Structure varies based on processing mode (direct vs background).