Enterprise administration APIs call returns 404 #55120
Replies: 1 comment
-
|
404 really makes me confused. The root cause is the token scope doesn't contain sufficient persmission |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Select Topic Area
Question
Body
Hello,
I deployed the Github enterprise 3.6 on AWS. Everything looks good except the enterprise administration API calls.
github admin api doc
curl --location --request POST 'https://github.example.com/api/v3/admin/users' \ --header 'Accept: application/vnd.github+json' \ --header 'Authorization: Bearer gho_JJN9Bk7jc1aJxxxxxxxxxxxxxxxxxxxx' \ --header 'Content-Type: application/json' \ --data-raw '{"login": "postman", "email": "postman@example.com"}'It always returns 404
{ "message": "Not Found", "documentation_url": "https://docs.github.com/enterprise/3.6/rest" }The token is from a site admin. And I have verified it with other non-admin APIs. I also tried out the other APIs under enterprise administration. They don't work with 404 error.
How to make these admin APIs available?
Beta Was this translation helpful? Give feedback.
All reactions