# Adding API

In this Chapter you will be given a overview of API Testing with QATTS.

![](/files/-MjTlQc4lCPw2xE94qrL)

The following is the description of adding an API in detail:&#x20;

* **API Name:** Giving proper name for the API based on the module.
* **Description:** Giving proper description related to module that you are going to work on.
* **Type:** Giving the Type of response.
  * **REST** (Representational State Transfer) - This is used when the request and response format are not in XML, i.e. it can be in JSON, HTML or any other format.
  * **SOAP**( Simple Object Access Protocol) - This is used when the request and response format of the API are in the XML format.
* **Select Group:** Select the Group name.
* **HTTP Methods:** Select the HTTP Method that needs to be performed on the API.
  * **Note**: POST, PUT, PATCH will have the request template( Need an Input to test API). GET will not have the request template unless for some special conditions.
* &#x20;Here by clicking on the **Eye** you can select the deployment that you are going work on.

Then Click on the **Save** Button.

Once saved more options are now visible to work with.


---

# Agent Instructions: 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:

```
GET https://docs.qatts.com/using-qatts/a-quick-tour-to-api/section-1.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
