I would like to know if the PayPal REST API Support Desktop/Installed Apps?
When I go to create a new application the only two options for Integration type are 'Web' or 'Mobile SDK'.
REST simply uses HTTP methods to access APIs, so it shouldn't matter whether you have a desktop app. As long as your app can make REST API calls and parse the JSON response, you should be able to use the PayPal REST API.
You can use the Integration Type as Web and use any of the .NET SDKs available here to build Windows Desktop Apps.
http://paypal.github.io/#payments-tab-csharp
Let us know if you are looking for Windows 8 version of the SDK (as this is currently under development).
Related
I keep getting an error that there is a problem with my sample pronunciation. Although, the problem is not clearly highlighted. I am using Google Assistant SDK to integrate it into a raspberrypi and in no way intend to make any commercial use of it. I would like to publish the app only so that I get more than the limited number of API calls using one account.
Could you also tell me the limit to the number of API calls using one account?
Is it necessary to develop and deploy Actions in order to extend the limit on the API calls made using assistant sdk platform?
enter image description here
Currently I am developing a new application using API amember pro for an already website. I want to integrate the API into my app (ionic 5) and I am really new about this.
For now, I have developed in half way progress and I am using the list of API under Remote API Permissions. The problem is, all the API used are needed to be login again in app just like opening website in application. May I ask about how to identify the suitable API in amember pro to be used in Application?
Hopefully there will be someone who have experienced this and willingly to share this with me huhu. Thank you.
The docs for API amember is here; https://docs.amember.com/docs/REST
I have an ionic v3 app and I have google plus login in it. I recently got a mail from google stating "Google+ API Shutdown"(refer here for more details). Google team has also said:
If you see API calls to people.get, these can be the result of using
the Google+ Sign-In feature in your application, which is now fully
deprecated and is being shut down. Developers should migrate from
the Google+ Sign-In feature to the more comprehensive Google Sign-in
authentication system.
You may see OAuth requests for plus.me, even
if your project is not requesting this scope directly. You only need
to remove such requests if your project is directly requesting this
scope.
I currently use'#ionic-native/google-plus' plugin.
Can someone let me know what should I do with the google plus API in case of an ionic v3 project ?
I've been told (secondhand) that although the plugin is named google-plus, it no longer uses the Google Plus APIs.
I would like to develop a REST API app that I can access from both web app and mobile app.
The REST API need to support simple authentication that can be done in both from a web app and from a mobile app (like Xamarin.forms)
I don't need multiple users, I need simple access control to my API.
I tried to develop a Azure API app with AD authentication, but it seem like it is very difficult to add support to Azure API App.
To summarized my questions:
How to do simple authentication in Azure API App or Mobile App?
Should I use API App or Mobile App or something else?
Does it support Xamarin and Web app access?
This is way too broad. Are you doing data access? Do you need simple auth? Have you tried any of the quickstarts to try to learn about your task?
Look at Azure App Service Authentication / Authorization - it provides a server directed flow for web and mobile access
This should have been your first question. You want an ASP.NET app, running on App Service (I'm biased here). It should cover both API, Mobile and Web together.
Yes, the App Service covers all your needs.
I have a Google API console premier account, and I'm using the places service for an application that has two parts, web app and mobile app.
It seems that Google API distinguishes between server and browser apps. So for each category I have to generate keys specifically for it.
The mobile app is a native iPhone App, that uses the Google Places Web Services XML API for a simple auto complete function.
The question is in which category does mobile apps fall in?
Browser Apps
Server Apps
And any resources of how to use them?, does the Google JavaScript API V3 still requires an API Key for the premium users? Google documentation about this subject does not have enough information.
There are two different interactive types of Mobile Apps that use Google Maps:
ones that use the Maps Javascript API v3 (either directly or embedded in a Native Application)
ones that use Native Google Maps APIs (currently available for Android and iPhone)
For more on that you can have a look at:
http://code.google.com/apis/maps/articles/mobile_overview_v3.html
Ones that use the Maps JS v3 are Browser Apps, the Native Apps are neither. They have their own TOS and quota system, like the one for iPhone and the one for Android.
About Google Maps JS API v3. It an be loaded :
without any key
with an API console key, which will allow you to track your usage (this was introduced recently)
with Maps Premier client id (gme-) if you are a Maps API Premier customer
The XML web service for places API should be used only as a server side solution. This is because you can imagine that a user might steal your key from the source of your iPhone app (by sniffing on the traffic) and use it.
The safe way out is to use a proxy server. You would then register an App Key for server apps (with IP locking for your proxy server) and then make calls to the Places API from this proxy.
Another option would be to use UIWebView on the iPhone side with JS Maps API v3 and Places library on the Google side. You would then fall in "ones that use the Maps Javascript API v3 in a Native Application" category.
You could then use any of the 3 options to load JS Maps API that are mentioned above.
I had to cut away some links, since I am not able to paste more than two, but I hope that helps anyway
Unless you have strong reasons against it, the "ones that use the Maps Javascript API v3 in a Native Application" category is the best option. There's a nice talk from Google I/O 2010 about it: http://www.google.com/events/io/2010/sessions/map-once-map-anywhere-geospatial-apps.html