Webhooks payload in JSON instead of multipart
It'd be nice to have the payload of webhooks POSTs to be encoded in JSON instead of multipart or form encoding.
Sebastián Magrí
shared this idea
Howdy all,
Thanks for your feedback and support! With the release of our Webhooks 2.0, the payload is now in JSON, and they follow our Event API schema. I’ve tested them out with Keen.io, and it does indeed work. Feel free to check out our webhooks documentation here: https://documentation.mailgun.com/en/latest/api-webhooks.html
-
Robert Anstett
commented
I build a lot of systems that interface with email sending providers. I like many of the features of MailGun, except for the lack of JSON support when sending a message to the API. Implementing MailGun in an application is more time consuming than other large name email providers, simply because of the lack of JSON support.
-
Glen Bizeau
commented
It'd be nice to have the payload of routes POSTs to be encoded in JSON instead of multipart or form encoding. Or even better, have the ability to choose
-
Hagen
commented
Agreed. This is really frustrating from a 'getting started' standpoint. Not to mention that two different form encodings are used, depending on the webhook - both application/x-www-form-urlencoded and multipart/form-data are used. Mailgun should take care of prepping this into JSON, and send that in the webhook payload.
Of course, once your code is in and you're correctly handling the webhooks, life's peachy, but we spent more time than we *should have* trying to work with Mailgun webhooks.
-
Elliot Taylor
commented
I am unable to integrate with keen.io or zapier because of this. Is there any chance this can be integrated as currently limiting my use.
This is the error received:
api.keen.io returned (400) Bad Request and said "The content-type of the request must be 'application/json'."