Today I use ngrok for this and it works brilliantly:<p><pre><code> $ ngrok http https://myapp
</code></pre>
and then I can point my clients at <random domain>.ngrok.io and inspect the request contents locally. How does this compare to that?
"Hosted on AWS" is gonna backfire on you. This basically opens you up to people misusing it to drive traffic costs for you and you end up paying a lot of money for it.<p>Better to find a host where you're not paying for traffic and you can have a dedicated host.
If you're looking to be more professional with less work, I would suggest using <a href="https://tailwindcss.com/" rel="nofollow">https://tailwindcss.com/</a> to spruce up the overall look!
Site is nice btw, will use in the future.
For client debugging I usually just use the network inspector or Charles (<a href="https://www.charlesproxy.com/" rel="nofollow">https://www.charlesproxy.com/</a>). But I guess this might be useful for server to server API call debugging
I've been frustrated with building API integrations and struggling to track down API call issues via Postman, e.g. what does a raw request really look like or where are my headers ending up. Interested to see if anyone finds this useful.