I am doing integration for Evernote Business. So, I would like to know that is Evernote for Business support Rest API with OAuth2?
Evernote does not provide an official REST API; their API is Thrift-based. If you're interested in why it's Thrift-based and not REST, their former CTO discusses the reasons for that decision on their tech blog.
Tadaya Tsuyukubo has written a REST-based front end for the official Evernote API which is available here on GitHub. I haven't tried it so can't personally vouch for it. There's also a bit of discussion about it here on the Evernote discussion forum.
Related
we are trying to enable the One Tap sign-up from Google. It seems there was some security concern (reading online not officially by google) and the official document has been taken out by Google.
Is that API still working, can we integrate it or should we wait for it?
You can find related functionality in Smart Lock for Passwords section here
Looks like original SDK was removed in favor of more common browser Credentials Management API (draft of w3c) in Сhrome 51 and then reworked in Chrome 60.
Also, they have a codelabs tutorial to learn it step by step.
I'd like to get access to the API Testing console (the one mentioned in the Quick start of the Cognitive services translation services, useful to test the API without writing a single line of code), but I don't find any direct access to on the Microsoft Azure. Thanks in advance for your help.
I think the text you mention about the console is a copy-paste error from other cognitive services quick start page.
Generally with Cognitive Services, you can find webpages which seems to be hosted under Azure API Management, where you got the basic documentation and access to a testing Console. For example for West Europe, all the services are here: https://westeurope.dev.cognitive.microsoft.com/docs/services/
And for Anomaly Detector API, you can see the link to the testing console:
Sadly, it seems that there is not equivalent for Translator API.
You still have samples on Github that you can use, in several dev languages: https://github.com/MicrosoftTranslator
Or you can directly call the API with a tool like Postman, it is really easy to implement
I have a REST API published to Google Endpoints and have been using the API Explorer to interact with it. When I accessed API Explorer this week I found this notice:
"This site is deprecated for Endpoints APIs. For exploring and testing Endpoints APIs, try the Cloud Endpoints Portal."
I can't find any other information such as when this service will be terminated. Anybody have a link or other information?
The APIs Explorer not going away so much as moving to Cloud Endpoints Portals. You still get an APIs Explorer there with all the same features, and more. It's just a newer format more specific to your API, with more detail and better navigation.
As mentioned on that page, you can try out the demo, including trying out your own API spec using the "Try your own API!" button.
I'm working on an asp.net web application that has two types of users. Advertiser and Publisher. Both of them have credit(money) in their accounts.
I need to integrate Paypal payments so that an advertiser can add money to his balance. And also for the publisher to be able to withdraw money from his balance (money he made using the website).
I've gone through the Paypal REST and classic API's. Downloaded and browsed the .net code samples provided by Paypal themselves but I'm still having trouble deciding which SDK should I use to satisfy both scenarios with the best experience possible for the user. I'm inclined towards MassPay (in the MerchantSDK) for the withdrawals but I'm not 100% sure of this.
Any help or guidance is appreciated.
Many thanks.
The short answer is that you should use the REST SDKs if at all possible. PayPal's products are moving to that API and once everything is there, support for older SDKs will be discontinued.
In late 2005, Niall Kennedy blogged about Google Reader’s API: http://www.niallkennedy.com/blog/2005/12/google-reader-api.html
He mentioned that a couple of guys at Google suggested to him that the API might be made official within a couple of weeks.
Has the API ever been officially and publicly documented by Google?
No, despite the talk about Google doing this some day, there is no officially documented Google Reader API yet.
However, the API has been unofficially documented.
Related: Where to start with Google Reader as an API?
I've been successfully using https://github.com/brutuscat/googlereader that is a fork of http://code.google.com/p/pyrfeed/
If you want to see more samples, I wrote an article about how to use the lib to extract the main text content from an HTML. This is an alternative to boilerpipe mainly for blogs.