Invoke-WebRequest failed - "Problems parsing json" with GitHub api

Question

I am attempting to communicate with the Graphql api through powershell. According to Github, one must first do the following curl call.

curl -H "Authorization: bearer token" -X POST -d " \
 { \
   \"query\": \"query { viewer { login }}\" \
 } \
" https://api.github.com/graphql

Using GitHub Enterprise, on powershell I do the following calls:

$url = "http://github.company.com/api/graphql" # note that it's http, not https

$body = "`"query`":`"query { viewer { login }}`""                                               #`

$headers = New-Object "System.Collections.Generic.Dictionary[[String],[String]]"

$headers.Add("content-type","application/json")

$headers.Add("Authorization","bearer myTokenNumber")

$response = Invoke-WebRequest -Uri $url -Method POST -Body $body -Headers $headers

I keep getting the same error message, that there are problems parsing JSON.

I assume the error is with the body tag, but I can't see how.

echo $body gives "query":"query { viewer { login }}"

What is the issue here?

Exact error message:

Invoke-WebRequest : {"message":"Problems parsing JSON","documentation_url":"https://developer.github.com/v3"}
At line:1 char:13
+ $response = Invoke-WebRequest -Uri $url -Method POST -Body $body -Headers $heade ...
+             ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : InvalidOperation: (System.Net.HttpWebRequest:HttpWebRequest) [Invoke-WebRequest], WebExc
   eption
    + FullyQualifiedErrorId : WebCmdletWebResponseException,Microsoft.PowerShell.Commands.InvokeWebRequestCommand

Have you tested your token and Query in GitHub's GraphQL Explorer Interface ? — Daniel
– Daniel, Commented Feb 8, 2018 at 23:13

mklement0 · Accepted Answer · 2018-02-09 00:02:24Z

4

Your $body value is malformed JSON, because it is missing the enclosing { ... }.

Using a here-string makes the construction of the JSON string easier:

$body = @'
{ "query": "query { viewer { login } }" }
'@

Similarly, you can simplify building the headers with a hashtable literal:

$headers = @{
  "content-type" = "application/json"
  "Authorization" = "bearer myTokenNumber"
}

answered Feb 9, 2018 at 0:02

mklement0

452k68 gold badges727 silver badges986 bronze badges

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

Comments

K Split X · Accepted Answer · 2018-02-09 00:12:50Z

4

Here is the working program. Thanks to those who answered:

$url = "https://api.github.com/graphql" # regular github
# for enterprise it will be http(s)://[hostname]/api/graphql where hostname is 
# usually github.company.com ... try with both http and https

$body = @'
{ "query": "query { viewer { login } }" }
'@

$headers = @{
  "content-type" = "application/json"
  "Authorization" = "bearer tokenCode"
}

$response = Invoke-WebRequest -Uri $url -Method POST -Body $body -Headers $headers
Write-Host $response

Output: {"data":{"viewer":{"login":"yourGithubUsername"}}}

answered Feb 9, 2018 at 0:12

K Split X

5,0777 gold badges28 silver badges57 bronze badges

Collectives™ on Stack Overflow

Invoke-WebRequest failed - "Problems parsing json" with GitHub api

2 Answers 2

Comments

Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

2 Answers 2

Comments

Comments

Your Answer

Sign up or log in

Post as a guest

Related