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

# API Testing

- [API Testing Overview](https://learning.contextqa.com/api-testing/api-testing.md): Automate REST API testing in ContextQA — request configuration, response validation, API chaining, and hybrid API-plus-UI test flows, all with no code.
- [Creating API Tests](https://learning.contextqa.com/api-testing/creating-api-tests.md): Create ContextQA API tests manually, import a cURL command, reuse variables, capture responses, chain requests, or generate coverage from OpenAPI.
- [Validating Responses](https://learning.contextqa.com/api-testing/validating-responses.md): Response validation techniques in ContextQA — payload validation, structure validation, status codes, and header assertions.
- [API Chaining](https://learning.contextqa.com/api-testing/api-chaining.md): Chain API requests in ContextQA by extracting response fields, reusing auth tokens, and passing runtime data into later API or UI test steps.
- [Tutorial: Your First API Test](https://learning.contextqa.com/api-testing/api-testing-tutorial.md): Build a two-step API test that authenticates against a REST endpoint, captures the access token, chains it into a second request, and validates the response — all without writing code.
- [Mock API Testing](https://learning.contextqa.com/api-testing/mock-api-testing.md): Capture real API responses during test execution and replay them as mocks on future runs for faster, more stable tests.


---

# 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://learning.contextqa.com/api-testing.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.