Github API Create Issues return 404 Not found

Question

I am making a request to the below URL- Post https://api.github.com/repos/kvimal/2048/issues With my Token as a header for authorization.

The Curl Request

curl -i -X POST https://api.github.com/repos/kvimal/2048/issues  -d "{title:'hey'}" -H "Authorization: Bearer xxxxxxxxxxxxxxxxxx" -H "Content-Type: application/json"

And GitHub sends a response 404 Not found. I have reade the Documentation and as far as i have observed i am doing it by the github standards. Can anyone Help with this issues?

Please post your code for us to help with. If you are getting 404 errors, you are trying to access a URL that doesn't exist. — Martijn Pieters
– Martijn Pieters, Commented Mar 9, 2015 at 7:30
The above mentioned Url is the one i am trying to make a request to. — Vimal
– Vimal, Commented Mar 9, 2015 at 7:32
But the above URL doesn't return a 404. It works just fine. Your code obviously doesn't, so please share it. — Martijn Pieters
– Martijn Pieters, Commented Mar 9, 2015 at 7:33
may not be actual answer but this may help someone.. in my case the issue was permission to the access token key created in git. I granted write package to key and it worked fine. Before that the error was 404 resource/file was not found at location.. (mostly due to security) (I wanted to add it as comment but not yet it seems) — granthik
– granthik, Commented Nov 10, 2020 at 14:34

VonC · Accepted Answer · 2015-03-09 07:43:55Z

11

As illustrated in this python script, the header should be using 'token' not Bearer'

headers = {
  'Content-Type':'application/json',
  'Authorization': 'token %s' % token,
}

(That script doesn't use curl, but give an idea of the header)

For curl queries, see this curl POST tutorial:

curl -H "Authorization: token OAUTH-TOKEN"

And the POST message must be complete as well (as in this python script)

issue = {'title': title,
         'body': body,
         'assignee': assignee,
         'milestone': milestone,
         'labels': labels}
# Add the issue to our repository
r = session.post(url, json=issue)

(again, not curl, but gives you an example of the body)

edited Mar 9, 2015 at 7:43

answered Mar 9, 2015 at 7:40

VonC

1.4m569 gold badges4.8k silver badges5.7k bronze badges

Sign up to request clarification or add additional context in comments.

6 Comments

Martijn Pieters Over a year ago

Ah, indeed, see this section in the documentation; the API responds with 404 Not Found to not reveal private repositories.

VonC Over a year ago

@MartijnPieters I agree, but github.com/kvimal/2048 is a public repo, is it not?

Martijn Pieters Over a year ago

A direct unauthenticated GET request certainly works, but for consistency the API may still use 404 to respond to invalidly authenticated requests.

VonC Over a year ago

@MartijnPieters that I understand, which is why I was pointing out the strange content of the header Authorization: Bearer.

Martijn Pieters Over a year ago

Github is probably first trying to parse the Authorization header for the token xxxx form, and if that fails, falls back to expecting Authorization: Basic. If the latter fails then a 404 is returned.

|

Beeno Tung · Accepted Answer · 2021-05-16 19:14:02Z

11

Go to "Edit personal access token" page, checkout the "Select scopes" session.

Make sure the token has been granted required access right.

I encountered similar case when trying to create public repo with 'Authorization: token ...' header.

answered May 16, 2021 at 19:14

Beeno Tung

1,29012 silver badges18 bronze badges

2 Comments

1owk3y Over a year ago

This was issue for me. Shoutouts to GitHub for not adding any 'you lack permission' text in the response, sending us on this wild goose chase in the first place...

Hunger Over a year ago

Thank you. It works after I add public_repo permission.

Jesse L. Greenough · Accepted Answer · 2023-03-17 11:33:18Z

1

I want to scream so bad right now!

If you leave an extra slash at the end of the graphql url then you will get a 404 error.

https://api.github.com/graphql is safe

https://api.github.com/graphql/ is a 404 error with no details.

I have spent the last 2 hours knowing my token or headers or query wasn't wrong and I was right! That little slash of hell will end you....

answered Mar 17, 2023 at 11:33

Jesse L. Greenough

751 silver badge7 bronze badges

Collectives™ on Stack Overflow

Github API Create Issues return 404 Not found

3 Answers 3

6 Comments

2 Comments

Comments

Your Answer

Linked

Hot Network Questions

Collectives™ on Stack Overflow

3 Answers 3

6 Comments

2 Comments

Comments

Your Answer

Sign up or log in

Post as a guest

Linked

Related