YouTube API Multi-Channel Network Stats? - youtube

I'm looking to obtain basis MCN stats to retrieve info such as:
Total Network Subscribers & Total Network Views
Does anyone know if this is possible & (ideally)
what the query would be to retrieve in JSON ?

Related

I need to figure out the max data ingestion rate for Firehose if I am reading it from a Kinesis data Stream?

The doc state the below:
Kinesis Firehose can ingest only 5 MiB/sec and that the maximum size of a record sent to Kinesis Data Firehose, before base64-encoding, is 1,000 KiB.
Is there a way increase the ingestion rate for Kinesis Firehose ?
Does Firehose also use shards concepts ?
I am forwarding it to Kinesis Data Analytics after filtering data at Firehose.
There is a concept of dynamic partitioning, but that will help you with throughput(but not for ingestion rate).
If you are using dynamic partitioning, a max throughput of 40 MB per second is supported for each active partition. This is a hard limit.
According to the AWS documentation, you can reach out to them to increase the quota.

Understanding Twitter v2 API rate limits for filtered stream

I understand there is no real tweet limit in stream mode rather a limit for connections and filter changes. Is that correct?
There is an overall Tweet cap limit on the standard basic product track of 500,000 Tweets per month with the v2 API.

YouTube Data API is counting too many requests

For the last few weeks, the YouTube Data API (v3) is showing a significant increase in requests. In fact, we hit the 50k quota limit every day, which means that requests in the afternoon/evening tend to fail with a quota exceeded error:
However, this usage count is not correct. We use a single API key for making requests to the YouTube API, and the Google Cloud API counter only shows ~2k uses per day for that API key.
All requests to our server endpoint that calls the YouTube API also pass through Cloudflare, which similarly shows <2k requests per day.
We just make a single request to www.googleapis.com/youtube/v3/search?part=snippet&maxResults=1&... – is it possible that these requests count as multiple queries? Or is there any other reason that could explain the incorrect query counts? Thanks!
This is a recurrent issue with the YouTube Data API quota system, that is caused by confusing terms used within Google's cloud console.
You have to acknowledge that YouTube's Data API quota system is not accounting for the number of queries one is making. Instead, the API attaches to each kind of its endpoint a quota cost, and, thus, is accounting for the sum of quota cost of all endpoint calls one is making.
Moreover, inspecting the quota costs page I mentioned above (or the official doc page of the endpoint for that matter), you'll see that the Search.list API endpoint is quite expensive: 100 units of quota cost.
Consequently, to reach a quota cost of 50000 units, your app has to issue only 500 calls to Search.list (this amounts on average to approximately one call at every three minutes per day).

Twilio API Stats Calls to Retrieve Agent Average/Max/Total Hold Times?

Is there a REST statistics API call that can be made that would retrieve the average, max, etc. hold times for Twilio tasks, queues, or workers/agents?
I see statistics that can show a participant being on hold at the current time, but not for reportable statistics on hold times.
Twilio developer evangelist here.
I believe you are looking for the TaskQueue Statistics API.

Twitter Stream API for Direct Message (DM)

I'm reading DM via Twitter GET API and each time I check for them I consume rate limit, even if I don't retrieve any messages.
I've seen it is possible to read DM through Streaming API and I would like to know if this does not consume rate limit or at least is a separate limit before implementing it, as it will take some time to do it. Also, is it fast getting new DM or it has some kind of delay as it is streaming?
So, in short:
Does Streaming API not consume my GET API rate limit?
Does Streaming API get DM "almost" instantly?
Thank you
Streaming API limits and REST API limits are completely separate entities. Consuming direct messages via a streaming API doesn't consume any REST API rate limits. And the DMs would arrive within a user stream almost instantaneously, provided that the access token used in the user stream connection had the appropriate permission level associated with it.

Resources