> 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/get-body.md).

# Get body

This is a pre-built Action located under the **APIs List**. The functionality of this Action in Avo Assure is to retrieve the entire response body from an executed API request and store the result in a dynamic variable.

## Syntax

**Input Value**: `N/A`

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

**Output Value**: `<Dynamic Variable>;<Dynamic Variable>(Optional)`

| Argument                                 | Description                                                      |
| ---------------------------------------- | ---------------------------------------------------------------- |
| <p>\<Dynamic Variable><br>(Required)</p> | This dynamic variable holds the full response body as a string   |
| <p>\<Dynamic Variable><br>(Optional)</p> | This dynamic variable holds the status as **True** or **False**. |

### **Example: Retrieving the Response Body from a API Request**

In this example, we explain how to retrieve the complete response body from an executed API request.

* **Action**: Get Body
* **Input Value**: N/A
  * This action does not require any input value.
  * The action automatically fetches the response body from the previously executed API request.
* **Output Value**: {Body}
  * The first output variable (**{Body}**) stores the complete response body returned by the API request.
  * If a second output variable is provided, the action returns the status as **True** or **False**:
    * **True**: If the response body is retrieved successfully.
    * **False**: If the response body is empty or the request execution fails.
* **Logical Explanation**: The **Get Body** action retrieves the complete response body from the executed API request without requiring any input value. The action stores the fetched response content in the **{Body}** variable.

<figure><img src="https://2174257472-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fk8QZzXZMIJSStKAzDSTu%2Fuploads%2FOn3XgkMoU87lOvnmDyoh%2Fimage.png?alt=media&amp;token=15fa6524-aab2-4dfd-93b7-bdeada2d4040" 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/get-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.