> 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.
---
# 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/avo-assure-supported-technologies-for-automation/api-automation/element-repository-interface-and-functional-flow/about-the-response-tab.md?ask=&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.
