> 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/element-repository-interface-and-functional-flow/about-the-response-tab.md).

# About the Response Tab

The Response tab in the Element Repository displays the server’s response to the executed API request. It is used for validating responses, troubleshooting failures, and analyzing returned data during API testing.

On the **Element Repository** page (Home > Select Project > Design Studio > Element Repository > Response tab), you can do the following:

1. Body: This tab shows the response message returned by the server. The content is displayed in JSON/XML, form-data and x-www-form-urlencoded format depending on the server returns.
2. Header:
   * This tab lists all response headers received from the API, such as server details, content type, and cache information.
   * The tab also provides additional execution details such as:
     * The HTTP status code received from the server. This helps to determine whether the request was successful (e.g., 200, 201) or resulted in errors such as client errors (400, 401, 404) or server errors (500, 503).
     * The response time.
     * The result of the request indicating whether it passed or failed.

<figure><img src="/files/3HbbpRt9P4rpaC8tSnOz" 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/avo-assure-supported-technologies-for-automation/api-automation/element-repository-interface-and-functional-flow/about-the-response-tab.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.
