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.
Related
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 built a web app in Laravel 5.2, and now, I would like to use Angular or Vue, so I am separating an API from my controllers.
Thing is actually, in my controllers, I use a lot :
Auth::user() to refer to the logged user.
What is the best way to deal with it???
Read books about API design. If the existing app isn't designed to be a RESTful API in the first place then you're in for a lot of learning. Laracasts has a great series called Incremental APIs.
Laracasts.com
Build APIs You Won't Hate
OK, I'm expanding my answer, despite this is not a great question, it is probably too broad. You need to look into Oauth 2.0 authentication for your API, you can still use a username and password, but OAuth 2.0 tokens over SSL is probably the best simple way to provide authentication for your API. If it is only used internally, or is read only then you may not really require authentication for the API at all. There's not enough information about your use case to even make a guess about that. Good luck!
I am new to API's. I want to create one in grails.
I believe that another application website etc. would just post to a URL in my web-app and it will start a method.
Where is a good place to start my research into this. Any help would be grateful.Thanks.
it's my first answer but I hope it'll be useful for you :)
Here are some resources you should look into before making your own API:
REST - it's the theory about the whole concept of api you're building. Please find it on Wikipedia. I can't post link because of 2 links limit for new accounts here :)
http://en.wikipedia.org/wiki/SOAP - this is protocol supported by W3C for exchanging messages. Using standard should help your clients to adopt your api.
http://en.wikipedia.org/wiki/Oauth - obviously you should authenticate your users somehow. You can do it with Oauth - it's widely open and easy to implement. Again, your clients will have easy time connecting to it.
You will find implementations of all those technologies in Java or as Grails plugin itself.
I have a WCF REST service. Now the question is how can I secure my REST service so no one can use/call it? and what would be the best way to call it (e.g. using jquery, or from code behind)? the client application is on MVC 3.
please help and advise
Many Thanks
Not sure if you're still looking for a solution. But I used WCFRESTContrib as a basis for my project for the security features, among other things. It's very easy to setup Basic Authentication on the entire service, or on an individual basis for each service method. They have a full description on it here. If you don't decide to use the project, it should at least give you a good understanding on how it works with WCF REST api's.
I'm working on a tool in C# that interfaces the JIRA SOAP API. I have read the documentation but I can't find what I'm looking for. Does anyone know if it is possible to link an issue to another one via this api?
PS : Actually, my real need is to convert an issue as a subtask of an issue...
Last time I looked, JIRA's web service wasn't really actively supported or encouraged by Atlassian. It's very much a second-class citizen compared to the web front end, with very basic operations.
Also, it's not a WSI-compliant web service (it's an old Axis-based RPC_encoded service), and so modern web service stacks won't even bind to it. You might want check that your client can perform basic query operations before diving into the depths of the API.
You can actually go pretty far with Jelly scripts, but converting an issue to a subtask then linking it as a subtask... I'm not positive that you can go that far.