HttpError: Not found

[henild]

I am trying to do something like this:

    const response = await octokit.request('GET /user/starred/{owner}/{repo}', {
        owner: "octocat",
        repo: "hello-world"
    })

but getting error

error: Uncaught (in promise) HttpError: Not Found
        const error = new RequestError(message, status, {
                      ^
    at https://cdn.skypack.dev/-/@octokit/[email protected]/dist=es2020/@octokit/request.js:65:23
    at async test.ts:18:22

Simple endpoints like /user/starred, /user are working fine. I tried with curl but it's not working there too. Is this a problem with github API?

[gr2m]

Turns out it's expected behavior, but I agree it's confusing.

See the docs

You can do the following

const isStarred = await octokit.request('GET /user/starred/{owner}/{repo}', {
    owner: "octocat",
    repo: "hello-world"
}).then(() => true, error => {
  if (error.status === 404) return false
  throw error
})

[gr2m]

instead of -u username:key, can you please try -H "Authorization: token [key]"

[henild]

Same result with that too.

[gr2m]

this request works for me:

curl \
  -X PUT \
  -H "Accept: application/vnd.github.v3+json" \
  -H "Authorization: token $GITHUB_TOKEN" \
  https://api.github.com/user/starred/octocat/hello-world

[henild]

Sigh... Turns out it was a permission issue. I had given only permission to Update all user data. And didn't think the public repository require to enable that permission manually(this is really confusing).

The top section of the permission says Full control of private repositories but it contains Access public repositories. If you can please forward this to the API team about the confusion.

[gr2m]

The response headers provide a clue. Not always, but for many API endpoints you see these two headers:

X-OAuth-Scopes: user
X-Accepted-OAuth-Scopes: public_repo, repo

The X-OAuth-Scopes response headers tells you which scopes your token has, X-Accepted-OAuth-Scopes tells you a list of scopes, one of which is required depending on the use case.

You are not the first to be confused by the 404 errors. Maybe we should log a more helpful message pointing out that the scopes are not sufficient for the request.