One YAML file per request
Collections, folders and requests each live in their own small file, so diffs stay readable and merge conflicts stay rare.
Yamlet is a local-first API client for Git-friendly collections. Start one container,
open localhost:7878, and every request, folder and environment you touch is
saved as a readable YAML file in your own workspace folder.
Yamlet ships as a single container image. Mount the folder you want to keep your collections in, and the app reads and writes YAML there directly.
Run this from the directory that holds (or will hold) your collections. It is mounted at /workspace and bound to your machine only. The yamlet-data volume keeps private app state, such as the Chrome extension pairing, across updates.
$ docker run -d --pull always --name yamlet -p 127.0.0.1:7878:7878 -v .:/workspace -v yamlet-data:/data ghcr.io/piyushdoorwar/yamlet
Go to http://localhost:7878. Create a collection or import one you already have, then start sending requests. Use your browser's Install app option to give Yamlet its own window.
Everything lands in collections/, environments/ and globals/ as plain YAML. Review it, diff it, branch it and merge it like the rest of your code.
Remove the container and run the same command again; --pull always fetches the newest image. Your YAML lives in your folder, and keeping the same yamlet-data volume keeps the Chrome extension paired.
$ docker rm -f yamlet
$ docker run -d --pull always --name yamlet -p 127.0.0.1:7878:7878 -v .:/workspace -v yamlet-data:/data ghcr.io/piyushdoorwar/yamlet
Inside the container, localhost is the container itself. Reach your machine in one of two ways:
A full request workflow in the browser, with nothing hidden in a database or a hosted account.
Collections, folders and requests each live in their own small file, so diffs stay readable and merge conflicts stay rare.
Request, collection, environment and global scopes. {{variables}} are highlighted inline; hover to peek a value, click to edit it.
Fresh test data on every send with {{$guid}}, {{$timestamp}}, {{$randomEmail}} and many more, with autocomplete as you type.
Pre-request and post-response JavaScript at request and collection level, with a pm API for variables, requests and pm.test assertions.
Bearer, Basic, Digest, API key, cookie and AWS Signature v4 auth, plus OAuth 2.0 client credentials, password, authorization code with PKCE and implicit. Inherit it from a folder or the collection.
Every method including the new QUERY, or any custom verb. JSON, XML and text, multipart form-data with file fields, URL-encoded forms, GraphQL and binary uploads.
Run a collection or folder in order, repeat it for several iterations and feed it rows from a CSV or JSON data file.
Import cURL commands, OpenAPI and Swagger specs, and v2.1 collection JSON exports. They are converted to Yamlet YAML on save.
Turn any request into ready-to-paste code for cURL, JavaScript, Python, Go, C#, Java and other languages.
See, edit and clear the cookies your requests collect, per domain, without leaving the app. The optional Yamlet Interceptor Chrome extension syncs cookies from sites you approve.
Save responses as examples next to the request, and revisit what you sent earlier from the request history.
Work across many requests in tabs that come back when you return, and keep your hands on the keyboard with shortcuts, including Ctrl+K to jump to any request.
The free Yamlet Interceptor extension syncs cookies from the sites you approve into the Yamlet running on your computer. Pair it in one click from Yamlet's Cookies dialog.
No export step and no sync service. The files Yamlet writes are the source of truth, so code review works on API changes the same way it works on code.
collections/
JSONPlaceholder/
.resources/definition.yaml
Posts/
.resources/definition.yaml
List Posts.request.yaml
Create Post.request.yaml
Users/
environments/
dev.environment.yaml
globals/
workspace.globals.yaml
$kind: http-request url: "{{baseUrl}}/posts" method: POST headers: - key: Content-Type value: application/json body: type: json content: | { "title": "Hello from Yamlet", "email": "{{$randomEmail}}" } scripts: - type: afterResponse code: | pm.test('created', () => pm.response.to.have.status(201)); language: text/javascript order: 3000
The yamlet CLI (@piyushdoorwar/yamlet on npm) runs a workspace headlessly: every request, every
script, every pm.test. It prints a results table and exits with code
1 if anything fails.
$ npm install -g @piyushdoorwar/yamlet
$ yamlet run ./my-workspace --env dev
# or without installing
$ npx @piyushdoorwar/yamlet run ./my-workspace --reporter junit
--env dev--bail--iterations 5--data users.csv--reporter junit
Yamlet workspace ./my-workspace env dev ┌──────┬────────┬─────────────────────┬────────┬───────┐ │ │ Status │ Request │ Time │ Tests │ ├──────┼────────┼─────────────────────┼────────┼───────┤ │ PASS │ 200 │ GET /posts │ 84 ms │ 2/2 │ │ PASS │ 200 │ GET /posts/1 │ 61 ms │ 2/2 │ │ PASS │ 201 │ POST /posts │ 142 ms │ 2/2 │ │ FAIL │ 404 │ GET /users/99 │ 57 ms │ 0/1 │ └──────┴────────┴─────────────────────┴────────┴───────┘ 1 failed, 3 passed · 7 of 8 tests · 344 ms exit code 1
Free and open source. Runs on any machine with Docker.