404s for any authed request on REST API #24765
-
When trying to GET a private repo (
Add a PAT (
As shown above, I get the same on just about any request (create repo, etc.) Anyone have a clue of what’s going on? |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments
-
Hi @pheel, Strange as it works for me. Are you trying to access your user owned private repository or organization owned private repository? You example text implies organization “ORG”. I only ask as the token scope (‘repo’) and user permissions are two different things. Can you access a public repository repository successfully using the same syntax? |
Beta Was this translation helpful? Give feedback.
-
I think I might have had the wrong PAT, because now it’s working 😅 . Marking your reply as solution, @byrneh. |
Beta Was this translation helpful? Give feedback.
Hi @pheel,
Strange as it works for me.
One thing I have found is many REST APIs responses will return a “Not Found”, rather than “does not have permission” for reasons of security/disclosure. So a “Not Found” root cause can be permission related, and community members have been confused by this when diagnosing problems.
Are you trying to access your user owned private repository or organization owned private repository? You example text implies organization “ORG”. I only ask as the token scope (‘repo’) and user permissions are two different things.
If its user permissions related a user owned repository you PAT I would expect to implicitly have access to its own user owned repositories wi…