Igor Kromin |   Consultant. Coder. Blogger. Tinkerer. Gamer.
Notice: I'm taking a break from blogging to focus on Atari Gamer . com, check it out!

NOTE: This article is 3 years or older so its information may no longer be relevant. Read on at your own discretion! Comments for this article have automatically been locked, refer to the FAQ for more details.
If you want to use the Google Plus API in your project, you have to create an app first. This is a relatively easy process and is described in the quick-start sample apps that Google provides, however here's another version with screenshots, because pictures are easier to follow than blocks of text.

So lets get started, but first here are some links that will be useful throughout this post:

To create an app, go to the Google Developer Console and click 'Create Project'.

Fill in the Project Name and the Project ID and click 'Create'.

Navigate to APIs & Auth > APIs and under Social APIs click Google+ API.

Click 'Enable API'.

Navigate to Consent Screen page and enter your email address and the product name, then click 'Save'.

Navigate to the Credentials page and click 'Create new Client ID'. Select Web application. Enter the JavaScript origins for your app, this is the domain name where your app will run from. Enter the authorised redirect URIs, this is where the OAuth2 redirection navigate to on your domain once Google has authenticated your user. Click 'Create Client ID'.

Once the client ID is created, the Credentials page will show two new important pieces of information, the client ID and the client secret. These are required for OAuth2 functionality used with Google+ API.


Skip down to comments...
A quick disclaimer...

Although I put in a great effort into researching all the topics I cover, mistakes can happen. If you spot something out of place, please do let me know.

All content and opinions expressed on this Blog are my own and do not represent the opinions of my employer (Oracle). Use of any information contained in this blog post/article is subject to this disclaimer.
comments powered by Disqus
Other posts you may like...