> For the complete documentation index, see [llms.txt](https://docs.qatts.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.qatts.com/master-1/using-qatts/a-quick-tour-to-api/section-3.md).

# Response

### **Test Log Messages** 

 The detailed information of all the steps and logs of the execution that is taking place on the API is displayed in this section.

![](/files/-MjTi-29q3VBzc--Sh-f)

### **Response Body**

 This is the output that you get through API for the data that was given in the Request Template.

![](/files/-MjTiCtzR_AQMAkt01wK)

### **Response Headers**

 API headers are like an extra source of information for each API call you make. Their job is to represent the meta-data associated with an API request and response.

![](/files/-MjTiSjcQGgfCW2PcA81)

### **Response Schema**

 This is the Validation section where we validate the output(Response Body) is equal to the Input(Request Template) from **Request**.\
 Here If you have parameterized the request template data you will get the output based on the Default Params.

![](/files/-MjTia_NfTLHaaAzC6V8)

### **Header Schema**

 As the response Schema, header schema is similar to it. Assertion to the headers content actions are taken place here.

![](/files/-MjTikbyusvohZiETONG)

### **Data** 

 This is where you get the filtered data that can be done by giving product element in the response schema.

### **Assertion Result** 

Here you get the assertion result that must be getting once the API is tested.


---

# 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.qatts.com/master-1/using-qatts/a-quick-tour-to-api/section-3.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.