3 ms·
I tend to use http://requestb.in/ http://requestb.in/ since it's a lot simpler to use. Basically press on the button in the middle, copy+paste url and then relo
by diggan 11y ago
I tend to use http://requestb.in/ http://requestb.in/ since it's a lot simpler to use. Basically press on the button in the middle, copy+paste url and then reload page once webhook is there.
Also, I created this nifty shorthand for use in the terminal:
alias bin_me="curl --silent -X POST http://requestb.in/api/v1/bins | jq -r '\"http://requestb.in/\(.name)?inspect\"'"
Requires JQ (could easily not require that) and you'll just remove the ?inspect when you want to use the bin.
- crabasa 11y agoRequestBin isn't a substitute for HttpBin, they do 2 completely different things: RequestBin = easily provision a url (useful for configuring a webhook) and inspect requests to that url. HttpBin = pre-defined urls that return specific responses (headers & payloads). Good for testing http clients. Fun fact: both tools are operated by the awesome people at http://Runscope.com http://Runscope.com.
- SnootyMonkey 11y agoSimilar to RequestBin is http://posthere.io/ http://posthere.io/ (Disclosure: I wrote it)
- billyhoffman 11y agoThis solves a problem that requestb.in does not. Namely, endpoints that predictably return various HTTP headers or HTTP content. This isn't about just testing to see what your app is sending. This is about testing how your application or HTTP client or whatever handles various weird HTTP responses and features. If I need to test how my application responds to a relative URL in a Location header, I can hit the /relative-redirect/:n endpoint. Same for Absolute urls via /absolute-redirect/:n. The If-Not-Modified stuff is also helpful.