Custom Jobs allow you to create exports for any date range. If the date range spans multiple days, they will generate separate output days. Jobs can be deleted with the Job resource. When a Job is completed successfully, the results are visible as days in the Day resource.
resource_typetype: stringThe type of communication – Messages, Calls, Conferences, and Participants
webhook_urltype: stringThe optional webhook url called on completion of the job. If this is supplied, WebhookMethod must also be supplied.
webhook_methodtype: stringThis is the method used to call the webhook on completion of the job. If this is supplied, WebhookUrl must also be supplied.
detailstype: objectThe details of a job which is an object that contains an array of status grouped by status state. Each status object has a status string, a count which is the number of days in that status, and list of days in that status. The day strings are in the format yyyy-MM-dd. As an example, a currently running job may have a status object for COMPLETED and a status object for SUBMITTED each with its own count and list of days.
job_queue_positiontype: stringThis is the job position from the 1st in line. Your queue position will never increase. As jobs ahead of yours in the queue are processed, the queue position number will decrease
estimated_completion_timetype: stringthis is the time estimated until your job is complete. This is calculated each time you request the job list. The time is calculated based on the current rate of job completion (which may vary) and your job queue position
| ENUM:STATUS possible values | |
|---|---|
ErrorDuringRun | The Job was attempted, but an error prevented completion. This is not a final status, the job will be retried. |
Submitted | The Job has been successfully submitted and is in the queue to execute. |
Running | The job is currently running. The output should be available shortly. Multiple Jobs may run at the same time. You can use the 'estimated_completion_time' to get a sense of when your job will be complete. |
CompletedEmptyRecords | The Job has been completed, however, no records for the requested resource have been found. An empty file will be available at the Day endpoint. |
Completed | The Job has completed, and the result files are available at the Day endpoint. |
Failed | The Job was attempted, but an error prevented completion. This is a final status, as the job has already been tried multiple times and has not been successful. Try submitting the job again, or reach out to your Twilio support team if the problem continues to persist. |
RunningToBeDeleted | The Job is currently running, but it has been marked for deletion and will be deleted soon. |
DeletedByUserRequest | The Job has been marked for deletion. So the system will not attempt to run it. |
POST https://bulkexports.twilio.com/v1/Exports/{ResourceType}/JobsResourceTypetype: stringThe type of communication – Messages or Calls, Conferences, and Participants
StartDaytype: stringRequiredThe start day for the custom export specified as a string in the format of yyyy-mm-dd
EndDaytype: stringRequiredThe end day for the custom export specified as a string in the format of yyyy-mm-dd. End day is inclusive and must be 2 days earlier than the current UTC day.
WebhookUrltype: stringThe optional webhook url called on completion of the job. If this is supplied, WebhookMethod must also be supplied. If you set neither webhook nor email, you will have to check your job's status manually.
WebhookMethodtype: stringThis is the method used to call the webhook on completion of the job. If this is supplied, WebhookUrl must also be supplied.
Emailtype: stringThe optional email to send the completion notification to. You can set both webhook, and email, or one or the other. If you set neither, the job will run but you will have to query to determine your job's status.
GET https://bulkexports.twilio.com/v1/Exports/{ResourceType}/JobsResourceTypetype: stringThe type of communication – Messages, Calls, Conferences, and Participants
PageSizetype: integerHow many resources to return in each list page. The default is 50, and the maximum is 1000.