Skip to content
Checkcraft
Checkcraft in practice

Chain API requests with extracted variables

A workflow often needs more than one request. Create an object, read it back and compare the identifier or amount. A variable connects the steps without copying values by hand.

Checkcraft team · Updated

What you can verify

The example extracts an identifier and compares it with a value in another part of the data. Use the same principle in a request sequence.

Actual Checkcraft interface. This reference screenshot was recorded in Russian.
Actual Checkcraft interface. This reference screenshot was recorded in Russian. Full size ↗

Extract a specific value

Choose the response path that contains the identifier you need. Save it under a clear variable name. Verify the value after extraction so that a missing or stale variable is caught before the next request.

Use the variable syntax shown by the field

Request templates and test expressions can use different supported variable forms. Follow the field help for {{session.varName}}, %variable% or ${variable}. Do not assume that every syntax works in every input.

Run requests in a known order

Create a request sequence and arrange its steps from top to bottom. Set the body variant and tests for each step. Decide whether a failed request should stop the sequence. Inspect both the request outcome and the test result.

Repeat the check with ready-made files

Download the Checkcraft test case and two inputs. One input is valid, and the other contains a deliberate error. These synthetic examples are available without registration.

Run the example in Checkcraft

Create a collection, a check and a test case using the workspace tree context menu. Click Import in the test case editor and choose the downloaded test case. Open the added case, copy the valid JSON, click Paste data for analysis, then Run test case. Open Result to inspect the report.

Repeat with the broken JSON without changing the rules. The first run should pass and the second should fail. If you see a different outcome, check the selected data source, imported steps and report.

The example files were executed against the application source on 14 September 2026. Reference reports recorded in Russian are available for the passing run and failing run. Sample names and literal data values do not change when you switch the interface language.

Try your own check

See the result on a small example first

Start with the sample, inspect the failure and then try a sanitized example from your own API. Free (beta) is available for Windows and Linux with no time limit.

Get Free (beta)Download and first run

An account and verified email are required to obtain the build. See the edition limits.