Note: This release is in preview. Features described here don’t become generally available until the latest general availability date that Salesforce announces for this release. Before then, and where features are noted as beta, pilot, or developer preview, we can’t guarantee general availability within any particular time frame or at all. Make your purchase decisions only on the basis of generally available products and features.

Use Compression for Bulk API 2.0 Ingest Responses

For ingest jobs, Bulk API 2.0 can compress the response body, which reduces network traffic and improves response time.

Responses are compressed if the client makes a request using the Accept-Encoding header, with a value of gzip. Bulk API 2.0 compresses the response in gzip format and sends the response to the client with a Content-Encoding: gzip response header. If a request is made using the Accept-Encoding header with a value other than gzip, the encoding type is ignored, and the response isn’t compressed.

As an example, if a Get Job Successful Record Results request is made with the Accept-Encoding: gzip header, the response looks something like:

1HTTP/1.1 200 OK 
2Date: Tue, 09 Oct 2012 18:36:45 GMT 
3Content-Type: text/csv; charset=UTF-8 
4Content-Encoding: gzip 
5Transfer-Encoding: chunked
6
7...compressed response body...

Bulk API 2.0 follows the HTTP 1.1 standards for response compression, as described in Using Compression. Most clients automatically support compressed responses. Even though you request a compressed response, the REST framework sometimes doesn’t send back the response in a compressed format. Visit https://developer.salesforce.com/page/Tools for more information on particular clients.

Bulk API 2.0 and Bulk API Developer Guide

Use Compression for Bulk API 2.0 Ingest Responses