---
title: "res_body | Speedscale Docs"
description: "Discover how to effectively utilize Speedscale extractors to gather and manipulate response body data in your application traffic. This documentation provides detailed instructions and examples to optimize your monitoring and testing processes."
canonical: "https://docs.speedscale.com/guides/transformation/extractors/res_body/"
---

[Documentation index](https://docs.speedscale.com/guides/llms.txt) | [Markdown](https://docs.speedscale.com/guides/transformation/extractors/res_body/index.md) | [Canonical page](https://docs.speedscale.com/guides/transformation/extractors/res_body/)

# res\_body

<a id="purpose"></a>

### Purpose

**res\_body** extracts the request body of the RRPair. For HTTP requests the response body will be returned as raw bytes. For non-HTTP protocols the body will be converted into a human readable JSON representation. The JSON itself can be modified by transforms and it will be re-inserted into the appropriate location within that protocol. For instance, if this extractor is applied to a GRPC message then a set of numbered fields in JSON format will be the output. You can then use a `json_path` transform to modify a field and the new value will be re-inserted.

<a id="usage"></a>

### Usage

```json
"type": "res_body",
```

This extractor has no user configuration.

<a id="example"></a>

### Example

```json
"type": "res_body"
```
