By default, a webhook generates a non caching JSON API 'ok’ response in the success case. Cache age can be overridden and small (< 16k binary) content can be served directly via the webhook in response to an invocation. For other cases, you may specify a redirect as a URL or a URI template and handle the presentation of the webhook response at another HTTPS endpoint. Note that the URI template is expanded in the context of the original URI match, not the equivalent JSON document and as a result the URI template does not have access to server data.
Currently, error messages are not customisable.
Note that caching values, if specified, are meaningful for HTTP GET webhooks as they may dramatically change the behaviour of requests and webhook invocations.
Updated less than a minute ago