DEV Community

Cover image for 404ping v2 β€” The API Testing CLI That Went From Side-Project to Beast Mode πŸ’₯
Nimesh Thakur
Nimesh Thakur

Posted on

404ping v2 β€” The API Testing CLI That Went From Side-Project to Beast Mode πŸ’₯

curl + Postman + brain = 404ping

When I built 404ping v0.0.1, it was a tiny experiment.
I just wanted a simple CLI tool that let me test APIs quickly β€” without opening Postman or remembering curl flags.

That first version could only:

  • Send simple HTTP requests
  • Store a few variables
  • Handle basic collections

That’s it.
But the response from developers and bug hunters was insane β€” people loved the speed & simplicity.
So I went back to the lab. And now, after countless commits, refactors, and caffeine, 404ping v2 is here.

And it’s not an upgrade…
It’s a transformation.


πŸš€ Introducing 404ping v2

Lightweight API Testing CLI β€” curl with a brain 🧠

No GUI. No accounts. No cloud sync.
Just pure, fast, developer-focused power.

npm install
npm run build
404ping request https://api.example.com
Enter fullscreen mode Exit fullscreen mode

✨ New Version Highlights

Feature curl Postman 404ping
Lightweight CLI βœ… ❌ βœ…
GUI Required ❌ βœ… ❌
Variables ❌ βœ… βœ… (global & scoped)
Collections ❌ βœ… βœ… (CLI-based)
Save & reuse requests ❌ βœ… βœ…
TLS / SSL inspection ⚠️ βœ… βœ…
Debug connection / TLS / timing ❌ ⚠️ βœ…
Output modes ⚠️ ⚠️ πŸ”₯
Secure by default ⚠️ ⚠️ πŸ”

🧨 What’s New in v2 (Massive Upgrade)

πŸ”„ Smart Saved Requests

Save requests with just one flag:

404ping request {{host}}/api/login -X POST \
-d '{"email":"{{email}}"}' \
--save myapp.login
Enter fullscreen mode Exit fullscreen mode

Run anytime:

404ping run myapp:login
Enter fullscreen mode Exit fullscreen mode

Override & save:

404ping run myapp:login -u https://staging.api.com/login --save
Enter fullscreen mode Exit fullscreen mode

🧬 Variable System: global + collection

404ping set host:https://api.myapp.com token:abc123
404ping request {{host}}/users/me -H "Authorization: Bearer {{token}}"
Enter fullscreen mode Exit fullscreen mode

Scoped:

404ping set myapp.token:xyz myapp.host:https://api.myapp.com
404ping request {{myapp.host}}/users
Enter fullscreen mode Exit fullscreen mode

πŸ“ Collections β€” Project API management like Postman, but CLI

404ping collection create myapp
404ping collection save myapp login -X POST {{host}}/auth/login -d '{"email":"{{email}}"}'
404ping collection show myapp
Enter fullscreen mode Exit fullscreen mode

🎯 Advanced Output Modes

404ping request https://api.example.com --info        # Full analysis mode
404ping request https://api.example.com --connection # Network info
404ping request https://api.example.com --tls        # SSL certificate details
404ping request https://api.example.com --debug      # Everything
Enter fullscreen mode Exit fullscreen mode

πŸ” Security-focused

βœ” SSL verify by default
βœ” TLS breakdown
βœ” Input validation
βœ” Path traversal protection
βœ” Explains failure reasons


πŸ§ͺ Real-World Workflow Example

404ping set host:https://api.myapp.com token:abc123
404ping collection create myapp

404ping request {{host}}/auth/login -X POST \
-d '{"email":"dev@myapp.com","password":"hello"}' \
--save myapp.login

404ping run myapp:login --info
404ping set token:eyJhbGc...         # update token after login
404ping run myapp:profile --connection
Enter fullscreen mode Exit fullscreen mode

🀝 Why I Built It (Personal Note)

I created 404ping because:

➑ Postman is too heavy
➑ curl is too raw & hard to reuse
➑ I wanted something fast, scriptable, hacker-friendly

Now it has:

πŸ”₯ Collections
πŸ”₯ Variables
πŸ”₯ Saved requests
πŸ”₯ TLS inspecting
πŸ”₯ Debug view
πŸ”₯ Secure defaults
πŸ”₯ And zero GUI

This is my tribute to terminal developers who prefer typing over clicking.


πŸŽ₯ Demo (GIF placeholder)

Drag & drop GIF here once uploaded

πŸ”₯ Terminal demo showing saving & running requests


πŸ’‘ Who Should Use 404ping?

πŸ‘¨β€πŸ’» Backend developers
πŸ›‘ Bug bounty hunters
πŸ§ͺ QA testers
βš™ DevOps / CI pipelines
πŸ–₯ Terminal lovers
🌎 Anyone tired of Postman’s 600MB RAM usage


🧠 Future Roadmap

πŸ“¦ Export / Import Postman Collections
πŸ”— Request chaining (use previous responses)
πŸ“„ .env support
πŸ§ͺ Assertions for automated tests


πŸ“₯ Installation

git clone https://github.com/toklas495/404ping.git
cd 404ping
npm install
npm run build
Enter fullscreen mode Exit fullscreen mode

πŸ”₯ Final Words

From a small v0.0.1 idea
to a production-ready API testing CLIβ€”
404ping became something I am proud of.

If you’re tired of fighting Postman or writing curl novels,
give 404ping v2 a try.

⭐ Star it if you like it
πŸ›  Contribute ideas
🐞 Report issues
πŸ’¬ PRs welcome

πŸ‘‰ GitHub: github.com/toklas495/404ping


🎀 Call to action

If this tool helps you:

⭐ Give a star on GitHub
🎭 Share with dev friends
πŸ”§ Try your first collection today
Enter fullscreen mode Exit fullscreen mode

Want me to:

  • Add GIF demo script?
  • Create a thumbnail banner for dev.to?
  • Create example real API test repo?
  • Make a video tutorial outline?

Just tell me yes bro, and I’ll do it. πŸš€πŸ”₯


How do you want the dev.to title? Options:

A) 404ping v2 β€” The API Testing CLI That Makes Postman Cry
B) Introducing 404ping v2 β€” curl with a Brain
C) Goodbye Postman. Hello 404ping v2.
D) API Testing at Terminal Speed β€” Meet 404ping v2

Which one do you choose bro? πŸ˜„πŸ”₯

Top comments (1)

Collapse
 
toklas495 profile image
Nimesh Thakur

Let's together and make it......