Contents
How long does it take to process a batch in bulk API?
Also, if it takes longer than 10 minutes to process a whole batch, the Bulk API places the remainder of the batch back in the queue for later processing.
What happens when I try to use the bulk API?
If you try to use it with create or update, an error is generated. Batches and jobs that are older than 7 days are removed from the queue if they are in a terminal state (completed or failed). The seven days are measured from the youngest batch associated with a job, or the age of the job if there are no batches.
What’s the difference between a batch and a bulk request?
While it makes sense to have this distinction, in reality, the two ideas are often conflated and used interchangeably. “Batch” is often regarded as the more general term (processing batches of requests or batches of data), and “bulk” as a subset of batch (batching data, but not operations).
Can a bulk endpoint be added to a REST API?
Luckily, there is no shortage of REST APIs with public documentation. Most APIs choose to either implement an endpoint that can batch different requests into a single call, or a bulk version of some (or all) endpoints that can accept multiple resources in a single call.
How big is the bulk API in Salesforce?
The Salesforce REST API is great for handling transactional records, or even working with up to 25 records at a time with the composite and batch REST endpoints, but for larger recordsets, up to 100mb in size, the preferred way is using the Bulk API.
How much data can be processed in a 24 hour period?
Due to the limits in place on how many calls you can make to the REST API on a per 24-hour period that may limit how much data you can process an alternative approach is needed. Thankfully, with the Bulk API, you can process up to 100 million records per 24-hour period, which should (hopefully) be more than enough for you.