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

# API Automation

API Automation helps you to validate backend services without relying on the application’s user interface. You can create the API Test Cases and execute within the Avo Assure platform, which also supports functional and UI automation to enable complete end-to-end validation.

When automating APIs in Avo Assure, the Element Repository serves as a key component for sending requests and receiving responses using various HTTPs methods and endpoint URLs. This capability enables real time interactions such as setting parameter values, tag value, tag attributes, and retrieving these values from the request body of the API endpoint for validation and automation.

## This Document Includes

[**Prerequisites**](/avo-assure/avo-assure-supported-technologies-for-automation/api-automation/prerequisites.md)\
Prerequisites for API automation.

[**Understanding HTTP Status Codes**](/avo-assure/avo-assure-supported-technologies-for-automation/api-automation/understanding-http-status-codes.md)\
Overview of HTTP Status Codes along with their descriptions.

[**Element Repository Interface and Functional Flow**](/avo-assure/avo-assure-supported-technologies-for-automation/api-automation/element-repository-interface-and-functional-flow.md)\
Understanding the Element Repository Interface and its Functional Flow for API.

[**Creating API Element**](/avo-assure/avo-assure-supported-technologies-for-automation/api-automation/creating-apis-in-element-repository.md)\
Creating API requests and importing API definitions in Element Repository.

[**Viewing Response Details**](/avo-assure/avo-assure-supported-technologies-for-automation/api-automation/viewing-response-details.md)\
Viewing the API response in Element Repository.

[**Creating API Test Case**](/avo-assure/avo-assure-supported-technologies-for-automation/api-automation/creating-apis-test-case.md)\
Creating Test Case for API Automation.


---

# 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.avoautomation.com/avo-assure/avo-assure-supported-technologies-for-automation/api-automation.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.