I've been building a prototype for account information gathering using the Yodlee API, and was playing around with their pre-made UI at first.
All of the features for the Fastlink UI worked, however the load times for after log-in processing were unacceptably slow...sometimes taking up to 30-45 seconds for verification and information display.
Is this normal?
Figured out the issue. The bulk of the delay times comes from the delay for the registry of MFA services.
The providers/providerAccounts/{id} endpoint is continuously called until the MFA data is available which in some cases takes some time.
Related
We are trying to deploy a bot in a google function as the example of Trivia but using the Client object.
It works, but the next day the bot appears as disconnected.
How long is a circuit session? Is it possible to create the client within a google function?
It is not a token problem, every time a new one is generated we store it in Datastore and collect it from there.
Google Cloud Functions are stateless, they get unloaded unless you have steady load, at which time the SDKs websocket connection closed, hence the bot is offline.
The Circuit SDK is not the best API to use in Cloud Functions, the REST API (as used in the trivia example) would work much better. The SDK is great for a browser app, or a NodeJS app that stays alive.
Now in terms of the Circuit SDK, you are correct, even though the token is still valid, the session will time out after one minute. Of course this is only the case if the app stops (i.e. websocket is closed).
More info on the GCF's execution environment can be found here.
Does anyone know how many API calls PayPal allow each day? I'm using GetRecurringPaymentsProfileDetails to check if payment has been successfully made and I might be doing the API call a lot of times each day. They have the error code on their docs but didn't specify the rate limit.
Thanks
I've never run into any daily limit issues with API calls. That said, I try to avoid hitting the API that many times.
I would recommend you take a look at Instant Payment Notification (IPN). It will automatically POST details about transactions to a URL listener you have on your server. That script that receive the data and update your system accordingly. This happens in real-time so everything would update automatically and immediately. This way you don't have to hit the API to pull details because IPN will feed those details as they happen.
I have read this article
Please explain the refresh process that yodlee employs..
We understand this happens within a 19 hour window, is there anyway to stop the automatic refresh (the initial refresh on a Site based AddAccount1 is fine) - so that the subsequent refreshes can be manually controlled.
Thanks
The automatic refresh can be turned off for any client by Yodlee. You can contact the customer care team by logging a service request through YCC(Yodlee customer care ) tool and they will help you with that.
is it ever possible to authorize twitter app on the desktop without user input (of the seven digit number)?
I am trying to develop a realtime tweet fetching application between a list of friends/followers "suspects" communicating together. But the authorization code that needs to reset after 15 mins is an issue, so unless someone if manually present to handle re authorization after a couple of mins is a serious challenging. Is there a solution to my question.
Joe Mayo or any one, pls help here.
Thanks
There are two different issues at work here: authorization and 15 minute rate limit windows. For authorization, you receive OAuthToken and AccessToken, accessible via IAuthorizer.Credentials after the user authorizes. These tokens never expire. So, you save them when the user first authorizes and then load them into IAuthorizer.Credentials and you won't need to perform authorization again. Here's a more detailed description:
linqtotwitter - grab the saved credentials
Since you mentioned something about "reset after 15 mins", I assume you're referring to Rate Limits, which are set in 15 minute windows. Here's a recent discussion:
How to handle LinqtoTwitter Rate(v2.1) limit exceeded Error
It would be helpful to review the Twitter docs on Rate Limiting.
Our site uses Facebook connect. When a new user signs up we ask for permission to pull their interest data, their list of friends, and their friends' interests. Fetching this data used to be a very quick process (couple seconds). Over the last week or so, the time to fetch this data has increase to 10+ seconds. According to Facebook insights, our site is not being throttled. We didn't make any changes to our site.
Anyone else experiencing this issue with Facebook? Have any ideas for how to address it?
Thanks!
As of 1/26 at 7:55 PM EST, the live status page doesn't indicate any irregular activity.
Sometimes this occurs because a user simply has a lot of likes and interests. I would recommend making this operation asynchronous following a flow something like this:
User connects with your app
Get the access token and store it in a queue that a background process can access.
Get all the information you need immediately to make the app work.
Some time later
In a background process, grab an access token from the queue, parse it and handle it however you'd like.
A simpler, although less stable option, is redirecting the user to a page upon installation which makes an AJAX request to that page telling it to download the information from the graph. This keeps the response time low, but does require your user to have Javascript enabled and for them to stay on the destination page long enough for the request to be created.