> 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/web-service-operations/web-service-list/set-whole-body.md).

# Set whole body

This is a pre-built action located under the **WebService List Element**. The functionality of this action in Avo Assure is to set the entire body content for the web service request.

{% hint style="warning" %}
***Note:** The header (such as **Content-Type**) should be set in the previous steps to ensure proper request formation.*
{% endhint %}

### **Syntax**

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

| Argument                          | Description                                                               |
| --------------------------------- | ------------------------------------------------------------------------- |
| \<Entire Body Content> (Required) | Provide the full body content to be sent in the request (e.g., JSON body) |

**Output Value**

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

**Example**

**Sets the Entire Request Body for a Web Service Call**

The **Set whole body** action takes the value from the Input Value column and sets the entire body content for the web service request.

**JSON Body:**

{\
"first\_name": "john",\
"last\_name": "smith",\
"phone": "9898787656",\
"email": "<johnsmith@gmail.com>",\
"password": "John\@123",\
"re\_password": "John\@123"\
}

<figure><img src="/files/PCOTphRu7DVhb7HMub7G" 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

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

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.