I tested Windows VM upgrades & downgrades by using PowerShell cmdlet (Invoke-WebRequest) and REST API (Softlayer API).
I searched concurrent API calls at once this website. The answer is 50 calls.
But I confirmed test result 20 calls at once.
What exactly about limitation on concurrent API calls (= HTTP requests at the same time)?
the API limitation according Softlayer is 50 api call per second for user, if you have more than that you will get an error saying that you exceed the rate limit.
regards
Related
I have a Informatica workflow which calls REST API Salesforce, I have 10 sessions concurrent each should process 100 records. However I hit 400 bad request. I run one session it runs good. Is there any limit on salesforce API limit? There was a connected app created for our integration and integration user which has API user profile
Based on this link, there are four policies for denying requests in the WSO2 API Manager.
Block calls to specific APIs
Block all calls from a given application
Block requests coming from a specific IP address
Block a specific user from accessing APIs
Based on this link, The following keys can be used to create custom rate limiting policies (with Siddhi query language):
resourceKey
userId
apiContext
apiVersion
appTenant
apiTenant
appId
clientIp
I need to deny requests within specific time limits. Maybe particular hours or some specific days. Is there a way to do that?
You can check on Siddhi Query functions to develop your custom Rate Limiting policy in the WSO2 API Manager to perform the limiting within a specified timeframe.
Also, the mentioned requirement can be achieved by developing a Global Synapse Handler and engaging it with the API Manager server. The Synapse Handler implementation is done using Java and will get engaged with each API call invocation.
Siddhi Cron
Synapse Handlers in WSO2 API Manager
I'm requesting a REST API through a HTTP Client from my machine (fiddler and C# app) and very first time, it takes around 30 seconds to get a response but it's very quick (around 250 ms) for subsequent requests to the same API.
REST API has been hosted on a different environment
Using fiddler and a C# app as client for the requests and both results in same way
The same REST API if requested from a different machine (in same domain, not API hosted one) is not having problem and very quick. So it's my machine only.
However there is no issue when requesting the REST API from any browser(IE, Chrome, Firefox) and REST Console.
I tried toggling 'Reuse server connections' (ON by default) option in fiddler and found that disabling that is making all requests slower (around 30 secs)
No impact of 'Reuse client Connections' option in fiddler
Could you please suggest what is the problem here as to why requests are taking so much time for a response and how can it be solved.
I am confused about the cost of the alchemy api. I am trying to figure out the cost of 3000 requests but it looks as if each request costs $0.007 which seems rather expensive. or is it $0.007 per 1000 requests?
You are referring to the standard pay per use plan. Basically the main concept is the API Event, not the request.
As stated in Alchemy API Service terms:
Events are calculated for and included in the information returned by each API call. Calculations vary by the type of service:
Events related to the use of the IBM AlchemyLanguage API will be calculated based on the number of enrichments returned by the API. Many of the API calls require 1 event; some API calls require multiple events.
Events related to the use of the IBM AlchemyVision API will be calculated based on the number of enrichments returned by the API. Many of the API calls require 4 event; some API calls require multiple events.
Events related to the use of the IBM AlchemyData News API will be calculated based on the following facets:
a) the number of enrichments returned by the API; b) the volume of data returned by the API; and c) the length of time, as specified in the API call, used to determine the number of news objects included for analysis.
In the Free plan the customer is entitled to a free allotment of 1.000 API Events per day across all services. In the Standard plan you will be charged per API Event.
The Standard plan is convenient when you need many concurrent calls.
If you are not deploying a large-scale application maybe using some cache services in the right way you can work in the free tier.
Take a look at Pricing for AlchemyAPI Services to read a detailed description of what is a transaction and how AlchemyAPI define those.
Does anyone know if there is a way to increase the quota limit of 10 queries when batching calls to the core reporting API?
This question/answer mentions the limit of 10: How can I combine/speed up multiple API calls to improve performance?
If I try to add more than 10 queries to the batch only the first ten are processed, each one after that contains a 403 quota exceeded error.
Is there a pay option? Would love to speed up the process of reporting on GA data for a bunch of URLs. I looked in my Google Developer's Console under the Analytics API where there is an option to increase the per-user limit and a link to request additional quota but I don't need total quota to increase, only allowed batch requests.
Thanks!
Quota is the number of requests you are allowed to make to a Google API without requesting permission to access more. Most of the Google APIs have a free quota, a number of requests Google lets you make without asking for permission to make more request. There are project based quotas and user based quotas.
Unless it says other wise APIs Quotas are projects based not user based.
User quota example
Per-user limit 10 requests/second/user
Some Quotas are user based, a user is normally the person that has authenticated the request. Every request sent to google contains information about who is making the request in the form of the IP address where the request came from. If you have your code running on a server the IP address is the same all the time so Google sees it as the same user. You can get around his by adding a random Quotauser to your request this will identify the request based upon different users.
If you send to many requests to fast from the same user you will see the following error.
userRateLimitExceeded The request failed because a per-user rate limit
has been reached.
The best way to get around this is to use QuotaUser in all of your requests, and identify different users to Google. Or just send a random number every time should also work.
Answer: You can't apply for an extension of the flood protection user rate limit. But you can get around it by using QuotaUser.
more info on quotas can be found on Google developers console APIs