> 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/actions/apis/assertion.md).

# Assertion

API Assertions are validation checks that verify whether an API response matches the expected outcome. They ensure that an API behaves correctly by automatically validating different aspects of the response, such as the status code, response time, headers, response body, or specific data values. Assertions perform these validations during test execution and indicate whether the verification has passed or failed. As a result, API testing becomes more reliable and efficient.

For example, you can use assertions to verify that an API returns the expected [HTTP status code](/avo-assure/avo-assure-supported-technologies-for-automation/api-automation/understanding-http-status-codes.md) (200 or 404).

Assertions automate response validation to improve test accuracy, reduce manual verification effort, and increase confidence in API quality and stability. This article explains the different assertion actions that help validate API responses during test execution.

## Prerequisites

* API Test Step Group must be created.
* An API request must be added and executed successfully before configuring or evaluating API Assertions.

#### This Section Includes Following Actions:

* [Status Code](/avo-assure/actions/apis/assertion/status-code.md)
* [JSONPath Match](/avo-assure/actions/apis/assertion/jsonpath-match.md)
* [Response time](/avo-assure/actions/apis/assertion/status-code-1.md)
* [Response body contains](/avo-assure/actions/apis/assertion/status-code-2.md)
* [Response body not contains](/avo-assure/actions/apis/assertion/status-code-3.md)
* [Response body equals](/avo-assure/actions/apis/assertion/response-body-equals.md)
* [Header exists](/avo-assure/actions/apis/assertion/header-exists.md)
* [Header value](/avo-assure/actions/apis/assertion/header-value.md)


---

# 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/actions/apis/assertion.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.