Like many others, I recently hit the limit on the number of upload requests I can make using my account's personal Application Client ID/Secret. It makes perfect sense because my application uploads ~100 images a day, so I could have hit either the daily or monthly quota.
I know you’re not AWS or GCP, but I was wondering if there is a way to let me pay to increase number of API calls i’m allowed (i.e. raise my Application quota)? If there isn't already a way to do so, i'd like to make a feature request to your product team. Let me know if you'd recommend any workarounds in the meantime.
{'errors': [{'id': 'legacy-api-5bcc787bb8-zpvcr/qtPyuFjKN3-3219168', 'code': '429', 'status': 'Too Many Requests', 'detail': 'Too Many Requests'}]}
Best,
Nick
Related
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
I'm trying to set up various Instagram clients to use with website integration. I must say that I am extremely disappointed in the quality of the Instagram developer documentation, and their API has some seriously annoying aspects to it.
That being said, when I try to update one any of my clients (under any of three accounts), I get the following error (in a non-styled, blank page):
Sorry, an error occurred while processing this request.
What gives? I was able to update a few of my clients, but then started getting this error.
Also, why does Instagram make it nearly impossible to create more than five clients? I need more than this to cover all of the environments that the website(s) run in, so I've been forced to create multiple Instagram accounts for each site...
Apparently Instagram's API (or at least the part relating to adding/editing clients) was down. I guess I'll mark this as answered, but I really wish Instagram would offer better documentation/support...
Im trying to add a feature to my website that involves the typical "invite your friends" with help from a contact importer (cloudsponge). Its a pretty popular and gets the job done but I need something faster..
The problem with cloudsponge is that they request all contacts in one call, this could mean a long wait time for someone with alot of contacts.
I looked at their rest calls and there doesnt seem to be a way to load contacts in pieces. Do any of these contact importing services allow you to pull in a few contacts at a time (lets say 50) so that we can show our user the first 50 contacts and load the rest / updating the view. So they dont have to wait forever for all the contacts to be pulled?
Ive looked at other apis like context io but cant seem to find a solution to this one.
I built the CloudSponge API.
Early on, we decided to support imports across a variety of providers while exposing a simple and consistent interface. Pagination and rolling or real-time access to contacts were things that were excluded in order to do that. To provide end-user feedback on the progress of the import, we added the /events endpoint.
So far import speed hasn't been a major issue for a couple reasons:
In general, end users with an address book of 10000+ contacts are rare (although this may not be the case for certain niches).
End users who do have this many contacts in their address book usually understand that it will take a while to import.
Having said that, the speed is something that we can definitely improve upon. Here's a few ideas:
We can allow for returning only a subset of all contacts by default. For example, we currently return all contacts for Gmail, which is usually a much larger number of contacts than are actually stored in 'my contacts'.
We can implement parallel paginated imports on the server side. This will make our server process work harder and faster to download the user's contacts from, say, Gmail. This adds complexity on our side but keeps the API untouched.
We can implement your suggestion: add a rolling or real-time access to contacts in our API, either in an extended endpoint or a new version of our interface.
I'm happy to work with you on exploring these to improve our service. Send us an email: support#cloudsponge.com
Graeme
We require to get the followers data (profile metrics specially follower's friends count) for my client's accounts having more than 500k followers. Because of Instagram api limitation we can only do 5k calls /hour. Thats why, it is impossible to load all followers data for every day. But there are few products like web.stagram.com etc, which are also using the instagram api and making unlimited (or some greater num than allowed limit) calls.
Are these partners exempted by instagram?
Please update if there is a way to get higher api limit.
We are ready to pay amount for the higher limit.
Regards,
Parvendra Adhran
You have to try to get whitelisted to get a new Rate Limit, there's a long waiting list and Instagram has mentioned they won't be getting to the requests anytime soon.
I've heard of people still waiting over 2 months so far.
I created an iOS app that using Instagram API and have a critical issue posting likes to Instagram.
Using endpoint – POST /media/media-id/likes, with user-specific access token. I request scope – likes from users.
Instagram API works fine for all requests except saving likes. We can only save/post a couple hundred likes to Instagram, and then response is "We've taken extra measures to protect the Instagram API from abnormal activity. Since you have recently created your API application, please contact apidevelopers#instagram.com to receive whitelisting for a higher rate limit."
There is other developers with same issue with no support or any feedback waiting for months.
Please, let me know if there is limits and how it works, or how to become whitelisted
I don’t want to create many Instagram API clients and assign users among them. It seems like bad acting for me, if there is official API with strict limits I want to work with it.
Instagram has new API limits: 100 likes/hr 60 follows/unfollows/hr per access token. That is only if you authenticate serverside and sign your headers. Check out the new authentication: http://instagram.com/developer/authentication/
I'm using it for my new site that automates likes/follows/unfollows, haven't had any problems works great. Check it out: http://instapromobiz.com
Instagram takes increased measures to limit your API requests based on IP address. This is not common knowledge, it's just something I've come to know from working with the API extensively.
They've built an API that is FAR from perfect, but have been upgrading it to be "smart". Smart enough to know that a newer client, pinging the API many times just for one user, may very well be a script kiddie trying to bot the system. For this reason, they do not give you a rate limit error, they politely say "we have taken extra measures to protect our API from being spammed by bots".
The good news is, other users should still be able to access your liking mechanism. Just not you, from that IP.