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 .
Related
I have an application with (nuxt js using nuxt-auth) with local authentication so far (later I want to add git and google auth).
Now I need to add authentication to invoke other services / API (like google cloud rest API, payment system, youtube API, etc...)
The question is: the user is authenticated only once (during login to the application.) but each of these 3rd party APIs has its own authentication.
How to implement multiple authentications. (I read the documentation and google for the entire day but there is no clear answer).
As of today, it looks like it is not doable (people are needed on this module): https://github.com/nuxt-community/auth-module/issues/889
So, you would need to make it manually by plugging the APIs yourself.
Answer to your latest question~comment
Nuxt is indeed nice with some of it's modules (but you can totally dislike it, no problem :D).
First thing that you need to know, is that this project (nuxt-auth) is not the biggest one, #pooya is doing his best but he is on a lot of projects, so he cannot give all of his love to it. Then, you also need to understand that it's working great but it's still in a decent beta state with a lot of missing features, needed documentation and a lot of small things to make it an all rounded solid top notch solution.
That do not mean that you should not use it, I'm just saying that this module do have some limitations. Hence, the fact that it is not supporting a whole lot of OAuth solutions in a clear + simple + flexible way. And some breaking changes may be introduced in future updates.
The module is aimed towards having an OAuth solution to block the content of your website behind it (in my opinion). It means that you will usually use a single login solution and then, being able to have access to your app. I don't think that it's a viable multi-OAuth solution (yet).
Some services don't even need to use a solution like this. Stripe for example, should not be handled on the frontend but communicate with a backend for sensitive variables and just send minimal info thanks to Stripe Elements.
That said, the most common solution is JWT or OAuth2, and you could totally have a backend service or service like Okta, Auth0 or alike, do the heavy lifting by allowing simple logins to providers (Github, Google etc...).
To sum up, you do connect to this backend/service thanks to nuxt-auth, the service itself does the provider connection and you get the best of both worlds while still connected in a secure way through your initial nuxt-auth entry point login.
Or you could try to reach the community on Discord, see if somebody knows how to do it. Or even try to read the source code to see if it is currently feasable.
And that's my 2cts.
I want to build a simple UI that surfaces a subset of the functionality of Google Ads UI by using the Google Ads API. Is there an example that shows how this can be done?
I believe there is no such thing, however there is a lot of examples on HOW to use the Google Ads API, and as a developer it's up to you how you want to turn that into a UI.
After all, WHAT you use the API for is entirely up to you, i.e. it is your design. Making the UI is a separate task from accessing the API, so a tutorial on how to design a UI is separate from how to access the API.
You can read about the Google Ads API here, and it's littered with examples. Warning, it has a pretty high technical level and just getting OAuth setup can prove to be a major hassle. Good Luck.
enter link description here
I am trying to implement account aggregation solution and am confused right now as there are multiple API's available that do the same thing.
I came across new Yodlee API as well as RESTful Wrapper APIs'. Both of these API classifications do the same thing but provide different APIs sets.
Can someone please let me know which one should I use?
I am referring to this link
https://developer.yodlee.com/API_Resources/API_Reference
Please go with Yodlee APIs, which is our latest product.
This is purely REST and the API response is simple, informative and decluttered. Here Webhooks is also supported
Please refer- https://developer.yodlee.com/Yodlee_API
API Flow- https://developer.yodlee.com/Yodlee_API/API_Flow/Add_Account_With_ProviderAccount
Swagger tool( to test APIs)- https://developer.yodlee.com/apidocs/index.php#!/providerAccounts
Hope this helps you in getting started.
Regards,
Krithik
Your documentation(API Reference) mentions some fields/endpoints deprecated but they still work in the old style. I find document inconsistent.
Also i could not even find a support email where i could even mail about this problem.
I would appreciate if you consider these points.
Thanks
I have read a thread regarding Yodlee implementation and on one of the responses a user said "It is easy to intergrate your app with Yodlee API" How exactly is it easy to implement Yodlee and integrate it with an existing C# Web App? I don't mind getting dirty, but I would like to know how hard can it get and is there forums out there and enough developer support? Please assist urgently as we need to test and implement Yodlee before the end of the month also note I am new to Yodlee and API integration.
Thanx in advance
You may not need to get dirty at all. It is so simple to implement Yodlee in any .net language. Yodlee provide a client library for .net as well, all you need to do is to wrap your business logic around the library. On other hand if you wish to take greater control of api calling as well, you will be provided wsdl proxies to the web services, code what ever way you feel good with it.
Twitter offers 'web intents' that are an alternative to OAuth access to their API. Basically, this provides a less feature rich experience, but can still be quite handy. User clicks on 3rd parts websites can create popup windows that check whether the user is logged in to twitter and if they are, allows them to us some Twitter features such as tweeting, retweeting, or following users.
My question is, how could I go about implementing an API like this? Are there tutorials or libraries? I'm not sure what technologie(s) power web intents or where I should start searching.
Thanks.
You can read more about web intents at webintents.org and read the W3C's draft spec. As far as I know, web intents are still somewhat of a new beast on the web and they have not been standardized.
Still, you may want to read this blog which contains a few examples of registering web intents and check out Paul Kinlan's git repo https://github.com/PaulKinlan/WebIntents
Hope that helps you get started.