Missing key in repo API response

I’ve been pondering over why my repo API call to one org is missing these keys


But it appears in another org. Both token have the same access to the corresponding org, both having enterprise licenses, under the same enterprise, but different SSO integration. Any idea what happened?

EDIT: FYI I’m using personal access token, and both the user are org admin

1 Like

I just figured out, the one with missing keys are called from org/repos, when I retrieve individual repo, I managed to get all the keys :slight_smile: