CLEM 1.0.1.6 · Windows · macOS · Linux

Test your API as a flow.
Run it anywhere.

CLEM is a desktop app for API testing. Build a flow of requests, pass values from one to the next, check every response, and run the same flow in CI as a plain Node.js script.

Free for individuals, education, open source and companies under 25 employees and $1 million revenue. Pricing

  • REST, GraphQL, server-sent events and WebSockets
  • Imports Postman, Bruno and Insomnia collections
  • Runs in CI without CLEM installed
The CLEM window: a tutorial flow of six steps (log in, who am I, create a product, change the price, a code block, delete) and the run log with every check passed The CLEM window: a tutorial flow of six steps (log in, who am I, create a product, change the price, a code block, delete) and the run log with every check passed
How it works

From first request to CI in three steps

  1. Build a flow

    Add requests one by one, or import a collection you already have. Extract values from a response and use them in the steps that follow.

  2. Run it and read the log

    Press Run Flow. Every step shows what was sent, what came back and which checks passed or failed.

  3. Hand it to CI

    Export the flow as a Node.js script. It runs in your pipeline with the same checks, and writes HTML and JUnit reports.

All of it in about 30 seconds, recorded in the real app: add a request and a code block, run the flow, export it, run the script in a terminal and open its HTML report.
Features

Everything an API test needs, in one flow

A flow is a list of steps that run top to bottom: requests, code and pauses. Each step can use what the steps before it found.

Requests that pass values along

Log in, keep the token, and use it in every request that follows. Extract any value from a response into a $variable and use it in URLs, headers and bodies.

  • JSON, form, multipart, file and GraphQL bodies
  • Basic, Bearer, API key and OAuth 2.0, per flow or per request
  • Test Request sends one step without running the flow
Requests in the docs →
The request editor: a POST to $baseUrl/auth/login with a JSON body The request editor: a POST to $baseUrl/auth/login with a JSON body

Check every answer

Checks turn requests into tests. Every check runs and shows up in the log, so a failure tells you exactly what was expected and what came back.

  • Status, response time, headers and body
  • JSON paths, XPath and JSON Schema
  • equals, contains, matches regex, length, type, greater / less than
Checks in the docs →
The Checks tab with eight checks: status, time, a header, the body, three JSON paths and a JSON Schema The Checks tab with eight checks: status, time, a header, the body, three JSON paths and a JSON Schema

See what every step did

A run writes a log you can read: each step with its result and time, and under it the request that was sent and the response that came back.

  • PASSED, FAILED or SKIPPED for every step, with the reason
  • JSON and XML as trees, CSV as a table, images and PDFs as previews
  • Secrets and tokens are masked in the log and in reports
  • One HTML report for a flow or for a whole project
Running and logs in the docs →
The run log: three steps passed, each with its request, status, time and the checks that ran The run log: three steps passed, each with its request, status, time and the checks that ran

Code when clicks aren't enough

Code blocks are JavaScript, run by Node.js, with helpers for requests, JSON paths, files and cookies. Loop over results, retry until a job is done, or write your own checks.

  • Requests inside code, loops and retries
  • Shared functions for every step, and imported libraries
  • Steps that always run, for cleanup after a failure
Code blocks in the docs →
A flow with a code block that loops over products and checks their prices A flow with a code block that loops over products and checks their prices

One flow, every environment

Keep what changes between dev, staging and prod in environments, and switch with one click. Secrets are encrypted on your computer and never written to a flow file.

  • Environments per project
  • Secrets that stay out of files and out of AI's reach
  • Data-driven runs: once per row of a CSV or JSON file
Environments in the docs →
The environments editor with dev and staging values The environments editor with dev and staging values

Bring your Postman, Bruno and Insomnia collections

Start from what you already have. Every import shows a preview first, then opens as a new flow or is added to the one you have open.

  • Postman collections (v2.0, v2.1 and the v3 folder format) and environments
  • Bruno collection folders, environments included
  • Insomnia exports (v4 JSON or v5 YAML), environments included
  • cURL commands, OpenAPI / Swagger and browser HAR recordings
Import in the docs →
The Import menu: cURL command, HAR recording, OpenAPI / Swagger, Postman collection, Postman collection folder, Postman environment, Bruno collection, Insomnia collection The Import menu: cURL command, HAR recording, OpenAPI / Swagger, Postman collection, Postman collection folder, Postman environment, Bruno collection, Insomnia collection

From your desk to CI, unchanged

Export a flow, or a whole project, as standalone Node.js scripts. CI needs Node.js and an npm install: no CLEM install, no license server, no account.

  • HTML reports, JUnit XML and JSON summaries
  • A suite runner with tags, environments, --parallel and --bail
  • Jenkins, GitHub Actions, GitLab, Azure DevOps
Export and CI in the docs →
The Export dialog: this flow or the whole project, with the suite runner option The Export dialog: this flow or the whole project, with the suite runner option

Reports you can send to anyone

One HTML file with the whole run: the result, the time, every step with its checks, and each request and response one click away. It opens in any browser, with nothing to install.

  • From the app (Run flow with report) or from an exported script (--report)
  • One report for a whole project, with a line per flow
  • Secrets and tokens masked, like in the log
  • A dark and a light theme, switched in the report
Reports in the docs →
An HTML report of the tutorial flow: passed, 6 of 6 steps, 19 of 19 checks, and each step with its request and checks An HTML report of the tutorial flow: passed, 6 of 6 steps, 19 of 19 checks, and each step with its request and checks

Let your AI build the tests

CLEM has an MCP server. AI clients such as Claude, GitHub Copilot, Cursor, OpenAI Codex and Gemini CLI can read, write, run and fix your flows the way you do.

  • You decide what an AI may do: read, change, delete, run, run code
  • Secret values never reach the model
  • Limit the hosts an AI's requests may go to
AI access in the docs →
Settings, AI access (MCP): the permissions an AI client gets Settings, AI access (MCP): the permissions an AI client gets
Your flows are files

Readable in a diff. Runnable in a pipeline.

A flow is a .clem.json file in a project folder. Put the folder in git, review changes in a pull request, and run the exported script in CI.

first-request.clem.json
{
  "name": "first-request",
  "globals": [{ "name": "$baseUrl", "value": "https://dummyjson.com" }],
  "steps": [{
    "type": "request",
    "name": "Get a product",
    "method": "GET",
    "url": "$baseUrl/products/1",
    "checks": [
      { "target": "status", "op": "equals", "value": "200" },
      { "target": "json", "path": "$.title", "op": "type", "value": "string" }
    ]
  }]
}
CI
npm install                 # once

# one exported flow: prints the log, exit code 0 = passed
node first-request.js --env staging --report report.html

# override a variable for this run
node first-request.js --set $baseUrl=https://qa.example.com

# every flow of a project: one report, JUnit for the CI
node clem-suite.js --tag smoke --junit results.xml

# what CI needs: Node.js and one npm install
✓ no CLEM install · no account · no license server
Pricing

Free for most. Fair for the rest.

One CLEM with every feature. Organisations with 25 or more employees or over $1 million in annual revenue pay $6 per user per month, billed yearly ($72 per user).

Questions

What is CLEM?

A desktop app for Windows, macOS and Linux that tests APIs as flows. A flow is a list of steps (requests, code blocks and pauses) that run top to bottom, and each step can use what the steps before it found. Checks on each response turn the flow into a test.

You can think of a flow as "E2E" for your backend: a user journey, such as a booking path from search to confirmation or an order from cart to refund, tested from the first request to the last. A flow can also be a suite of steps that each test one of your API routes on its own, with every step run even when one fails.

Is CLEM free?

Yes, for individuals, education, open source, and organisations with fewer than 25 employees and under $1 million in annual revenue. Larger organisations pay $6 per user per month, billed yearly ($72 per user). Every feature is in both. See pricing.

Can I import my Postman, Bruno or Insomnia collections?

Yes. CLEM imports Postman collections and environments, Bruno collection folders and Insomnia exports, and also cURL commands, OpenAPI / Swagger descriptions and HAR recordings. Each import shows a preview of what comes in before it becomes a flow. See Import in the docs.

How do I run my API tests in CI?

Export a flow, or a whole project, as standalone Node.js scripts and run them in your pipeline. CI needs Node.js and one npm install, not CLEM. The scripts write HTML reports, JUnit XML and JSON summaries, and the exit code says whether the run passed. See Export and CI.

Do I need an account? Where are my flows kept?

There is no account and no cloud workspace. Flows are .clem.json files in a folder on your computer, so you can keep them in git. Secrets are encrypted on your computer and never written to a flow file. CLEM has no telemetry: see the privacy policy.

Is it only for REST APIs?

REST is the main use. CLEM also sends GraphQL queries, reads server-sent events, talks to WebSockets (sends messages, waits for the replies, and can keep a connection open while the next steps run), and handles file uploads and downloads.

Build your first flow in five minutes

CLEM comes with ready-made example flows against free public test APIs. Install it, open one, press Run.