-->

How to acquire API Key, Client ID and Client Secret for Blogger API v3 App

API keys are mostly used to acquire APIs client Library. When we are calling an API using our project app, it does not access private data. This key only used to authenticate your application for accounting purpose.

Getting API keys:

2. Select a project, or create a new one.
create a new one

3. In the sidebar on the left, expand APIs & auth. Next, click APIs. In the list     of APIs, make sure all of the APIs you are using show a status of ON.
APIs & auth

4. In the sidebar on the left, select Credentials.
5. Click Create new Key and select the appropriate key type.

Always keep your API keys secure, follow the best practices for securely using API keys.

Getting Client ID:

OAuth 2.0 allows users to share specific data with you while keeping their usernames, passwords, and other information private.
To use OAuth 2.0 in your application, you need an OAuth 2.0 client ID, which your application uses when requesting an OAuth 2.0 access token.
2. Select a project, or create a new one.
3. In the sidebar on the left, expand APIs & auth. Next, click APIs. In the list       of APIs, make sure all of the APIs you are using show a status of ON.
4. In the sidebar on the left, select Credentials.
5. Click Create new Client ID.
6. Select the appropriate Application Type for your project and enter any              additional information required.
appropriate Application

7. Click Create Client ID

Client Secrets:

The Google APIs Client Library for Python uses the client_secrets.json file format for storing the client_id, client_secret, and other OAuth 2.0 parameters.


The client_secrets.json file format is a JSON formatted file containing the client ID, client secret, and other OAuth 2.0 parameters. Here is an example client_secrets.json file for a web application:





Google APIs Client Library

Here is an example client_secrets.json file for an installed application:

{
  "installed": {
    "client_id": "837647042410-75ifg...usercontent.com",
    "client_secret":"asdlkfjaskd",
    "redirect_uris": ["http://localhost", "urn:ietf:wg:oauth:2.0:oob"],
    "auth_uri": "https://accounts.google.com/o/oauth2/auth",
    "token_uri": "https://accounts.google.com/o/oauth2/token"
  }

}




No comments