Deprecation of https://www.googleapis.com/plus/v1/people/me and how properly to migrate - google-plus

Recently Google plus is pending for shutdown, which also shutdown some Google Plus API including this one https://www.googleapis.com/plus/v1/people/me which our service is actively using.
That above API was used in one of our legacy login library, which I can't even find the source for it. Hence I am now trying to patch it myself.
Reading the migrate guide from Google, it doens't tell much in terms of how to change the url.
Referencing some open source library like 1, 2. I have come up with the fix of replacing the url https://www.googleapis.com/plus/v1/people/me with https://www.googleapis.com/oauth2/v3/userinfo, which works but oauth2/v3/userinfo lacks documentation, so I am pretty worry that oauth2/v3/userinfo is not intended to be used like the above.
So my question is:
Is my solution: change https://www.googleapis.com/plus/v1/people/me with https://www.googleapis.com/oauth2/v3/userinfo an intended migration, if not then how can I migrate out of Google Plus API?
Any documentation on https://www.googleapis.com/oauth2/v3/userinfo? The closest I can find is this, which seems more like an brief intro then a documentation.

The "/oauth2/v3/userinfo" call will not be deprecated on March 7th, 2019 as it is not part of the Google + API.
If you look at the Google Developers Console, those calls are not registered as part of the Google + API.
From Google email:
If you are directly requesting the “plus.me” scope, any other Google+
OAuth scopes, or making any Google+ API calls, please ensure that you
remove these requests from your project before March 7, 2019.

Since nobody answer, I think I will give out the best info I can gather...
For 1. Supported by multiple open source project. Pac4j, hybridauth. It seems like the method of change https://www.googleapis.com/plus/v1/people/me with https://www.googleapis.com/oauth2/v3/userinfo is the best you can do to fix this issue.
For 2. Still no detail documentation for that

Related

Does Google Data Studio have API functionality, and if not, will it in the near future?

I'm trying to automate a workflow using Google Data Studio. Requirements are simple - I need to be able to programatically copy a templated report (from a Python/Java application) and import/set a data source (Google Sheets doc) for that report. Nothing more fancy (no visualisation creation, formatting, or anything graphical, etc.).
Sources here, here and here (last two require Google Cloud Console account) suggest an API does exist (and detail a setup process to access it). However, after going through this setup process, I can find no details or documentation of any functionality, and consequently have been unable to progress.
Can anyone authoritatively state whether:
1. There does exist any API functionality for GDS? and
2. If not, are there plans to develop such? (since the Google links above suggest there is, I'm wondering if this means it's in the pipeline for near future).
The only directly related SO posts I can find are here and here. The first suggests there isn't, but doesn't account for the Google links I've provided above which suggest there is; the second doesn't really cover the same use case, so doesn't provide answers applicable here.
FYI - I've posted a Google Community forum post here asking essentially the same question.
If anyone is able to help out, that would be greatly appreciated :) Many thanks in advance for your time and help! :)
Fresh as of 2022-05-23
There does exist any API functionality for GDS?
Not in the way you are expecting. The three links you posted all refer to the current Data Studio API. The only things you can do with that API is view your Data Studio assets and update permissions. That's it. This API won't let you create/copy/modify reports or data sources.
If not, are there plans to develop such?
Not in the near future. You can make/vote for this feature request in the official tracker. More popular feature requests are usually prioritized in roadmaps.
That being said, a lot of the API use cases can be resolved using combinations of Community Connectors, config parameters, direct linking, viewer's credentials, Linking/Integration API etc.

Is Using Deprecated Google Infographics API a Good Idea

So I have recently found out about Google Infographics QR Codes API which is very easy to use and I have yet to find a better alternative. Example: https://chart.googleapis.com/chart?cht=qr&chs=200x200&chl=Example:
However their documentation page (https://developers.google.com/chart/infographics/docs/qr_codes) says this: Warning: This API is deprecated. Please use the actively maintained Google Charts API instead. See our deprecation policy for details.
Also Google Infographics main page(https://developers.google.com/chart/infographics/) says the fallowing:
Deprecation notice
While the separate Google Charts service is actively maintained, the infographics service was deprecated in 2012 and turned off on March 18, 2019.
Go to Google Charts
About Google Infographics
This deprecated API serves static PNG images via URLs you can place in the src attribute of an tag.
As you can see eventhough Google says that it is turned off the API for QR Codes still works fine. Does this mean that I can still use this API with no worries? If not is there an equivalent API?
Using a deprecated anything is never a good idea. deprecation notices are there to tell developers that they need to move away from something because its due to be shut down.
If its deprecated that means they will turn it off. They start turning it off on "March 18, 2019". It can take a while for it to be completely turned off and some APIs continue to work for a year or so before they stop working all together.
I would not use this or develop with it as it is going to stop working soon.
Recommendations of equivalent APIs is out of scope for Stack overflow i suggest you Google it.

how To Have complete Access to Instagram API (Live/Sandbox)

I'm new to Instagram API and my question is how to get complete access to Instagram's API without any limitations - like API's that any other Third-Party Client Apps Like (6tag /ink361.com/insta(X))uses .i want to give my users complete access so they can (like - repost - regram - Edit - ...).
and as I read in the official documentation there is a Sandbox / Live Permission/Condition that developers can get to have that kind of Access.
If I understood you correctly, you are trying to built an app similar to the core functionalities of Instagram (or most of it!).
As you have said, they have introduced Sandbox features post November 17th, so any app created after that date will be running in Sandbox mode until you give it for a review.
Few things to note here:
They are restructuring their APIs, meaning there are lot more restrictions and validations!
I'm not sure, but if you search on Google about their restructuring of APIs, it clearly states that Instagram is trying to block an app which has most of the core functionalities of it - likes/posts/feeds etc. This is to secure their users' data and prevent malicious activities.
Most of the endpoints are restricted and some of the old ones are slowly being deprecated.
So, I guess from now on you can't build an app on Instagram which is similar to theirs. Regarding the existing apps which does the same, they have to remove those deprecated endpoints as these new features will be imposed on them post 2016!
At the moment, you can the endpoints available to you are documented on http://instagram.com/developer/endpoints/.
Hope it answers all your queries!

REST API for Whiskerboard

I need some help with implementing a status board with a REST API. I've already found the two best options (in my opinion): Stashboard and Whiskerboard.
I have already tried Whiskerboard and I find it easy to install and deploy because it does not need Google App Engine's SDK to be used locally. However, I need something like Stashboard's REST API: http://readthedocs.org/docs/stashboard/en/latest/restapi.html
I know that Whiskerboard is based on Stashboard so probably they have the same REST API. But I cannot seem to find any documentation on Whiskerboard's REST API. Moreover, I looked into each status board's models and there are lots of differences, with Whiskerboard's being largely simpler compared with that of Stashboard's, so they must not have the same REST API.
I will appreciate it if anyone can provide me a link to Whiskerboard's REST API which should be much like Stashboard's. If there really is none, some other solutions could still be suggested. Thank you in advance!
No, it doesn't have the same REST API. You could find this out by reading the code. If you want a similar REST API you have the following options:
Code the feature yourself.
Ask the developer of Whiskerboard for the feature.
Ask someone else at your organization to code and contribute the feature.
Good luck.
You can check out this solution forked by sijis and myself, jvasallo, that we have been working on. He forked the repo for whiskerboard and added an API to it. Still uses Django, and recently I did some work porting it to 1.5.1. Initially, Whiskerboard is a 1.3 Django app.
https://github.com/sijis/whiskerboard

How To Get Started Working with the Google AdWords API?

I'm a student working on a project related to SEO; I need to write an optimization tool, so I'm writing an application using C# and Windows Forms. The main part of the application is for keyword selection, and I want to use the Google AdWords API to obtain a list of keywords.
I downloaded the C# client library, but can't understand how to set up the project: I am getting the error:
"An API exception has occurred. See ApiExecption and InnerException fields for more details".
Maybe I have made a mistake when I edited the App.config file as I haven't changed anything else. Can anyone advise me where I should begin? I would be grateful to hear your ideas.
Unfortunatley, the AdWords API isn't as open as you might think: It's meant for ad agencies managing large accounts, or software vendors who want to build ad management platforms. You need to apply to Google for an API key to gain access; they used to give them out to nearly anyone with an account, and it took about 14 days to process the application. However, Google has got very strict about their terms and conditions over the past 12 months, and to put it simply, you probably won't meet them if you're building an SEO tool; even if you apply to build a full platform, you'll need to wait six to ten weeks for approval as they've got a huge backlog of applications to process at the moment.
As this is just a student project, you should actually be able to get away with just using the AdWords API sandbox, which is open to anyone with a Google account. This won't give you real keywords or stats, but would demonstrate your understanding of the platform.
Another option would be to check out the Ad Intelligence Service of the adCenter API; you'd still need to open an adCenter account (with a $5 activation fee), but you should be able to get an adCenter API key without waiting too long. The stats available from Microsoft won't be as extensive as what Google has to offer, but will still be relevant to the at least the US market. Also, being Microsoft, they've got a good range of C# examples.
You could use the sandbox, but it is good only for testing purposes. You won't get real values for traffic estimation and keyword ideas.
To use the sandbox, what you need is a Google account (your gmail account for instance). To initialize the sandbox,
In your App.config, put email/password/developerToken as your email / your password / youremail++USD (e.g. john.doe#gmail.com++USD)
Run the GetCampaigns.cs code example. It is under v201109/BasicOperations folder in the C# examples project. This will initialize the sandbox.
Run the GetAccountHierarchy.cs code example. It is under v201109/AccountManagement folder. This will give you 5 client emails and their customer ids.
Use one of these customerIds in the ClientCustomerId field of App.config.
Run any other code example.
The video is a bit outdated, due to recent changes in AdWords API, I need to update it.
you can find a very good article series about adwords api there: Google Adwords API
it is not that hard to learn how to use it! I think the API itself is very good documented and there is a good suppo from google.