In youtube interface if we search for a term with spelling mistake, Interface provides an option to "search instead" for a similar term. for example
poovin maarile search gives you results for poovin marile
but while using youtube api version 3, poovin maarile gives zero results and poovin marile gives 230+ results. But there is no way in the api to get this very closely related term.
I am aware of spelling suggestions feature in version 2 but since version 2 is deprecated I am not interested in using it. Is there something similar for youtube data api version 3?
I don't think there's an official API for this at the moment.
You probably shouldn't rely on this being available in the future, but I think the only alternative at the moment is querying the same URL that YouTube and other pages use.
From another question: Youtube API search auto-complete
A page detailing the query parameters: Google Autocomplete API
Related
Freebase will be deprecated starting Tuesday, March 31st, what does this mean for topic based searches with the youtube api? Will these queries still work?
https://www.googleapis.com/youtube/v3/search?part=snippet&relevanceLanguage=en&topicId=%2Fm%2F04qf57&type=video&videoSyndicated=true&key={YOUR_API_KEY}
I think this will be unaffected since Google Knowledge Graph API, which is the replacement of Freebase, is able to search by topicId too.
Do not quote me on this one though as there's really no documented change notes on the Youtube Data API
Also, some SO posts that contains discussions regarding the possible impact and alternatives(as of the moment) to the use of Youtube Data API and topicIds can be found here and here
I've been using the old url api(v1) to get the count of a given url, lately I needed to get also the re-tweets and started searching about that.
this is the exact url I'm using right now:
http://urls.api.twitter.com/1/urls/count.json?url=http://google.com
As I viewed with some reading the v1 api is deprecated but at least it's still working.
I found some questions on the dev page of twitter:
https://dev.twitter.com/discussions/12643
those are a little old questions and have no specific solving to the problem. I mean, the most near solution was using the search api(search/tweets) which could be good but not a exactly replacement for the urls/count method.
Please note that Twitter's search service and, by extension, the
Search API is not meant to be an exhaustive source of Tweets. Not all
Tweets will be indexed or made available via the search interface.
also it has a limit for 100 results at maximum per 'page', even it throws the link to get the next set of objects, thats good but when the search reaches 1 million of results I'll need to get page over page to now how much tweets I got and having to do to much request to the api...
I sought some question over the dev page on twitter suggested using the stream api, I've tried using (statuses/filter) but that don't work very well given a URL as track param(which they said that is the keyword to track).
So, anyone who's been using the old urls/count has found a reliable alternative with the new apiv1.1, especiffically to get the tweets and re-tweets for a given url ?
The official suggestion by Twitter staff is that either the search/tweets endpoint (having just the last 7 days data) or the Streaming API be used (handling yourself the counters, making everything just too complicated for a d*mn counter).
As an extra warning, the old endpoint (http://urls.api.twitter.com/1/urls/count.json?url=YOUR_URL) will stop working on November 20th, and according to this blog post from Twitter there are no plans to replace it with anything in the short term and they are even removing the count from their own buttons.
I had a working script written in PHP YouTube API 2.0 that would retrieve a feed of videos based on a search query.
Over the couple months it has been getting choppy and it won't consistently retrieve the amount of video views that each video has which is messing up my website.
Does anyone have or know where I can find a working Zend PHP YouTube API 3.0 example that will retrieve videos based on a specific search query?
Anything helps!
Check https://developers.google.com/youtube/v3/code_samples/php
But be aware, that the V3 is still "experimental" and therefore some things might not work as expected ;)
you can find many code samples like https://developers.google.com/youtube/v3/live/code_samples/php
Getting started - https://developers.google.com/gdata/articles/php_client_lib
YouTube API Samples project has a great example. Make sure, you enabled Data API v3 in your dev console first. Also Data API v3 is highly supported and not experimental anymore.
Is it possible to get all comments for a video with the new (experimental) YouTube API v 3.0?
I only found how to get "activities" (in their terminology comment is a kind of activity) originating from a given account.
The api page says the api is not feature complete, so it is quite possible that functionality is not yet made available. Although I might've just missed it.
There's no support for retrieving comments using v3 of the API. We can't make any commitments to add in support for reading/writing comments at this time, so if your application depends on them, using v2 is required.
I have been trying out the youtube API with Java. When I do a search using the API I don't get the same results as when I just type the keyword in the browser, any logical explanation why this is?
Compare: http://www.youtube.com/results?search_query=blah+&aq=f
http://pastebin.com/FVRd3URT (list of video Titles)
I also noticed that some videos (or at least their title) are duplicated.
YouTube API version 3 gets the same search results. Version 3 is still experimental, according to the documentation. https://developers.google.com/youtube/v3/docs/search/list
No, it's just how it is. Trying to match up the two is a futile exercise.
Amazon search has the same problem.
This demo might help.
https://github.com/bitsabhi/YouTubeDemo
A java project to return title, album, you tube link when the user searches for any songs. Uses You tube search API.
I have the same problem.
It is as if the API queries don't support full text search - results through the API are the same as if you enter "my search query" in quotes.
Although, try setting a slightly larger time frame: 'today' might be different from 'last_week', and you may get more relevant results.