# 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](/docs/platform/api-asynch/guide/get-job-successful-results.md) request is made with the `Accept-Encoding: gzip` header, the response looks something like:

```nolang
HTTP/1.1 200 OK 
Date: Tue, 09 Oct 2012 18:36:45 GMT 
Content-Type: text/csv; charset=UTF-8 
Content-Encoding: gzip 
Transfer-Encoding: chunked

...compressed response body...
```

Bulk API 2.0 follows the HTTP 1.1 standards for response compression, as described in [Using Compression](https://developer.salesforce.com/docs/atlas.en-us.api_rest.meta/api_rest/intro_rest_compression.htm). 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.