Comments on: Queue Webhook Events with IronMQ Webhook Support

By: matt

matt — Thu, 17 Jan 2013 01:44:07 +0000

Excellent – that would be the only thing blocking me from using it today, personally, as that Shopify example is a real use case for me – I need the headers they send to process their webhooks correctly – I’d love more than anything to ditch the current solution for handling this in favor of IronMQ – if the receiver is down and the webhook fails they don’t give you much help when tracking down the problem.

By: Travis Reeder

Travis Reeder — Wed, 16 Jan 2013 18:47:33 +0000

Hi Matt, not currently, we only capture the body right now. Capturing headers is probably a good idea though, I've added it to our list to review. Thanks!

By: matt

matt — Wed, 16 Jan 2013 18:06:39 +0000

Is there any way to access the HTTP headers that were included in the POST? For instance Shopify includes information in the headers with their webhooks (https://wiki.shopify.com/WebHook#Headers) – might be handy to get at that data in a lot of cases.

By: Travis Reeder

Travis Reeder — Thu, 03 Jan 2013 00:11:57 +0000

Hi Paul, not currently, but we will be coming out with more find grained authentication in the near future.

By: paul.querna

paul.querna — Wed, 02 Jan 2013 23:56:47 +0000

Is it possible to have a restricted use OAUTH token that can only be used to insert into a queue?