I use some self developed script to get info about my posts and followers. Recently I discovered that Instagram changed rate limits for my app. I see following info in headers:
x-ratelimit-limit: 200
I learned Instagram blog and page with changes but found no mentions about any changes since Oct 1, 2017.
Is this new limit related only to my token or to entire platform? Could you check your token?
Yes It is, Although no official communication.
I also experienced that.
I found this in their documentation.
The Instagram API uses the same rate limiting as the Graph API (200 calls per user per hour) with one exception: the /media/comments edge limits writes to 60 writes per user per hour. Please refer to the Graph API's rate limiting documentation for more information.
https://developers.facebook.com/docs/instagram-api/overview/#rate-limiting
https://techcrunch.com/2018/04/02/instagram-api-limit/
Hope this will be helpful.
Update:-
Further on 4th April few more APIs deprecated by Instagram.
https://www.instagram.com/developer/changelog/
Some perspective:
This 200 per hour call has been in the Graph API documentation for at least a month (according to wayback machine).
Facebook must have panicked over the weekend and pressed the "require Graph API permissions" button, thus our current situation. :\
Yes,
The limit has been reduced.
Here are some reference links for detailed documentation:
Instagram API limit reduced to 200 from 5000
https://techcrunch.com/2018/04/02/instagram-api-limit/
https://developers.facebook.com/docs/instagram-api/overview/#rate-limiting
Hope it helps
Thanks
Here's our answer: https://www.instagram.com/developer/changelog/
The API deprecated immediately. So really the limits probably don't matter that much anymore. I really don't see myself building another app based on their API...
Here is The New Instagram's Public Api Update , unfortunately Limit rates are worthless for some Features in Instagram .
April 4, 2018
The following endpoints are deprecated immediately:
Follows and Relationships
GET /users/self/follows
GET /users/self/followed-by
GET /users/self/requested-by
GET /users/{user-id}/relationship
POST /users/{user-id}/relationship
Commenting on Public Content
GET /media/{media-id}/comments (Deprecation not relevant when fetching comments for self media)
POST /media/{media-id}/comments
DEL /media/{media-id}/comments/comment-id
Media
GET /media/{media-id}
GET /media/shortcode/{shortcode}
Likes
GET /media/{media-id}/likes
POST /media/{media-id}/likes
DEL /media/{media-id}/likes
User Search
GET /users/{user-id}
GET /users/{user-id}/media/recent
GET /users/self/media/liked
GET /users/search
Subscriptions - to receive notifications when media is posted
Some information on Public Content returned through hashtag and location search will be removed - Name, Bio, Comments, Commenters, Follower Count, Following Count, Post Count, and Profile Picture
Related
I currently have the below API response for one of our instagram pages using the Graph API that includes media_product_type, even though our Page has a STORY we are not seeing it come through, but we do see FEED and IGTV, see here for the documentation on this field. Has this happened to anyone else?
/12334555/media?limit=100&period=lifetime&fields=name%2Ccaption%2Clink%2Cshortcode%2Ccomments_count%2Cmedia_type%2Cpermalink%2Clike_count%2Ctimestamp%2media_product_type&access_token='blah'
You will need to use the stories endpoint (not media)
eg:
{baseUrl}/{version}/{instagramUserId}/stories?fields=caption,media_url,timestamp,permalink,username,media_type,like_count,comments_count,shortcode,thumbnail_url,video_title,media_product_type&limit=10&access_token={accessToken}
Note: story info is only around for 24 hours, so ideally you polls for infor and then setup the webhook to receive the final counts before the story dissapears.
We're developing a service which helps owners of social accounts to answer questions asked in their social accounts/communities. The issue we're having with Instagram is the following: we obviously have read the open info on endpoints and comments and we do the following: we snatch some X top media of the account, and then fetch the comments from each media to see if there is a new comment there. It works, but.
We have to limit ourselves to certain number of top media to track. If there is an active account, it can easily have 1000s of posts. Ok, the probability of someone commenting on media like #900 is fairly low but still requesting and snatching comments for 1000s of posts seems like just creating unnecessary entropy :) and unnecessary load to server and to instagram too.
We're very sure there should be some way/hidden/secret/private/unofficial endpoint or whatever which gives out just the latest comments regardless of how deep the commented media is in the account.
If anyone knows how to do it, please share. I'd be eternally grateful!
Keep a track of comment count for all posts, and check for the count via media/recent API every hour or so, and then fetch comments using the get comments API for the media that has changed comment count.
media/recent API can be used to get comment count for up to 32 posts with one API call, so this will not reach the API rate limits quickly. This is better than using get comments API for every post to see if there is new comment.
https://api.instagram.com/v1/users/{user-id}/media/recent/?count-32&access_token=ACCESS-TOKEN
API response will have comment count:
"data": [{
"comments": {
"count": 0
},
...
"id": "xxxx",
...
if count has changed the use the id to get comments:
https://api.instagram.com/v1/media/{media-id}/comments?access_token=ACCESS-TOKEN
We are having problems with returning results from Instagram API for location (lat, lng) and hashtag searches. It only stopped working in the last couple of weeks.
Has Instagram changed API without warning?
PLEASE help us.
Does anyone also have a sample get call for hashtags?
The script is wtitten in Python.
Thank you
Coby
Theres a new Instagram API update that happened in June 2016.
refer dialogfeed doc link
I really wonder how they can increase traffic on insta by setting up stringint limitations. :-(
The Doc stats - "This aims to limit third party inadequate uses of Instagram user contents and to increase trafic on Instagram."
I am planning to use the /media/search endpoint in the Instagram API. For our purposes we would need to use MIN_TIMESTAMP to get publications written after a certain timestamp. However, I have noticed that this parameter is available in the deprecated API, and it is not available in the new API:
This is the endpoint in the deprecated API:
https://www.instagram.com/developer/deprecated/endpoints/media/#get_media_search
This is the endpoint in the new API:
https://www.instagram.com/developer/endpoints/media/#get_media_search
As you can see, MIN_TIMESTAMP and MAX_TIMESTAMP disappear from the new documentation. However, I have performed a query with these parameters and they seem to work.
I have searched in Instagram's developers blog and I did not find any comment on this.
Are these timestamp parameters disappearing in the future?
The changes were rolled out today (1st June 2016) and you will see that now the min_timestamp is no longer taken in to account.
I'm posting a comment to a content on Instagram using Instagram API.
My app is registered and approved, so I was supposed to have 60 comments per hour (or at least 30, in case it is still in Sandbox mode).
I keep getting this message:
The maximum number of requests per hour has been exceeded. You
have made 23 requests of the 15 allowed in the last hour
I can't understand where does the 15 request allowed per hour came from.
Couldn't find it anywhere in the documentation as well.
Well, I would suggest you to go to the developer dashboard(MANAGE CLIENTS) page and report this issue. Its an option there. After that wait for a day and then check your mail. You might find a reply from them. As you have transitioned from the sandbox mode to active, the limit should increase and I hope they fix it for you
Just some ToC I found.
Instagram may rate limit or block apps that make a large number of
calls to the API that are not primarily in response to direct user
actions. Details Here
And also here
Display more than 30 Instagram photos or videos per page in your
application or use an unreasonable amount of bandwidth.Found Here
It sounds like they could acutely intent to limit your requests to preserve their bandwidth. 15 requests seems like a reasonable amount, if you contact them with a reason why you'd necessarily require more they might up this limit.
Also interestingly, they can change this if they see fit
Instagram may elect to provide you with support or modifications for
the Instagram APIs (collectively, "Support"), in its sole discretion,
and may terminate such Support at any time without notice to you.
Instagram may change, suspend, or discontinue any aspect of the
Instagram APIs at any time, including the availability of any
Instagram APIs. Instagram may also impose limits on certain features
and services or restrict your access to parts or all of the Instagram
APIs or the Instagram Web site without notice or liability.Details Here
Hope this helps