Have Json constructs as Webhook parameters in addition to URL parameters

[Grégoire_Miche2]

When defining a webhook, passing parameters can only be done with URL parameters (under the form of ?param=value).

Yet, some web services will rather use JSON as entries (such as SFDC APEX REST @httpPost ).

It would be really great if we also could set webhook call parameters as a JSON construct (in addition with the currently possible URL parameters).

-Greg

[SanfordWhiteman]

Greg, you can pass a JSON-formatted entity-body via Marketo webhooks already... we do it all day.

I guess what you mean is that Content-Type should be switchable to application/json.  I agree this would be nice (and upvoted), but if you control the webhook endpoint and the ep is only capable of parsing well-formed JSON anyway, you can ignore the C-T and validate the body as JSON.  Or you could duck-type the body: it's hard to imagine a body that would be simultaneously valid application/x-www-form-urlencoded ​and ​valid application/json.