ApiQuest UI

A local-first API tool for developers and QA. Send requests, run collections, inspect results, and extend the app with plugins — all on your machine.

Download ApiQuest

Documentation GitHub

CLI Runner · CI/CD · QA

Fracture

Headless collection runner for CI/CD and QA. Validate deployments, run regression suites after each release — same schema and assertions you built in the UI.

npm install -g fracture

Documentation GitHub npm

ApiQuest UI in action

Fast request editing, collection runs, and real-time execution feedback — all local.

ApiQuest request editor with POST body and response viewer

Request editor — body, headers, params, auth, scripts. Response inline with status and test results.

ApiQuest collection runner with configuration panel

Collection runner — select requests, configure iterations, data file, delay, parallel execution.

Built by developers, for developers

Every decision was made to stay out of your way and out of the cloud.

Local only. Always.

Collections are JSON files on disk. Nothing is uploaded, nothing is tracked. Your API data stays yours.

Git-native collaboration

Share collections the same way you share code — pull requests, branches, diffs. No proprietary cloud required.

Plugin-driven architecture

HTTP, GraphQL, SSE, Vault integration — each is a first-class plugin. Swap or extend the runtime without touching core.

Collection runner

Configurable iterations, CSV/JSON data files, delays, assertions, and parallel execution. Repeatable and deterministic.

Fracture for CI/CD & QA

Validate deployments, run regression suites, and gate releases automatically. Same collections your QA team built in the UI — no rewrites.

Private by default

Vault-backed variables, local environments, no telemetry. Security is the baseline — not a paid tier.

Fracture CLI

Run the same collections you build in ApiQuest UI directly from your terminal or CI pipeline. No configuration drift, no surprises.

Schema-validated collection format shared with the desktopDeterministic, order-preserving executionGate releases — fail CI when API assertions failQA regression suites — same collections, automated runsStructured JSON output for machine parsing and reporting

Fracture documentation

$ fracture run ./collections/basic-api-test.apiquest.json

============================================================
  Fracture v1.0.6
  Collection: Basic API Test Collection
============================================================

Expected tests: 9

> Get Single Post
  GET https://jsonplaceholder.apiquest.net/posts/1
  < 200 OK (166ms)
  [PASS] Status is 200-3
  [PASS] Response has userId
  [PASS] Response has title

> Get All Posts
  GET https://jsonplaceholder.apiquest.net/posts
  < 200 OK (17ms)
  [PASS] Status is 200-2
  [PASS] Response is array
  [PASS] Has multiple posts
  [PASS] Each post has required fields

> Create New Post
  POST https://jsonplaceholder.apiquest.net/posts
  < 201 Created (52ms)
  [PASS] Status is 201-1
  [PASS] Response contains created post

------------------------------------------------------------

RESULTS:
  Collection: Basic API Test Collection
  Duration: 0.35s
  Requests: 3  (Successful: 3)
  Tests:    9  (Passed: 9)

[PASS] Collection run completed successfully

Your APIs. Your machine. Your rules.

Free. Open source. No account required.

Download ApiQuest