To add this this:
404 is “route not found”, it’s not documented as it’s “standard across the whole API and only occurs if incorrectly calling the API. It’s not a valid HTTP response code when calling correctly”.
Either using the wrong HTTP Verb, or a typo, or something isn’t calling what you think it’s calling. Network tools for the browser in JS will help debug what and how you are actually calling.
A token problem would be a 403.
404 - route it’s just not there, generally user error.
403 - a token problem
400 - input error (you got words in your id generally)
200 - got data, it may or may not contain users
If everything is correct, there could be an issue based on region if fast.ly is being dumb, often a problem for south american users. You can debug this from making your call via another region such as your production server in a different region