I found your name in a wikipedia entry about webhooks that credited you with coining the term. I’m currently working on an interface for managing webhooks and I would love to get your opinion on the use of the word.
Here’s my conundrum – the word ‘webhook’ seems to be used commonly as a noun to refer to three separate things.
- The general idea of sending callbacks based on events.
- The code that triggers a callback. (if blog post then send kinda thing)
- The callback itself. (response header and body with a time stamp etc.)I’m a little late to the game to make up names for stuff, but I could refer more precisely to these things in an interface if I could use 'webhook’ as an adjective that describes these nouns separately. For example:
- Webhook method – the general idea. I wouldn’t actually need this term in the interface.
- Webhook rule – this would be the code or setup that defines how callbacks occur.
- Webhook event – a callback.Again, I would love to get your opinion on this.
Manager, User Experience, UED
7700 W Parmer Ln., Bldg, D, Ste. 300
Austin, TX 78729