google image search API for iOS app - ios

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.

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.

Delete channel in Slack API

I am finishing development of API similar to Slack API, but with more/different features. I have to implement an API (more like command/endpoint) for deleting a room and I can't find anything like that in the documentation.
It seems that it can be done via webUI according to this help article.
But there is no method for it in Slack API methods.
I think there is only channels.archive with similar purpose, but it seems very strange not having a method to delete a room.
Is it really like that that room can't be deleted via Slack API?
There is no method for deleting a channel in the official API, but there is the undocumented method channels.delete that has this exact functionality.
Basic usage is:
https://slack.com/api/channels.delete?token=TOKEN&channel=C12345678
Please note that undocumented methods are not officially supported by Slack and might change or stop working without any prior warning. Still, they are very useful and I have made a github to document all known undocumented methods. Please feel free to use and contribute.
Tried it today 2nd June 2022 and it responds with 'unknown_methods', I guess it's outdated now.

What are the 'subtle changes' in Google Spreadsheets API?

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.

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.

Problem with Bing.AdvancedSearchBox helper method

Is anyone else experiencing problems with the Bing helper in Microsoft.Web.Helpers?
The Bing.AdvancedSearchBox helper method tried to load the following javascript file but throws a 404 error. The script is http://www.bing.com/bootstrap.js
Has anyone else experience the same problem? So far there has not been any updates to the microsoft-web-helpers package in Nuget. Any information is greatly appreciated.
Thanks,
Diego.
UPDATE 5/1/2011
I found the following official statement...
I wonder when Micorsoft will release an update to Microsoft.Web.Helper to remove the deprecated functionality.
Note: Bing team at Microsoft announced that they will be shutting down siteowner service on April 4th. This will prevent you to use the AdvancedSearchBox feature of Bing on your website/blog or web applications. Here is the quote from Bing's official blog:
As of April 4th, 2011 we will discontinue support for the bing.com/siteowner functionality. If you continue to leverage the feature after this date (April 4th, 2011), users who attempt to query in the search box will be redirected to a 404 page. This means that you will need to move to the Bing API in order to continue to receive web or site search results from us. We have decided to take this step for two reasons.
First, the tool has not been getting a lot of use and while we have some very loyal customers on it, we believe we can provide you better alternatives in the future as we free up resources.
Second, the functionality available through bing.com/siteowner can be replicated with the Bing search API and so it feels a bit redundant.
As has become customary, we will give you a window to migrate off and ask us any questions you may have about this change. We will also provide reminders as we get closer to April 4th. Thank you so much for your support.
It looks like something has changed on the bing servers and this script no longer exists.

Resources