It is absolutely needed@David as it is possible for anyone to spam my webhook and corrupts my data, which could be very painful to eliminate.
Indeed, is it not that hard to find the endpoint as it has often a basic structure (webhook/pipedrive or webhooks/pipedrive), and after that you can easily spam and corrupts other people’s data.
Mailgun does the same and I am pretty sure that it is not hard to implement on your side and it is still non-mandatory for users to verify webhooks.
This would be nice. However what if you just obfuscate your endpoint. Of course I know “obscurity is not security” but that’s a good temporary alternative. Most spam bots will just hit the domain and any publically availible pages inside the robots.txt or sitemap.xml. I haven’t seen many bots target pipedrive webhook endpoint urls.
You can add a random ?somevar=somehash (check that hash against the variable in your request) that makes it almost impossible for a bot to guess unless your URLs get leaked somehow, which is even worse.