I want to develop some stuff with the twitter streaming API and twitter4j in university. I read now about shutting down the share-count API (https://blog.twitter.com/2015/hard-decisions-for-a-sustainable-platform). Will this effect the twitter streaming API and how it works in any way? Because I need this service for at least 6 month.
The Share-Count and the Streaming API do not cross paths, actually you can obtain the share-count from the Streaming API data as suggested in this post.
Since they are discontinuing that service, it will have no effect on the data that you're able to obtain from the Streaming API so it won't effect the progress of your project.
As far as GNIP goes, that's overkill, it should not have been suggested at all. For research base, especially during initial stages and possibly later phases, the Streaming API will provide you with excellent amount of data. You can even request a limit increase through Twitter's Sale Department but it's up to them to make the final decision. They can be contacted at data-sales#twitter.com
Share count and streaming are totally separate APIs.
If you need guaranteed access, I suggest paying for Twitter's GNIP service - https://www.gnip.com/
Related
We are building an application that manages video campaigns on DV 360. It includes uploading and changing a lot of YouTube videos on a daily basis.
We found that the YT Data API allows us to upload about 5 videos daily before we exhaust the API quota. We requested an extension via the public form. But there is no public information about the SLA for that form or how to get additional Dev support with the API. Which we will need, as our use case is different from the typical API user (apparently).
Has anybody gone through this process successfully and/or found a way to get Dev Support from Google for the YouTube Data API?
Thanks!
Your questions are indeed very much pertinent.
I can state -- based on my experience monitoring the tags youtube-data-api and youtube-api for more than three years -- that there's no official info related to SLAs and Dev Support here on SO.
The YouTube Data API is officially a free of charge API. But that does not exclude the possibility of Google offering this API under different conditions to clients willing to pay for the services provided to them.
I'd recommend to address your issues directly to Google, either through its own issue tracker site, or through its own support forum.
I requested more quota and after months of back and forth YouTube decided to revoke my API key for 'reverse engineering' the API. I am not intending to reverse engineer anything and followed the developer policies closely. My app is described at https://playsiv.com
Can anyone help guide me as to how to open a line of communication with the API team so I can resolve their concerns and obtain the desired quota limit to launch my app.
Thanks!
(Disclaimer: Please note the fact that I'm not a Google employee, neither am affiliated or connected in any way with this company; am only using its public APIs, as many others do.)
A first question that pops into my mind: are you using web-scraping over YouTube? That's forbidden by section III.E.6 of DTOS.
To my understanding, your app employing reverse engineering (if it actually does that; I cannot know) means that the app makes use of undocumented YouTube APIs. That's forbidden by section III.D.7 of DTOS.
A first look at one of app's web page made me think that the app downloads video content from YouTube -- if it does not, I honestly misunderstood that page's descriptions. Downloading video content from YouTube does imply using undocumented APIs and, indeed, reverse engineering.
I'm building a website that will eventually host educational how-to videos that intend to charge for via subscription based services. I am using Firebase and have done some research for the best ways to do this.
I've come to the conclusion that hosting videos on your own storage isn't trivial and cost efficient. So my question is if using YouTube's API is the right choice?
Here are my pros and cons:
PROS
Leverage YouTube's storage
Better user experience
Option to leverage YouTube platform for views, user signups, traffic, etc
CONS
Need to have users authenticate with YouTube
Privacy of content will be able to be set in two different places (on website thru api, on youtube).
Less reputable business if not hosting own content
I looked around and did not see sites using YouTube in such a way. Obviously if successful the end solution should be in-house, but prior to that it seems like going with YouTube API for a startup is a better choice.
I am going to implement a python client that search videos on youtube with different queries. Apparently I should use youtube data api for this. Even though I read quata cost I just want to be sure that using youtube api is totally free of charge. Sorry it is too basic.
Yes, using the YouTube API does not incur any monetary cost for the entity calling the API. If you go over your quota an 403 Error will be returned by the API.
Links:
YouTube API Quota DetailsYouTube Quota Calculator
Google already provides a Python client for all of its APIs, including YouTube, which handles authentication, forming and making the API request as well as some datatype translation (i.e. JSON to dictionary, etc.). (link)
Yes it is, but some restrictions like limit you can use only 100000 units per day.
and 3000 per second per 100 user per day. For more quotas you have to apply for it. You can apply key or oauth id at HERE. Hope it will help you.
Is there a way to get YouTube audience retention data of a particular video via API? This doesn't seem to be available via API (even in youtube experimental API). Any other way, like parsing the UI data or contacting Youtube to get this data?
Or any idea whether this data will be available via API in near future?
It's a common feature request that we've heard from developers, and there's a good chance that it will be added. I don't have any specific details to share about when that might happen, though.
Your best bet is to file a formal feature request and we'll track things there.