I get a 429 quota exceeded response to the venues/venueid endpoint of the Foursquare API for every request. According to the docs, it should allow 500 authenticated requests per hour per token. There is no way this many requests are being made. I even created a new account, got a token that has never made a single API call, and it got quota exceeded on the first request. The headers have x-ratelimit-limit and x-ratelimit-remaining both 0. What is going on?
https://api.foursquare.com/v2/venues/VENUE_ID?v=20180620&oauth_token=TOKEN
Related
I have been testing around with the Azure App Services and got this error
App Service Plan Create operation is throttled for subscription.
As I understand I created too many apps in a short period, how long until I can create a new app again?
Thank you
I began receiving this error, but without the Retry-After property in the response. After working with Azure support, it turns out newly-created subscriptions take a while to fully allocate in the background. We had to wait 48 hours before the throttling error would go away, and that was what Azure support validated with us.
Once the 48 hours passed (and the new Azure sub was presumably complete in its creation), we no longer received the errors.
As I understand I created too many apps in a short period, how long
until I can create a new app again?
We dont have any ideal time that how long until you have to wait to create a new app again.
Throttling happens at two levels. Azure Resource Manager throttles requests for the subscription and tenant.
When you reach the limit, you receive the HTTP status code 429 Too many requests. The response includes a Retry-After value, which specifies the number of seconds your application should wait (or sleep) before sending the next request. If you send a request before the retry value has elapsed, your request isn't processed and a new retry value is returned.
You can determine the number of remaining requests by examining response headers. Read requests return a value in the header for the number of remaining read requests. Write requests include a value for the number of remaining write requests.
You refer this documentation,on how to Retrieving these header values in your code.
Does anyone have experienced any changes on Instagram API that are limiting access by server IP and not by user?
I have received this message: "Something went wrong: Throttled by Instagram because of too many API requests".
Is this a bug or normal?
That is not bug, and it is normal.
Instagram limits count of certain api calls, and if you call those apis fast enough, then Instagram throws the message "Something went wrong: Throttled by Instagram because of too many API requests".
If you try them after minutes or hours at worst, they will work fine.
Is OAuth API call counted as API request? As you know, the number of API request call is limited to 1,000/account/hour. My customer would like to know whether OAuth API call is included into its limit or not. I coudn't find out any information regarding this topic.
Their developing application now can't keep holding access token after an envelope process is completed. It will be fixed later but at present, OAuth API call happens whenever end-user sends an envelope through their application.
Therefore, they want to confirm this point.
I don't know offhand if OAuth API calls count against the limit. If they don't currently then they will in the future.
All software stacks for web apps include a session storage feature which should be used to store the access token returned from the OAuth process.
In addition, note that your understanding of the API usage limits is not correct. The limit is 1,000 API calls per Integration Key per account per user per hour.
For example, if Joe and Susan are using the same Integration Key (same application) and they both use the same account on DocuSign then each of them can make 1,000 API calls per hour.
While implementing the DocuSign we are getting The maximum number of hourly API invocations has been exceeded error message sometimes this is because of the API call rate exceed per 1 hour. Anyone have any idea how to increase the API call rate per account from 1000 to 5000?
You need to contact your DocuSign's Account Manager with a valid usecase why you need the API limit to be increased to 5000. As a defensive check you should always read the header in the API response, DocuSign provide the data as whats your call limit, how many calls are remaining and what is next schedule counter reset for you. By reading these header values, you can make your application pause for sometime so that you don't hit threshold limit and handle the limit scenario properly.
Along with your DocuSign Account Manager, you can contact support#docusign.com also.
How to increase following limit per hour on Instagram? is there any other ways to increase following peoples more than its limit.
Can we increase by using multiple application?
If you ask your users to log into their Instagram account, and authorize your app, then you can make 5000 requests per hour per user:
http://instagram.com/developer/limits/
If you just use your key, you are limited to 5000 requests per hour, no matter how many users you have.
But I'm worried, what if this token expires?
AFAIK, Instagram accesstokens don't expire currently.
Note: From Instagram documents.
Note that we do not include an expiry time. Our access_tokens have no explicit expiry, though your app should handle the case that either the user revokes access or we expire the token after some period of time. In this case, your response’s meta will contain an “error_type=OAuthAccessTokenError”. In other words: do do not assume your access_token is valid forever.
Should I authorize the app each time the token expires?
At the moment, you do not need to do that, as token does not expire. As and when the token expires in future, a corresponding warning or error code and message will be sent to you, which you need to handle.
what can I do to have my app always pulling data from account without
my participation?
You can try following:
Use sharedpreference to store the accesstoken.
First time when you try to fetch data that needs accesstoken(Authenticated requests), first check in the sharedpreference whether the accesstoken is stored or not.
if yes then you don't need to login, just use that accesstoken. If you don't have the accesstoken in preference then do the login using instagram credentials, get the accesstoken and then share it in shared preference and use that for subsequent requests.
You can provide instagram logout option in which you just need to clear the accesstoken from sharedprefernce.
Hope this is helpful to you.