Is it necessary to have Google account to use google+ apis like google hangout etc ? Like with Google maps it is not required.
Yes, you do need a Google account to use the Google+ APIs. The reason differs based on the API you're interested in using, though.
REST APIs
You need an API key to use the Google+ REST APIs. You can acquired an API key from the Google API Console. You need a Google account to use the API console. This API key is used for many things including to manage your quota.
Hangouts API
The Hangouts API requires a Google account for two reasons. First, you must use the API console to create your project. Next, you must have a Google account to start a hangout.
Related
When creating chrome extensions that play with the youtube data api, the api key is used. But is there any other way to get data from google servers instead of exposing our personal api key in the xmlhttprequest, apart from the naive way of asking the user to create his/her own api in their account and input that to use it in the extension?
I would refer to Google for best practices.
https://support.google.com/cloud/answer/6310037?hl=en
You could use OAuth 2.0 credentials, obtain an access token through chrome.identity API, and then use that token in the XMLHttpRequests.
I have a site that I have tagged using Google Analytics. I can see that the stats are being created and I can analyse them using Google Analytics web tool.
I want to extract my tagging data using the Google Analytics API but all the instructions seem to point me towards the developers console to create my OAuth2 token. My site does not appear in the list of apps that is presented, so I can't do the next step of generating my OAuth2 token.
I feel like I must be missing something obvious, but I am hitting brick wall at the moment. How do I get the site to appear so I can see it in the developers console?
The Google Developer console is for registering your application, this way google knows who is using there APIs. Your Google analytics account wont show up here because well that's not how it works.
Create a new project you will get a client_id and client secrete that are used to identify your application. Then you use a programming language to access the API using the client id and client secret.
I am not a java programmer so i cant help you with that. You mentioned that you want to access your own data. I recommend you look in to using a service account. A service account can be used to grant authentication without having to prompt a user for access. This only works when it is your own account you are accessing and the data doesn't belong to another user. Take the service account email address and add it as a user in google analytics at the ACCOUNT level it must be the Account level. then when you use the service account in your code you will have access.
https://developers.google.com/analytics/devguides/reporting/core/v3/quickstart/service-java
I want users to my website to use Google Accounts to authenticate / sign in to my website. The primary use case being users will edit and generate content and we want to log ownership in a secure way. We are not interested in obtaining users Google data, we just want a means to authenticate users.
After googling, I came across some documentation, which seems to explain how to do this OpenID Connect (OAuth 2.0 for Login). But the documentation immediately says "Note: If you want to provide a “sign-in with Google” button for your website or app, we recommend using Google+ Sign-In, ...", which if you follow the link ultimately takes you to Google+ Sign-In.
What's the difference between these two pages of documentation? Why does the first tell you to go to the second while not saying the first is deprecated? Are both/either suitable for my use case? All it says is "we recommend" I want to know WHY, WHY do they recommend it?
UPDATE: I also found yet another link which seems to be documenting another approach https://developers.google.com/accounts/docs/OAuth2WebServer I think this is just for "Authorization" i.e. authorizing your app to make google api calls to get user data, so cannot be used for authenticating/sign-in.
BTW I'm building my website with a Scala Spray BE REST API & NG JS FE.
A comparison of the two is available here.
Google+ Sign-In with profile scope
Has Google client libraries for authenticating with OAuth 2.0, which includes support for Google+ and other Google services (like getting social information on a user). Also this can make implementing easier and requires less boiler plate code
Has the Google+ Sign-In button to simplify sign-in Has no pre-built widgets
Supports over-the-air Android installs
OAuth login is primarily just for authentication at a lower level, that is by making raw HTTP requests, no API.
OpenID Connect protocols (OAuth 2.0 login)
Google+ Sign-In supports OIDC interoperability if you configure with the openid scope and get the user profile using getOpenIdConnect.
OAuth 2.0 login supports OIDC directly. Use it for signing in users to apps that do not need social features and run on platforms not supported by Google+ Sign-In.
I want to develop application for google fit i followed This Link they mentioned to activate google fit API under oath and Api section.
But i cannot see anything related to google fit api in the developer console.
Go to the Google Developer Console and open up your respective project. Under APIs and AUTH -> APIs you should see a list of the available APIs. Enable the fitness API and you should be good.
You can also connect to Terra's API to access Google's API, amongst every other wearable
I am trying to get an API key for Google AJAX Feed API's. However, it will only let me login with my Gmail (Google account), and I don't see any way to login with the Google Apps account here.
Couldn't find anything related on Google or Lycos. So is it possible to tie the AJAX Feed API key (which I believe will let me access other APIs as well) to my Google Apps account instead?
Gmail mail addresses are linked to a Google account by default, but Google Apps mail addresses aren’t.
You’ll have to sign up for a ‘Google Account’ using your Google Apps email address. After that, you’ll be able to login using your Google Apps email.