Thank you for the feedback! In this case it's a bit complicated, as the document you linked is specific to our V1 API which does not have the same errors as our V2 API. This is a bit tricky to document for V2 as we opted to show the status codes on a per-endpoint basis rather than having a global table. In particular this code doesn't make a great deal of sense to document on every endpoint, as it only shows up when you've entered the URL incorrectly and are not calling a valid service that would contain a valid endpoint.
I'll chat with the team here and see if we can come up with a way to document this better!
... View more