And gives context such as being a supplement to Y and an alternative to Z. After reading every page, i still have no idea what it does, what its for and how i can learn more about Y and Z so i can understand why i need X.
`curl --data 'foo=bar&hello=there' http://hook.io/Marak/echo`
Gotta say I really like it, maybe put the example curl request much nearer the top in a big font size?
I took the curl example added it to the homepage right under the tagline.
Thinking of a Hook as a standard Unix Pipe really helps solidifying the entire concept.
... and tried to fork Node's EventEmitter into "EventEmitter2":
This time it's "HTTP Microservices", eh? Maybe next time it'll be even more incredibly powerful and surprisingly simple.
The hook.io domain actually expired and went to public auction recently and I was able to purchase it.
The only code that gets shared with the site is when a new gist is created. Never previous gists.
I'll investigate the Github API scope settings immediately and see if I can make the access level only public gist.
Thanks for the head-up.
Can I use this to transform Web Hook data from one service into a format that another service expects?
Service A WebHook -> hook.io -> Service B Rest Request
Edit: Would definitely need SSL support for the above use case.
Try taking a look at the transform or merge examples
You should check out our tools. We can help a lot with the storage/display of http requests.
Here is a live example of merging multiple hooks: http://hook.io/Marak/merge
and of using piping hooks together:
Adding HTTPS is now a top priority.