thanks for your question! Currently, web hook receive URL endpoints will always return a 200 (during normal operations) with an empty response. At the moment, there is no way to customize the response or add extra logic there.
As always, feel free to create a feature request for that, including the info whether you would need to customize the response in a static fashion (e.g. always return this body XY) or in a dynamic fashion (fetch data, execute logic, yield a response body with the result).
I will think about the feature request I think it’s the only system I have seen yet that demands a response other than the ‘200’ so whilst it stops the integration I was building it is probably an edge case and I expect I can switch the other system out if need be.
Honestly I can’t actually remember what service I was trying to connect to but it wasn’t the one you mention. There are a few that need it though.
It’s not really a solution but the way I get round it these days is just make a little (Cloudflare) worker to sit in the middle, I do that to handle files when the service doesn’t send or receive in a way that works with Tape nicely.