We currently have credentials and access to FastLink 1.0. I'd like to try FastLink 2.0.
The documentation I found # https://developer.yodlee.com/Fastlink_2.0/FastLink_Integration_Guide_for_Web is okay but I am missing a couple key pieces of information.
Questions:
Can FastLink 1.0 users immediately try FastLink 2.0 or is there a setup/migration step?
It looks like FastLink 2.0 uses a different oauth tokening endpoint, is that the case?
How do I create the FastLink 2.0 URLs from my current FastLink 1.0 and REST urls, specifically:
"Getting the token": http://<REST_URL>/authenticator/token
"Rsession Based Launch Parameter": http://<node domain>/authenticate/<cobAppName>/
What is our REST_URL base?
What value would we use for <cobAppName>
Thanks
For Fastlink 2, a separate provisioning is required and its not available Out of box. YOu will need to contact your respective Sales Counterpart for enabling the same.
Yeah, Fastlink2 is based on a different architecture all-together. End points etc will be different.
Once Fastlink2 is provisioned in your respective environment, we will provide you the required end-point etc to invoke the same.
Regards,
Vishal
Yodlee Interactive
Related
Is it possible to get the comments from a tweet in version 1.1 of the Twitter API?
I know it's possible in version 2.0 but I must use version 1.1.
There is no direct ability to retrieve a thread using conversation_id in v1.1 - this functionality does not exist. You would have to try to use the search API to find replies, but this is much more difficult and less likely to find threaded responses.
I have several dozen offices that haven't migrated to OAuth 2.0 yet. One of these offices I transferred to another subscriber, and the app needs to utilize 1.0 until we can migrate. I recall being able to create Oauth 1.0 apps after 2.0 was implemented by using a URL parameter, but I can't recall the actual parameter. Does anyone know how to do this?
https://developer.xero.com/myapps?privateAppCreation=true
This will work until the end of June 2020.
is There any code related changes like getting memsiteid after adding account and all api's call related code when i apgrade my application to fastlink 2.0
There is no changes to the APIs, all the APIs will work as it is.
The changes in FL 2.0 is from UI perspective and also the way you access it. Accessing FL 2.0 is no more dependent on Oauth.
I am brand new to YODLEE API.
Is it mandatory to use Fastlink? Is Fastlink mobile responsive?
What if I want to build my own instead of using Fastlink? Do you have any guides to help?
FastLink is not mandatory. You can definitely use SiteBased APIs for having this flow handled. However, there are certain advantages you would have if you use Fastlink, like the add/Edit account flow is completely handled by Yodlee and that would reduce your coding drastically.
There is lot of documentation around this on our Developer portal # Add Site Account
Hope this helps, Happy coding .
I do not see a .NET client for the Google People API here.
https://code.google.com/p/google-api-dotnet-client/wiki/APIs
Do you know of any?
I need to get the user's full name, email address, gender and date of birth from Google using OAuth2. I could use it the raw HTTP way, but just to be safe, I want to use a Google provided client API.
Update
Hurray to hand-plumbing
The Google .net client Library can be found on NuGet, the plus package is here Google.Apis.Plus.v1 Client Library
PM> Install-Package Google.Apis.Plus.v1
I'm pretty sure it requires the latest version of Nugget to get it.
But I think you are going to have a small problem. Not all of the information you are after is exposed in the API. Sex and date of birth for example.
You can try it here People.Get. Scroll to the bottom: Authorize it then in userId enter "me" and it will show what the API can get of your data.
All the APIs are available here: https://developers.google.com/api-client-library/dotnet/apis/
I'm pretty sure that one of the following APIs will make your life easier: https://developers.google.com/api-client-library/dotnet/apis/plus/v1 or https://developers.google.com/api-client-library/dotnet/apis/oauth2/v2