This is a bad error from the API (IMO it’s a bug)
It returns 401 if it can’t find the route you are specifying. In this case I believe the trailing slash could be the problem. They recently stopped sanitizing URLs, specifically slashes, double slashes, etc.
Just a hunch, but I would try without the trailing slash and see if you get a proper response.
Cheers,
Adam