{"version":"2.1.311","anchor":"api-incremental-request-body-added-to-the-feature-name-list","canonical_anchor":"api-incremental-request-body-added-to-the-feature-name-list","heading":"Incremental request bodies for API calls","tier":"internal","area":"API Requests","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.311\/e\/api-incremental-request-body-added-to-the-feature-name-list","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.311","markdown":"### Incremental request bodies for API calls\n\nA new `api_incremental_request_body` mode lets gzip-compressed API requests reuse parts of earlier request bodies\n\n**What**\n\nClaude Code has a new way of building the request body it sends to the API. The request body is the data uploaded with each request, which includes the conversation.\n\n- A new name, `api_incremental_request_body`, joins the existing `api_gzip_request_body` entries in a list of API-related feature names.\n\n- The gzip path, which compresses request bodies before sending, now also accepts bodies prepared as binary buffers. Before, it compressed only text bodies.\n\n- It keeps fingerprints (\"digests\") of the blocks in a body from one request to the next. It also reports how much of each body was reused and whether an incremental body was sent.\n\n**Why**\n\nIn a long conversation, much of each request repeats the previous one. Reusing those parts across requests can shrink what has to be uploaded each time.\n\n- Area: API Requests\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: no"}