> For the complete documentation index, see [llms.txt](https://docs.testwheel.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.testwheel.com/api-management.md).

# Api Management

This Page describes the API Management feature in TestWheel application.

The **API Management** feature in TestWheel enables users to trigger test executions through **REST API** calls. For every application created, TestWheel generates a unique **API URL** that allows users to initiate test execution seamlessly.

When the API URL is accessed, the test execution is triggered automatically and runs securely in the background. Once the test execution is completed, the test results are automatically sent to the user’s registered email address for review.

Each generated API URL remains active for **90 days**. After the validity period expires, the system displays the API expiry status. Users can renew the API validity easily by clicking the **Renew** button. The platform also provides an option to **Deactivate** the API at any time, giving users greater control and flexibility over API usage and access management.

<figure><img src="https://4225752331-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfpdbhL4mnjdXkFbYOzps%2Fuploads%2Fpgkcv98qwUzsjCiNG7LR%2Fimage.png?alt=media&amp;token=f5815c33-84c7-48d4-9fc7-15dc3de2c6b6" 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.testwheel.com/api-management.md?ask=<question>&goal=<user_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.
