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
Related
Looking for a list of tables that are accessible to developers to make sure we can accomplish what we're hoping to before going through all of the effort to get the data into Azure. Anything someone can share?
Adam
Xero's documentation is frustrating, as some of it is out of date and references long-dead information.
Use the Xero API Explorer to verify at
https://developer.xero.com/announcements/all-new-api-explorer
You're wise to verify this before starting coding as there are a lot of oddities (and omissions) in the API.
I'm working on a cloud project and I have to use Contrail it provides a RESTful API to use, but it is documentation is too small. I would like to know how to perform rest requests, especially post requests on "project" resource.
Each Contrail config node provides supported API details(searchable) at http://:8082/documentation/index.html
You could also check here which is a bit old but should serve your project API needs.
Your question is old, but as there are no other answers I thought I would contribute one. Were you interested in an answer or just wanted to share the documentation you'd written? I agree with you that Contrail documentation is very scarce, and every attempt to contribute to it should be appreciated. I had to integrate with Contrail API a while ago, and found out that in some cases I had to call OpenStack APIs to get the job done (Contrail is built on top of OpenStack). Project and user management were some of them.
I wrote a documentation about Contrail api, For each resource I mention the allowed methods and which parameters to integrate on the request body and I test it until I get it to work finally I put an example. I haven't finished the documentation, I stopped working on Open Contrail. The documentation is my personal try maybe it would be useful and maybe it contains some mistakes, Thus, I would like to share it. You can find it here.
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.
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 need some help with implementing a status board with a REST API. I've already found the two best options (in my opinion): Stashboard and Whiskerboard.
I have already tried Whiskerboard and I find it easy to install and deploy because it does not need Google App Engine's SDK to be used locally. However, I need something like Stashboard's REST API: http://readthedocs.org/docs/stashboard/en/latest/restapi.html
I know that Whiskerboard is based on Stashboard so probably they have the same REST API. But I cannot seem to find any documentation on Whiskerboard's REST API. Moreover, I looked into each status board's models and there are lots of differences, with Whiskerboard's being largely simpler compared with that of Stashboard's, so they must not have the same REST API.
I will appreciate it if anyone can provide me a link to Whiskerboard's REST API which should be much like Stashboard's. If there really is none, some other solutions could still be suggested. Thank you in advance!
No, it doesn't have the same REST API. You could find this out by reading the code. If you want a similar REST API you have the following options:
Code the feature yourself.
Ask the developer of Whiskerboard for the feature.
Ask someone else at your organization to code and contribute the feature.
Good luck.
You can check out this solution forked by sijis and myself, jvasallo, that we have been working on. He forked the repo for whiskerboard and added an API to it. Still uses Django, and recently I did some work porting it to 1.5.1. Initially, Whiskerboard is a 1.3 Django app.
https://github.com/sijis/whiskerboard