just to complement my own comment with a solution. It seems we can do this but a bit in reverse: we copy/paste our 1st webhook as many times as needed (once for each path), and configure all the paths we need for our api. Best explanation I found is a video from n8n team: n8n - ▶️ webhookDemo | Loom.
I found this vid on another thread: Webhook - Enhanced with dynamic elements in path RESTful API approach [GOT CREATED] - #7 by David . Which points to a pull request: ✨ Webhook route parameters by BHesseldieck · Pull Request #1343 · n8n-io/n8n · GitHub. Which in turn points to the loom.
So, although the node does not support routing directly, we can achieve this by using multiple copies of our first webhook (so that the node id is fixed) and changing the path to whatever we need.