WebPipe Triggers and Zapier's Rest Hooks

[Matthew Hudson]

This is looking, in part, like a solved problem:

• http://resthooks.org/
  
• https://zapier.com/developer/reference/#rest-hooks

Leasing/Renewing is definitely still a problem. But if there's already solid work we should try to move more towards Zapier's direction if we can and build on top of their proposal.

[Jeff Lindsay]

They're defining a loose framework for subscribe/unsubscribe with restful endpoints. HTTP Subscriptions can be made to be compatible with this, but what I don't like is making WebPipes a REST API. A trigger or action should just be a single endpoint. :\

--
You received this message because you are subscribed to the Google Groups "webpipes" group.
To unsubscribe from this group and stop receiving emails from it, send an email to webpipes+u...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

--
Jeff Lindsay
http://progrium.com

[Tom Robinson]

I haven't looked at it closely, but it sounds like they're just using a REST API to manage the webhook subscriptions:

    REST Hooks itself is not a specification, it is a collection of patterns that

    treat webhooks like subscriptions. These subscriptions are manipulated via a

    REST API just like any other resource. That's it. Really.