> For the complete documentation index, see [llms.txt](https://docs.avoautomation.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.avoautomation.com/avo-assure/actions/apis/apis-list/set-whole-body.md).

# Set whole body

This is a pre-built Action located under the **APIs List**. The functionality of this Action in Avo Assure is to set the complete body content for the API request.

{% hint style="info" %}
**Note**: You set the header (e.g., Content-Type) in the previous steps to ensure the request is formed correctly.
{% endhint %}

## **Syntax**

**Input Value**: `<Entire Body Content>`

| Argument                                    | Description                                                                       |
| ------------------------------------------- | --------------------------------------------------------------------------------- |
| <p>\<Entire Body Content><br>(Required)</p> | Provide the body content which you want to sent in the request. (e.g., JSON body) |

**Output Value**: `N/A`

| Argument | Description    |
| -------- | -------------- |
| N/A      | Not Applicable |

### **Example: Setting the Entire Request Body for a API Call**

In this example, we are explaining how to set the complete request body for a API call during API testing.

* **Action**: Set whole body
* **Input Value**: {\
  "first\_name": "john",\
  "last\_name": "smith",\
  "phone": "9898787656",\
  "email": "<johnsmith@gmail.com>",\
  "password": "John\@123",\
  "re\_password": "John\@123"\
  }
  * The input value specifies the complete request payload that should be applied to the API request. The action configures the API to use this body content for subsequent API execution.
* **Output Value**: N/A
* **Logical Explanation**: The **Set whole body** action reads the value from the **Input Value** column (**{**\
  **"first\_name": "john",**\
  **"last\_name": "smith",**\
  **"phone": "9898787656",**\
  **"email": "<johnsmith@gmail.com>",**\
  **"password": "John\@123",**\
  **"re\_password": "John\@123"**\
  **}**) and applies it as the entire request body for the API call.

<figure><img src="https://2174257472-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fk8QZzXZMIJSStKAzDSTu%2Fuploads%2FngrCaAHCIBTY8GuPy81y%2Fimage.png?alt=media&amp;token=41e86f5f-577d-4798-831f-c17544d45c1d" alt=""><figcaption></figcaption></figure>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.avoautomation.com/avo-assure/actions/apis/apis-list/set-whole-body.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.