Core Bulk

the bulk api is expected to be used with a large number of rows the bulk process runs asynchronously and calls an automation endpoint on completion its best to use this when you are expecting a process to run over for more than a minute there are three parts to this api input is expected to be a large list of json objects functions a list of any of the core functions in the function json representation format defined here output an output definition for each of the items in the input list there is a minor difference in the way the functions list is created follow the example in the api for clarity this will be aligned in future releases of the bulk api webhooks in this api name description completion required the api will be rejected without a valid automation url this is where the output along with the "process name" will be sent as a post resquest progress optional use this to track the progress of api this works in conjunction with progress rows and sends a progress notification for every n rows (100 in this example) error optional useful to track any failure the error notification works on every item of the list that is being processed any error will not stop processing but will send a notification to he url specified and continue to process the remaining items api definition