No JSON could be decoded

[gurisko]

It seems that Instagram changed their endpoint. followers (link) gets 404 back.

console output:

attempting login...
logged in successfully
building follower list...
Traceback (most recent call last):
  File "instamanage.py", line 419, in <module>
    menu()
  File "instamanage.py", line 94, in menu
    start_sync()
  File "instamanage.py", line 135, in start_sync
    data = json.loads(followers.text)
  File "/usr/lib/python2.7/json/__init__.py", line 338, in loads
    return _default_decoder.decode(s)
  File "/usr/lib/python2.7/json/decoder.py", line 366, in decode
    obj, end = self.raw_decode(s, idx=_w(s, 0).end())
  File "/usr/lib/python2.7/json/decoder.py", line 384, in raw_decode
    raise ValueError("No JSON object could be decoded")
ValueError: No JSON object could be decoded
logging out...

[realtux]

Well that's lame :/

[tducasse]

Well that's lame :/

Exactly what I was thinking haha

I think they changed their endpoint, I read about them deprecating their /query route...

The graphql api seems available at /graphql/query now.

[realtux]

yes, it looks like they are using /graphql/query. rather than a custom string as a post var, they are doing everything as querystring params. the response looks similar. this probably isn't that hard to fix.

[gurisko]

Is anyone looking into this?

[danperrout]

Same issue here...

[katepratik]

@ebrian So have you fixed it yet?

[realtux]

@katepratik No. This project is no longer maintained. I personally don't have any free time to get this fixed. You are welcome, of course, to fork the repo and make the fix. I'm sure it wouldn't take longer than an hour or two.