It's 11pm. Production is returning 502s on one endpoint and only one, and the person who noticed is asking you to confirm whether it's still happening.
You are not at your laptop.
This sounds like a small problem. It isn't, because every option you have at 11pm is bad in a different way.
Termux and curl. Works fine. Becomes miserable the moment you need an auth header, a request body, or the same environment variables you used yesterday.
Wait until morning. Correct, and completely useless to the person currently waiting on you.
A cloud request tunnel. Sends production traffic and its auth headers through a third party's logs. I've done it. I don't love it.
A public API playground. Requires pasting an internal URL and a bearer token into someone else's website. I don't think any of us should do this, and the number of people who do it regularly is not the number who should.
So I built the option I kept wishing for: a real API client that runs on the phone in my hand.
What it does
It's called Taho.β¦