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

# API Description Import

TestMace allows not only to create API description manually, but also to import an existing documentation from Swagger 2.0 and OpenAPI 3.0.

 You can import API description right from the + context menu by choosing **Import -> Swagger** (there is the same menu in the Scratches area as well):

![The project context menu](/files/-Lh0pQi2448lA3Sg_HP2)

You'll see the next dialog:

![](/files/-Lh0pb1rAlqZWHqkw6yb)

As you can see, both import from file and downloading API from the remote server at a specific URL are supported. The imported description is added to the project tree after you click on the **OK** button.

### API Description Update

You can also update an existing API description. To do that, choose **Update api** from the [ApiRootFolder](/node-types/api-description/apirootfolder.md) context menu. You'll see a dialog similar to the import API dialog. All changes you make in API description will be canceled after the update.


---

# 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.testmace.com/node-types/api-description/import-api.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.