> 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/avo-assure-supported-technologies-for-automation/api-automation/copy-of-viewing-response-details.md).

# Copy of Viewing Response Details

The APIs response helps you view and verify the results of a APIs request. An API response includes the response body, headers, and HTTP status code. You can check details such as the returned data, response time, and status to ensure the request executes correctly.

* **Response Header**: Displays response headers such as status code, content type, and other metadata.
* **Response Body**: Shows the main content of the API response in all body formats (form-data, x-www-form-urlencoded and raw (JSON or XML)).

## Viewing Response in Element Repository

To view and validate the APIs response, perform the following actions:

1. On the **Element Repository** page, after sending an APIs request, select the **Response** tab.
2. On the **Response** tab, you can validate an APIs response using the following tabs:

<details>

<summary><strong>Response Header</strong></summary>

The **Header** tab displays the **HTTP status code**, **Server**, **response time**, **Content-Type**, and **Length**.

<figure><img src="/files/bBUAJJSekZfMuNeZeMeT" alt=""><figcaption></figcaption></figure>

</details>

<details>

<summary><strong>Response Body</strong></summary>

The **Body** tab displays the response returned by the server. The content is displayed in JSON, XML, or raw format depending on the server returns.

<figure><img src="/files/W7E3lARfcFnluZ4oUFDA" alt=""><figcaption></figcaption></figure>

</details>

## Viewing Response in Test Case

To view and validate the APIs response, perform the following actions:

1. On the **Test Case** page, send the APIs request.
2. Select the **Add Step Manually** (**+**) button. The new step created.
3. Add the required validation steps by using the following actions:
   * **Get Body**: Retrieves the response body from the executed Web Service request.
   * **Get Header**: Retrieves the header value by using the header key.
   * **Get Key Value**: Retrieves a specific key value from the JSON response body.
   * **Get Tag Value**: Retrieves a specific tag value from the XML response body.

{% hint style="info" %}
**Note:** To add APIs test steps, refer to[ Creating APIs Test Case.](/avo-assure/avo-assure-supported-technologies-for-automation/api-automation/creating-apis-test-case.md#adding-elements-manually)
{% endhint %}


---

# 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/avo-assure-supported-technologies-for-automation/api-automation/copy-of-viewing-response-details.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.