Test API

What’s New in 2.0

• Postman collection import & export — drag a .json file in, tweak a few calls, drag it back out. Zero context-switching.

• Environment variables — drop {{baseUrl}}, {{token}}, and friends into any field, and keep your requests portable.

• Auto dark-mode — the UI now respects your browser or OS theme, so midnight debugging doesn’t blind you.

• UI <> cURL — every change you make in UI reflects immediately in the cURL equivalent. And vice versa: paste the cURL command and see the UI version instantly!

• All-new, modern UI — the popup got a complete redesign: cleaner layout, snappier interactions to keep you moving fast.

Feedback That Shaped 2.0

A handful of brave early adopters pinged me with “It’s cool, but could it…?” emails. Big shout-out to everyone who:

• Asked for dark mode (my retinas thank you),

• Sent gif-powered bug reports, and

• Politely reminded me that “variables are table stakes these days.”

Your ideas went straight into the codebase!

What’s Cooking for 2.1?

I’m hammering away at an update that turns a Chrome limitation into a feature I haven’t seen anywhere else.
Can’t spill all the beans yet, but imagine a per-site API test helper baked right into the extension.
Stay tuned!

What's New in 2.1

• Chrome local variables & environments: the game-changer you didn't know you needed.
  Store auth tokens, chain API calls, and switch between dev/staging/prod environments seamlessly.
  It's like having Postman's variable system, but native to Chrome.

• Request chaining made simple: authenticate once, use the token in the next call, and then grab the user ID for the third request. No more manual copy-pasting between API calls.

• Environment isolation: keep your production tokens away from development. Each environment gets its own variable scope, because nobody wants to nuke production data accidentally.

Feedback That Shaped 2.1

Funny story: users kept asking for "Chrome local storage support."
I almost built exactly that until I realized what they really wanted was smooth request chaining.

Sometimes the best features come from reading between the lines of user feedback.
Shout-out to everyone who:

• Described their API testing pain points in detail.

• Shared workflows from other tools they missed.

• Helped me connect the dots between storage and chaining.

Your "wouldn't it be cool if..." messages literally shaped this release!

What's Cooking Next?

Several users have been asking for some significant UI changes, and honestly, they're right.
The current setup works, but what if it didn't have to live where it currently lives?

I'm working on something that breaks free from the usual constraints.
Think less "confined to one spot" and more "work however feels natural."

Can't spill the details yet, but let's just say your API testing might soon have a lot more breathing room.
The boundaries you're used to?
They're about to get very, very flexible.

Stay tuned! 🚀