# API testing tutorial: from your first request to a check that catches bugs

Source: https://checkcraft.ru/en/guides/api-testing-tutorial.html · updated 2026-11-23

API testing for beginners: how to send a request, what to check besides status 200…

Practical workflow

Checkcraft is a desktop app for checking APIs and logs without code, with a free edition. [Download, no sign-up →](https://checkcraft.ru/en/download-checkcraft.html#free-download)

API testing is not “did a response arrive” but “is it right, and what happened after it”. Here are five steps from the first request to a check that catches the bug on every run.

Checkcraft · 23 November 2026

Get help with your first test →

## Step 1. Write the expectation before the request

Start from the requirement: which fields must come back and how they relate. For an order: total = subtotal − discount, status is one of NEW, PAID, SHIPPED, CANCELLED. The expectation comes from the requirements, not from the first server response, or the test will lock the bug in.

## Step 2. Send the request and compare

Send it from curl, Postman or right from the practice API page.

Repeating checks like this by hand? Checkcraft saves them and reruns them in one click. [Download Free →](https://checkcraft.ru/en/download-checkcraft.html#free-download)

```
# 1. Send a request
curl -s https://checkcraft.ru/practice-api/v1/orders/5001.json

# 2. What came back (excerpt)
"subtotal": 3170.00, "discount": 300.00, "total": 2970.00

# 3. What to check
status 200                         ✓
total = subtotal − discount        ✗  (3170 − 300 = 2870, the API says 2970)
```

## Step 3. Check more than the status

A 200 means the server understood the request, not that the result is right. Check types (a number, not a string), allowed values, extra fields (leaks), calculations, every array item and consistency between answers: the list and the card must agree.

## Step 4. Look at what happened after the response

The most expensive bugs come after the response: the payment service never got the request, the log has an error, the database row is still NEW. Find the log records of the same request by traceId and check their fields; with database access, run a SELECT by the ID.

[Search a log by traceId online →](https://checkcraft.ru/en/guides/log-search-online.html)

## Step 5. Save the check and hand it to an AI

A manual check is forgotten after the release. Save the rules so they run every time, by hand or in CI. Checkcraft does it without code: the response, the log by traceId and the database in one check. An AI drafts the checks from the requirement, either the built-in local one (Windows build) or your Claude Code and Cursor over MCP, and they run the same way every time. You make the call.

## Practise

All ten typical bugs from this tutorial hide in the practice API. Find them and get into the hall of fame.

[Bug hunt →](https://checkcraft.ru/en/guides/bug-hunt.html)

Next step

## Repeat this on your own API

Checkcraft is a desktop app that saves API response checks without code and shows what did not match. Start with a sample, then use your own sanitized data. Free runs on Windows and Linux with no time limit.

[Download Free](https://checkcraft.ru/en/download-checkcraft.html#free-download) · [Download and first run](https://checkcraft.ru/en/download-checkcraft.html)

No sign-up or email needed, the archive is ready in a couple of minutes. See the [edition limits](https://checkcraft.ru/en/pricing.html).

## Continue with a related task

[Free APIs for testing: JSONPlaceholder vs DummyJSON vs Reqres, and one with real bugs](https://checkcraft.ru/en/guides/free-apis-for-testing.html) · [Bug hunt: find 10 bugs in the practice API and get into the hall of fame](https://checkcraft.ru/en/guides/bug-hunt.html) · [Postman online: the web version, its limits and how to test an API in your browser](https://checkcraft.ru/en/guides/postman-online.html) · [An API client that checks Kibana logs and the database, not just the response](https://checkcraft.ru/en/guides/api-client-kibana-logs-database.html) · [Checkcraft MCP server: an AI agent checks the API, logs and database](https://checkcraft.ru/en/guides/mcp-server.html) · [HTTP 200 but the result is wrong](https://checkcraft.ru/en/guides/http-200-wrong-result.html)

Start with the linked example and compare its result with your own test requirement.

Ask a person

## Get help with your first test

Tell us what you want to test or where you got stuck. We can help you start Checkcraft, choose an example and understand your first run. You can ask before downloading.

[Ask in Telegram](https://t.me/checkcraftchat)Send an email

The Telegram group is public: do not post passwords, tokens or confidential work data. A description of your task is enough to start.

You can also email us support@checkcraft.ru

Page card: /ai/pages/en/guides/api-testing-tutorial.md
