201$.data.status equals confirmedX-Request-Id is present800msA brick is a single API call stored as an editable record: method, URL, headers, body, auth, variables, response checks, even the host it hits. Chain them into scenarios, branch, loop, retry — with full visibility at every step.
Stop digging through generated code. Each request lives as a transparent record you can edit in the UI: method, URL, headers, body, auth, variables, assertions — even which host it hits. Bricks chain together into scenarios that feel alive. You see the wiring. You own it.
accessTokencartId, cartItemsorderIdMethod, URL template, headers, body, files, auth — fully tweakable in the admin UI. No codegen blackbox.
Extract from one brick, reuse downstream: {orderId}, {option.API_HOST}.
Retry until a condition, poll an async job, run on items, skip bricks with conditions — first-class, no hacks.
JSONPath, raw body, response headers, latency — each check fails the brick with a human-readable reason.
https://… or {option.HOST}.{API_TOKEN}.No more opening a generated file to figure out why the request looks odd. Every detail is in front of you, every save is a revision, every variable has a known origin, and every response has human-readable checks. When something flakes — you know exactly which brick, which field, which check.