Bulk API 2.0 and Bulk API Developer Guide

Introduction to Bulk API 2.0
What’s the Difference Between Bulk API 2.0 and Bulk API?
How Requests Are Processed
Limits
Getting Started
Bulk API 2.0
Bulk API
Glossary
PDF

Newer Version Available

This content describes an older version of this product. View Latest

Limits

Learn about the importance of limits, and compare the limits and allocations of Bulk API 2.0 and Bulk API. For Bulk API 2.0, we simplified limits, which are available to clients via the REST API /limits endpoint.

Approaching the Limit

Limits are in place to ensure optimal performance for all customers and to provide fair access to system resources. Each org is only able to handle a certain number of API requests within a 24-hour period. Budget your overall API consumption to account for what each integration does against the org.

Questions that might help to plan for limits:

  • How many other integrations are making API requests into your org?
  • How close does your org come to reaching its entitled request limit each day?
  • How many API requests per day would be required in order to address your use cases and data volume?
  • Of the APIs that could do the job you’re planning, what are their limits characteristics?

So consider both what your new implementation is attempting to do as well as what existing integrations are doing to make sure your workloads won’t be interrupted.

Batch Allocations

You can submit up to 15,000 batches per rolling 24-hour period. This allocation is shared between Bulk API and Bulk API 2.0, so every batch that is processed in Bulk API or Bulk API 2.0 counts towards this allocation.

In Bulk API 2.0, only ingest jobs consume batches. Query jobs do not. For details, see How Requests Are Processed in the Bulk API 2.0 Developer Guide.

In Bulk API 2.0, batches are created for you automatically. In Bulk API, you must create the batches yourself.

General Limits

Item Bulk API Limit Bulk API 2.0 Limit
Batch and job lifespan Batches and jobs that are older than seven days are removed from the queue if they are in a terminal state (completed or failed) regardless of job status. The seven days are measured from the youngest batch associated with a job, or the age of the job if there are no batches. You can’t create batches associated with a job that is more than 24 hours old. Jobs that are older than 7 days are deleted if they are in a terminal state (completed or failed),
Binary content
  • The length of any file name can’t exceed 512 bytes.
  • A zip file can’t exceed 10 MB.
  • The total size of the unzipped content can’t exceed 20 MB.
  • A maximum of 1,000 files can be contained in a zip file. Directories don’t count toward this total.
 N/A
Maximum time that a job can remain open 24 hours The same. (But this only applies to ingest jobs, not query jobs.)

Limits Specific to Ingest Jobs

Item Bulk API Limit Bulk API 2.0 Limit
Maximum number of records uploaded per 24-hour rolling period 150,000,000 (15,000 batches x 10,000 records per batch maximum) 150,000,000
Batch processing time Batches are processed in chunks. The chunk size depends on the API version. In API version 20.0 and earlier, the chunk size is 100 records. In API version 21.0 and later, the chunk size is 200 records. 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. If the Bulk API continues to exceed the 10-minute limit on subsequent attempts, the batch is placed back in the queue and reprocessed up to 10 times before the batch is permanently marked as failed. Same as Bulk API
Maximum time before a batch is retried 10 minutes The API automatically handles retries. If you receive a message that the API retried more than 10 times, use a smaller upload file and try again.
Maximum file size 10 MB 150 MB
Maximum number of characters in a field 131072 Same as Bulk API
Maximum number of fields in a record 5,000 Same as Bulk API
Maximum number of characters in a record 400,000 Same as Bulk API
Maximum number of records in a batch 10,000 N/A
Maximum number of characters for all the data in a batch 10,000,000 N/A

Limits Specific to Query Jobs

Item Bulk API Limit Bulk API 2.0 Limit
Number of attempts to query 15 attempts at 10 minutes each to process the batch. There is also a 2-minute limit on the time to process the query. If more than 15 attempts are made for the query, an error message of “Tried more than fifteen times” is returned. If the query takes more than 2 minutes to process, a QUERY_TIMEOUT error is returned. The API automatically handles retries. If you receive a message that the API retried more than 15 times, apply a filter criteria and try again.
Number of retrieved files 15 files. If the query returns more than 15 files, add filters to the query to return less data. Bulk batch sizes are not used for bulk queries. N/A
Results lifespan 7 days Same as Bulk API
Maximum retrieved file size 1 GB. If processing of the batch results in 1GB of retrieved data, then those results are saved to disk, and then the batch is put back on the queue to be resumed later. This also counts as one of the 15 retries. Same as Bulk API.

Additionally, the API client can navigate through the full set of results by using the locator and maxRecords query parameters. The client is not bound to a set of files.
Number of query jobs that can be submitted per 24-hour rolling window See Batch Allocations. 10,000

The current number can be seen in the DailyBulkV2QueryJobs value in the response to the /vXX.X/limits/ REST API method.
Total query results that can be generated per 24 hour rolling window N/A 1 TB.

The current size can be seen in the DailyBulkV2QueryFileStorageMB value in the response to the /vXX.X/limits/ REST API method.
Number of characters in a SELECT clause.

This limit pertains to all the fields listed between SELECT and FROM. This includes the commas that separate the fields and the quotation marks that Salesforce automatically wraps around each field. Salesforce automatically removes any spaces between fields.

For example, in this query

SELECT CloseDate,​Name,​StageName,​Amount FROM Opportunity

Salesforce converts the SELECT clause to

"CloseDate",​"Name",​"StageName",​"Amount"

The number of characters in this example is 39.

 N/A 32,000