does the old api of onedrive (skydrive) which was exposed in liveconnect api will be down(close) with time???
the above statement was made in one of the blog
http://venturebeat.com/2015/02/24/microsoft-launches-new-onedrive-api-with-change-tracking-resumable-uploads-and-customizable-thumbnail-images/
m currently working to integrate the onedrive with our product, it is reallu tough decision to go with new apis or use older one...
pls comment, ty in advance
We recommend you use the new API. It offers more features, better performance, and should be easier to use than the old one. We haven't announced plans for the LiveConnect API, but we're actively developing the new API.
Related
The Wit AI project added a new concept called Story to their Converse functionality. Is there a way to manage (create/edit/verify) these Wit AI Stories via their HTTP API?
This is what the Wit.ai team said when asked about having an API for stories:
"Not yet, unfortunately. The only workaround is to use the export/import and update the JSON files but I agree this is not great. Or to try to emulate the calls made by Console...very hacky sorry."
You can try API.ai, their API is more complete and it's free as well.
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
Anyone having trouble building API's with the new Kimono Desktop app. When I click create API the browser just stays on create API screen loading but nothing happens.
I even tried building an API that is the same as one I built when Kimono was still in business and no luck.
My existing api's still run and pull data fine.
Working just fine here.
Just a shot in the blue...did you install the new extension specifically for the desktop app? The old one can't work anymore since Kimono disabled the online service.
You can't build new APIs I think - only existing ones. :( Said something like it was not the acquiring company's policy to provide this publiclu available service but since they did not know how many businesses depended on their APIs they decided to allow existing APis to run.
You can also use their software for replace the online API. But it's an abandonware.
It's working great but on some website I can create new API because of an error.
I just find a possible (free) product that can replace Kimono : Datascraping.co.
They will include an REST FULL API within few days / weeks, as they said here.
It's a good software, but comparing to Kimono Desktop it's a little much more complicated.
Kimono got bought out and it's not working anymore.
Import.io is good but it kinda expensive for me. I've tried the free trial before but see the price starts from $249, so... https://www.import.io/standard-plans/
I don't have any progamming skills so I know very little about some web scraping frameworks like Scrapy.
You may want to look at this new web scraping software called Octoparse.
In case you want to know, here is the link:http://www.octoparse.com/
It takes a little time to begin. But they have rich tutorials on the website. Plus it doesn't require programming skills.
They provide cloud-based scraping service and API access.
You can use it to create API but you have to pay for the service. Free version doesn't have the API and cloud service.
I've been using it for 2 month with the Standard plan $89, which a lot cheaper than import.io. So far so good.
Hope it would be helpful for you.
Is there any way currently to do a parallel payment in paypal with the rest api? I am building a mobile application and can only use the rest api system however there is no documentation on how you can use parallel payments with REST.
You can do everything else so it seems to me like the developers got to that feature and just gave up :P.
This feature is a huge part of our website and if we cannot use it on the mobile app it will mean we have to redo how we handle transactions on the site so that both areas are consistent.
If this feature is not available since rest was supposed to be the refresh of all their API's to support newer tech is it coming? Does anyone know and if you do any information on a timeline would be helpful.
REST API does not support parallel payments at this time, it's in the product road map but not yet in the released APIs.
An alternative for your use case is to integrate the webview embedded Express Checkout flow into your APP, it provides the most identical experience to payers since the new UI was released.
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.