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

# Getting Started

**Overview:** The document introduces the API Process, where multiple APIs are linked together, and their responses are passed between them for comprehensive testing.

**Getting Started:** Learn the basics of API testing to prepare for the process.

**Test Suite Creation:** Create, edit, and manage organized test suites for efficient testing.

**API Import:** Import APIs from various sources, including existing APIs, Swagger files, and Postman collections.

**Manage APIs:** Effectively manage API details, such as endpoints, headers, and parameters.

**Create Flow (Old & New):** Choose between old and new flow creation methods to sequence APIs and establish connections.

**Execute API Flow:** Execute tests as functional or performance tests, with steps for execution and report access.

**Reports (Functional & Performance):** Understand the structure and content of functional and performance reports, including graphical insights.

**Advanced Features:** Explore advanced functionalities, including report actions and parameterized testing.


---

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

```
GET https://docs.qyrus.com/api-testing/api-process-testing/quick-go-through-to-api-process.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.