Describe the bug

When running gh api /user/emails I receive an HTTP 404 error despite being logged in (checked with gh auth status) If I first create a personal token on github.com and then run
gh api user/emails -H "Authorization: token <myusertoken>" I get the information I need.

Steps to reproduce the behavior

1. run gh api /user/emails and get HTTP 404 error.

Expected vs actual behavior

gh api /user/emails should ideally return the same as the longer custom header command. Is it not possible to retrieve the user/email information via a standard SSH gh auth login?