What are the 'subtle changes' in Google Spreadsheets API? - google-sheets

Google is upgrading old spreadsheets to the new version of Google Sheets.
This is beginning to screw up a web service I'm running that uses the Google Spreadsheets API. I need to quickly make some code changes so it understands the new API, but I don't know where to start.
The above linked has only this to say:
APIs — You may notice some subtle differences in API behavior.
What are these 'subtle differences'? Why can't I find a list of what has changed?

Well one thing that changed is it no longer suports the old way of authenticating. You now have to use OAuth. I think this is where my problem was.

Related

Keywords Planner in Google Ads API

I am trying to use Keywords Planner programmatically, through its API.I came across Generating Targeting Ideas, which pretty much summarizes the use. When I visit Get Started, it states
Try the new Google Ads API—which has the latest Google Ads features. The AdWords API is in maintenance mode and not being actively developed.
I visit Google Ads API, where I cannot find anything related to the Keyword Planner.
Has someone any idea if the planner is available through the new API, or do I have to use the old one?
Thanks,
Alexios
I'm currently working on converting an old Adwords cron job to the new Ads API. While I'm not sure if this is exactly what you're looking for, the old TargetingIdeaService has been replaced with a new KeywordPlanIdeaService (see https://developers.google.com/google-ads/api/docs/migration/services).
You can find examples for KeywordPlanIdeaService here:
https://developers.google.com/google-ads/api/docs/samples/generate-keyword-ideas
Pay careful attention to how the code formats each selector field and using a helper class to format language and geotargeting codes. It's not the most intuitive way of passing paramters.

What is a good strategy for staying up-to-date with external API's?

My project is reliant on several API's, like Twitter and Youtube for example. Recently, Youtube deprecated their old API, and it caused issues with my team's iPad app.
We could have stayed ahead of the change if we were paying attention to Youtube's announcements of the upcoming deprecation. But alas, we were not and the idea of staying up to date with all of our dependencies manually(browsing the web) seems exhausting and inefficient.
I have found the following tool to help notify when changes occur with external library dependencies, https://libraries.io. However, this does not help with API dependencies.
Besides checking the API source webpages every so often, I was wondering if anyone had suggestions on how to stay notified and up-to-date with news regarding updates to a specified list of external API's?
After some time looking at different options, I have found a solution that is not perfect, but seems to work best at fitting this need.
Solution Description
This solution uses a combination of Twitter, Google Scripts, and website blogtrottr.com. I am creating a twitter list of reliable dev handles that often post updates on new API. For example I made a list that contained #twitterapi and #YouTubeDev. Used Google Scripts to create an online feed out of the twitter list. Then used blogtrottr to email me every time that feed gets a new posting.
Steps to Implement
Create a twitter list of reliable handles that often post about updates to their API
Create an RSS Feed from that Twitter list. The details for how to do this can be found here.
Plug that url that you get from Google Script into blogtrotter.
I did find some other ways to do this, but so far this is the only solution that was 100% free!

google image search API for iOS app

I am creating an application in which I am trying to implement google image search using Google- image-search API. I refer this [google API link] (https://developers.google.com/image-search/v1/) . But I have one problem, on that page, mentioned (DEPRECATED). So can I use this API or I should use other API? Can anyone knows about this?
Thank you in advance
If APIs are deprecated they may work for now but not with full features and may go offline in near future.
If you go to https://developers.google.com/image-search/
It says its Deprecated and the number of requests are limited now.
Important: The Google Image Search API has been officially deprecated as of May 26, 2011.
It will continue to work as per our deprecation policy, but the number of requests you may make per day may be limited. We encourage you to upgrade to the Custom Search API, which now supports image search.
Here is the link to Custom Search API
https://developers.google.com/custom-search/
Hope it helps
Deprecated means it is older one also it means that there exist new version code for that. Check this out.
Example:
For example, in order to change our search engine from webresults-based to image-based, we can utilize the defaultToImageSearch attribute.

Which fusion tables maps do I need to migrate

I'm unsure if the maps I have created through the last years will work when the Google SQL API is shut down January 14th.
I have read about the migration process and I understand it should be straightforward. I don't think so.
Where can I in the code see if I have to change the code?
Some of my maps I have build with the help of the FusionTablesLayer Wizard.
Other maps I have build by using maps and templates I have found and changed. I have made it work, but I won't say I understand everything going on in the code.
I don't see an api key anywhere in the code of my maps. And that makes me unsure if I need to change anything.
Will this for instance work after January 14th:
http://www.kaasogmulvad.dk/unv/fusion/test.html
and what about this:
http://www.kaasogmulvad.dk/unv/3f/projekter1.html
Any help is much appreciated.
Neither of the examples you reference use the FusionTables SQL API. That is an external API for accessing data stored in FusionTables. Both of your examples just use the FusionTablesLayer from the Google Maps API v3.

Google Places API Violation

I am using Google Places API to pull a list of resturants, and I am displaying them on map. However, since Apple has switched there map services over from Google in iOS 6.0, I am now in violation of Google's terms of use, which states that you must display Google data on a Google map.
"If your application displays Places API data on a map, that map must be provided by Google."
https://developers.google.com/places/policies#terms_of_use
I obviously need to change the map, because I am not going to release an application that is in violation. Any thoughts or suggestions on what to do? Should I go Google Maps with a web view? Does apple have some sort of Google Places API alternative?
Edit:
Using Google Maps through a web view is a hassle, i'd like to find an alternative to that, although it would technically work.
I decided to use Google Maps JavaScript API. Although, it is a little more difficult to deal with, mainly the JavaScript through Objective-C, it is a solution. The map is displayed through a web view, and I use JavaScript to interact with the map.
https://developers.google.com/maps/documentation/javascript/tutorial#api_key
I will wait to accept this answer, to see if anyone else has any thoughts. I just wanted to post this, in case it helps someone else.
Edit:
Google recently released a Maps SDK for iOS, this is the better solution now.
https://developers.google.com/maps/documentation/ios/
I would try to directly contact Google, explaining the situation, and ask them for written permission to use Apple's maps. This is more a legal question than programming. One would think that Google is aware that you can no longer display their maps using Apple's API and that, even regardless of the map, they would want you to use their places, as doing so generates advertising revenue for them.
Agree with #Owen here - you could get permission to leave your app unchanged until some possible future date when you might have to change it, or could you definitely go to the effort of changing it now and then possibly have to change it again in the future for some other reason.
If you could get a 100% guarantee that you could change it once and never have to change it again then I'd say do it now, but nothing's certain.

Resources