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

✨ New Version Highlights

🧨 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

Run anytime:

404ping run myapp:login

Override & save:

404ping run myapp:login -u https://staging.api.com/login --save

🧬 Variable System: global + collection

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

Scoped:

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

📁 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

🎯 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

🔐 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

🤝 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.

💡 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

🔥 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