This content has been marked as final. Show 8 replies
webhooks currently does not support changing the request headers. All webhooks call-outs are done as form POST
The Drop down that you are using is for response parsing. i.e. parse the response as JSON/XML and then use it to map values to lead fields.
We plan to allow custom headers in the June release and this will enable you to change the mime-type
Thanks for the reply.
So to be sure - what you are saying is that the "Request Token Encoding" does not work?
not quite - token encoding is handled properly, but mime-type is not set to match the request template.
@Raj Thanks for the responses. May I check on the status of this? For my POST webhooks Marketo always seems to set the content-type header to "application/x-www-form-urlencoded", even when posting json.
But third party site requires it to be set to "application/json" when POSTing json.I don't see any way to set custom headers. Changing "Response type" doesn't seem to do it.
Thank you Raj! I never would have found that; I was looking in the "Edit webhook" dialog.
Now working. Incidentally, the third party I am using returns status code 201 ("CREATED") which is perfectly legitimate. Marketo sees this as an error. It probably shouldn't. Anyway, the data get across so I can now start to see what I can make with this!
We will fix the webhook infrastructure to treat all 2xx responses as success in a near future release.