|Newsfeed Stories|| |
|Newsfeed Posts|| |
Instagram made some changes to its API & app approval policies as of 2018, revoking access to existing apps and requiring a much stricter approval process to even access any amount of data from Instagram (even if public or from your own account).
Frequently Asked Questions
taken_at field in posts is an epoch, you can convert it to a human readable timestamp with an epoch converter.
code field in posts can be used to construct the URL to the Instagram post on the web by prepending
https://www.instagram.com/p/ to it.
While this was a win for user privacy, this change makes it even more difficult for developers to get started building something to prototype with (and then eventually go to Instagram for formal approval).
A number of unofficial APIs and platforms still exist for accessing Instagram data, though Instagram is aggressively making these approaches more difficult to use with request signatures and certificate pinning on applications.
Although these private API endpoints appear to require signatures to work properly (why a full-fledged Python library exists), with a little trickery it's possible to use these endpoints with your cookie from the Instagram Web App.
Getting Your Cookie
You'll need to use the Chrome Developer tools and need a valid Instagram login to get your cookie, but the process is very simple.
sessionidand double click the value to the right of it. This is your Session ID you'll need to use these endpoints
Automated Logging In
While not recommended for beginners, if you need an automated access to log in and retreive your session ID, please see the Instagram Login task, which will retreive your session ID via endpoint.