Google Places API for iOS Quota - ios

We have an iOS app which uses Google Places API for iOS. We realized upon launch that we receive more than a 100 requests in a day which is causing our app to break because we reached our limit.
Now, we've increased our limit with the help of Google and I want to know if already generated API keys will be affected or we have to generate new API keys .
Also, where can we see the quota used on the console. because what we have currently shows 0/150000

Yes, your already generated keys should have the new limit of 150,000.
Also, for the quota, it does not update immediately, you'll have to wait a bit till they start showing up.

Related

YouTube DataApi v3 subscription limitations

I am using https://developers.google.com/youtube/v3/guides/push_notifications to continually monitor ~ 2,000 channels for new videos etc.
Up until last week, I wasn't having any problems, with pubnubsubbub, however, for some reason, I am getting 403 when I am trying to access (via curl or requests) https://pubsubhubbub.appspot.com/subscribe saying nothing more than
<p>
<b>403.</b> <ins>That’s an error.</ins>
<p>Your client does not have permission to get URL <code>/subscribe</code> from this server. <ins>That’s all we know.</ins>
</p>
So my questions are:
is there any limit (either IP or time or quota) that is documented somewhere and I am somehow hitting? As xml calls were "unlimited" and i do not see any difference in the official YouTube Data Api documentation
have somebody found a better pub/sub channel (either paid or not) with YouTube DataApi 3
if somebody had a similar situation, how long my "ban" will stay
As suggested by Marco Aurelio, I am adding my solution.
My VPS provider had some bans from Google on their IPv6 network in the data center where I had my server running. Thus by contacting them and fixing my network settings the pubsubhubbub continued working without issues.
So the tip for future debuggers stumbling upon here is trying to curl any other Google API (e.g. a function) that you are 100% sure it works and if you are still getting 403, then your IP address range is blocked for some reason (like data center ban in my case).
If you continue to have the problem and getting the "notification" with a maximum delay of 6 minutes isn't a problem, here is a workaround.
I don't use pubsubhubbub but you can simulate its advantages. Indeed you have 10 000 quota a day, using PlaylistItems: list with the uploads playlist of the channel found with contentDetails in part by using Channels: list.
In that way you can check for new videos for 50 YouTube channels for 1 quota so if you want to check your 2 000 channels you have to spend 40 of quota.
If you want to uniformly check during the day you can so make 250 global checks a day, so every 346 seconds (almost 6 minutes).
Of course you have to store your last videos found for a YouTube channel in order to check if there is any difference during your new global check.
If you just want a boolean response whether or not your current request response is different from the previous one, you can check the etag.

What are good guidelines to avoid getting locked by twitter API with a newly created bot?

I have finished creating a bot and got blocked 1 minute after I finally got it to work. The account is now restricted.
this is what I get on my terminal if I try to run the bot now:
tweepy.error.TweepError: [{'message': 'Application cannot perform write actions. Contact Twitter Platform Operations through https://help.twitter.com/forms/platform.', 'code': 261}]
I understand Twitter may restrict new bots for several reasons. I have summited my report to try and get my account unrestricted.
What are good do and don'ts for bots?
In my original bot I was replying every 10s was this too much ? Should I had set a different time frame?
https://help.twitter.com/en/rules-and-policies/twitter-limits
Relevant parts:
Tweets: 2,400 per day. The daily update limit is further broken down into smaller limits for semi-hourly intervals. Retweets are counted as Tweets.
These limits include actions from all devices, including web, mobile, phone, API, etc. API requests from all third-party applications are tracked against the hourly API limit. People who use multiple third-party applications with their account will therefore reach the API limit more quickly.
What happens if I hit a limit?
If you do reach a limit, we'll let you know with an error message telling you which limit you've hit. For limits that are time-based (like the Direct Messages, Tweets, changes to account email, and API request limits), you'll be able to try again after the time limit has elapsed.
10 seconds is too much.

youtube data API not resetting quota

since 3 days the youtube Data API v3 keeps returning the same quota exceeded errors. I made some changes to drastically reduce the number of calls to the API yesterday, hoping it would reset at midnight pacific time today, but no such luck. Could somebody please look into this. The project ID is (removed), project number is (removed).
Thank you.
#TotallyFuzzy I am having same issue yesterday and when I looked into quota the daily limit was set to 0 in my google admin console and there was no way edit,
so in the end I removed and recreate the youtube API in developer console
that fixed the problem for me, here is the screenshot of new youtube API quota

Google Static Maps for iOS

I use the static map google webService in my iOS app.
And when i read the google document of the static map, i found this Note:
https://developers.google.com/maps/documentation/staticmaps/?hl=fr#Limits
The Google Static Maps API has the following usage limits:
25 000 free static map requests per application per 24 hour period.
Additional image requests can be purchased on a per application basis at the rate currently listed in the FAQ. Additional quota is purchased through the API Console and requires the use of an API key.
If a user exceeds these limits, the server will return an HTTP 403 status.
Then i created an app that sent more then 25 000 request to the WebService,
but my application from the other devices and the iOS still working without any problem.
Please someone can explain to me, what the static map WebService work, because i reached the number max of the request/application and my ios App still work on the other devices ?
From an ip or from a device number of free request that can be made from google is 25000 request only per day after this you have to pay to google for it. So answer to your question is request from a particular ip is considered for calulating total requests.

Google Maps SDK for iOS - Delivery Timeframe

I'm wondering if anyone has requested and actually received an API key for the Google Maps iOS SDK. I put in my own request over a month ago now, and still nothing despite having a shipping app that is ready to make immediate use of the new SDK (and which is picking up some negative feedback due to inaccuracies in Apple's maps).
Has anyone been issued an API key for the Google iOS SDK, and if so, how long did you have to wait for it and what were the circumstances of your application (i.e. did you have an app already deployed, how popular was it, etc.)?
I'm hoping that if we can unravel the criteria Google uses to issue these keys we can allow people with pending requests to come up with an approximate estimate of when their request might be granted.
As I mentioned in this answer, I applied for access on the 13th of December, and then received an email saying I'd been approved on the 17th of December.
I have an app on the app store which used to use Google Maps, but I had to remove the maps when iOS 6 came out. Not sure if this had anything to do with it, or if I was just lucky because I happened to hear about the SDK almost immediately after Google announced the new SDK, and I applied for access right away.
When I received the email saying that I'd been approved, I was added to a google group - which is how Google sends out notifications of updates. From the looks of it that group only has 77 members, so if that's equal to the number of people which have been given access, I guess Google are rolling out access quite slowly.
UPDATE:
As of the 21st of February, it looks like the SDK is now open to everyone.

Resources