Getting html resp instead of json

[walmartwarlord]

Is it normal that I get html response instead of json? Trying to paste this in the console

curl --request POST \
  --url https://www.threads.net/api/graphql \
  --header 'user-agent: threads-client' \
  --header 'x-ig-app-id: 238260118697367' \
  --header 'content-type: application/x-www-form-urlencoded' \
  --data 'variables={"userID":"314216"}' \
  --data doc_id=23996318473300828

gives me HTML response. Am I missing something? I already changed userID and doc_id etc but no luck

[jjhb94]

Look at the readme for the content type response. You want a header with a "header('Content-Type: application/json');" typically. In this case the response will ignore it since it doesn't know what you really want to do with json, and so the default returned will be html. Whenever you request json you typically need to then parse the object (call json.parse in code and pass in the object returned as a a parameter ). Otherwise you'll keep getting an html object

[surya-prakash-giri]

@walmartwarlord, I was also facing the same issue, you can resolve it by providing the correct headers and request payload.

curl --location 'https://www.threads.net/api/graphql'
--header 'X-Fb-Friendly-Name: BarcelonaProfileRootQuery'
--header 'Origin: https://www.threads.net'
--header 'Content-Type: application/x-www-form-urlencoded'
--header 'X-Asbd-Id: 129477'
--header 'X-Fb-Lsd: api-token'
--header 'X-Ig-App-Id: 238260118697367'
--data-urlencode 'variables={"userID":"314216"}'
--data-urlencode 'doc_id=9943275619045977'
--data-urlencode 'lsd=api-token'

Threads

Threads

Threads, an Instagram app

Say more with Threads — Instagram's new text app.