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
Related
I'm programming an application for Microsoft Planner and I need to get the tasks of individual users. I am using Microsoft Graph Planner API. However, there are no recurring tasks in response. Recurring events are present in the internal api planner, the specific call is :
https://tasks.office.com/{clientID}/TasksApiV1/GetPlanDataAsync?planId={planId}.
I am unable to authenticate. I'm using TeamsFxProvider for authentication, but the token with the api https://tasks.office.com doesn't work (bad credentials error). Is there a way around this please?
Tasks.office.com is not a supported API you can use. It exists just to provide the web experience and will change frequently without notice. We're working on enabling the recurring tasks in the Graph API, which should be available soon.
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 know how to implement token based security via OAUTH to protect the access of an api. I also know ho to use HTTPClient to call an api.
But when I search/google how to use OAUTH calling a web api from a web api all it shows me is how to implement token based security for an web api (which I already have).
In my scenario I have an UI calling web api 1. After that I have to do some server to server communication: web api 1 calls web api 2 and web api 2 calls web api 3. Web Api 3 does something & returns to web api 2 which then does something based on success or failure, then returns to web api 1 (which does something) returning back to the UI.
(The reason for that intended implementation is storing (different) data in 3 different databases where I currently do not want (and later maybe not be allowed to) grant web api 1 direct access to them.
I am just unclear how I would manage the tokens (I don't want to request them every time, so I guess I will need some kind of service handling that and keeping them).
Any hint I could get the authorization (token handling) done?
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 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