A local space for your APIsOpen source. Still taking shape.

Make senseof everyrequest.

From the first HTTP call to the shape of an API.
A focused workbench, right on your machine.

Start building locally Take a look inside

Local storage

OpenAPI 3.1 export

JSON you can version

Explore the workbench

The workbench

Less between you
and the response.

Compose a request. Inspect the answer.
Keep your collections close.
No account needed to begin.

PacketLarkLocal workspace

GEThttps://api.example.com/v1/profile

ResponseJSONSample response

{
  "name": "Alex Morgan",
  "role": "Developer",
  "workspace": {
    "name": "A good place to build",
    "local": true
  },
  "ready": true
}

Try the preview: switch requests and press Send. Sample data stays in this page.Open your local studio

Make the call.

HTTP methods, query parameters, headers, request bodies, and everyday authentication.

Check your assumptions.

Pre-request JavaScript and response assertions, with a familiar subset of the pm API.

Keep the context.

Collections and environments in readable local JSON. Import Postman collections or cURL.

Traffic to spec

Real traffic.
A clearer picture.

Working with an undocumented HTTP API? Forward calls through the local proxy and turn the responses you observe into something you can build on.

Try it with your API

Capture a conversation

Forward HTTP requests through port 8085.

Find the shape

Infer JSON schemas and recognize common IDs.

Take it into your project

Export OpenAPI 3.1 or a TypeScript client draft.

A starting point, shaped by what you capture. Review generated schemas and code before use. HTTPS CONNECT interception is not supported.

Your APIs.
Your machine.
Your pace.

Good tools give you room to think.

PacketLark is an independent, open-source side project for developers who want a small, understandable HTTP workspace. It stores its workspace locally and doesn't require a PacketLark account.

It’s early. It doesn’t replace Postman’s collaboration, protocol coverage, or automation platform. If a focused local workflow fits you, there’s something useful here.

Explore the source

Build something

A fresh workspace.
On familiar ground.

Node.js 22 or newer. A terminal. Your next idea.

Open local studio

Start on your machine

git clone https://github.com/abrar225/packetlark.git
cd packetlark
npm ci
npm run build
npm start

Then open localhost:4040 →

A few things to know.

Is PacketLark a replacement for Postman?

For basic local HTTP requests, collections, and scripts, it may fit. For OAuth flows, gRPC, WebSockets, team collaboration, monitors, mock servers, or mature CI workflows, use a tool with those capabilities. PacketLark’s most interesting workflow is capturing HTTP traffic and inferring a spec.

Does the studio work without the internet?

The interface, fonts, icons, and workspace run locally after installation. Calling a remote API still requires a network connection. Collections and environment values are plain files, so keep credentials out of Git and only run scripts you trust.

What does the traffic proxy capture?

HTTP requests explicitly routed through it, including HTTPS targets using the /https://target path or X-Target-Url header. It doesn’t decrypt browser HTTPS CONNECT tunnels. Traffic is held in memory, capped at 500 records, and can contain sensitive data.

Can I contribute?

Yes. PacketLark is MIT licensed. Read the source, try it against your own API, and share an issue or a pull request on GitHub. Reliability, migration compatibility, and everyday usability are especially valuable contributions.