Bulk API Developer Guide

Introduction to Bulk API
Quick Start
Plan Bulk Data Loads
General Guidelines for Data Loads
Use Compression for Responses
Prepare Data Files
Load Binary Attachments
Request Basics
Work with Jobs
Work with Batches
Bulk Query
Reference
Sample Client Application Using Java
Map Data Fields
Glossary
PDF

Newer Version Available

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

Use Compression for Responses

In API version 27.0 and later, Bulk API can compress response data 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 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 is not compressed.

As an example, if a Batch 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 follows the HTTP 1.1 standards for response compression. Most clients automatically support compressed responses. Visit https://developer.salesforce.com/page/Tools for more information on particular clients.