We have identified the issue and just fixed it in production and will continue to monitor our API's for errors.

An incident occurred where some api calls to the v1/users/ endpoint were returning 500 errors. We are investigating this issue.