Tale of how Google billing has changed, or how to avoid unnecessary costs

Hello. On one of the web projects we use the Maps jаvascript API, but after the charging change from July 1? 201? something went wrong. We share our experience so that this does not happen to you.
cloud.google.com provides the ability to use different APIs. There are many of them; it makes no sense to list everything - but we use the Maps jаvascript API cloud.google.com/maps-platform/maps .
3r3146. API services are managed through a completely understandable GUI with the dashboard of the used services 3r-328. console.cloud.google.com/home/dashboard
3r3146. Integration for different clients is done differently. In our case, simply place the JS widget according to 3r3333. developers.google.com/maps/documentation/jаvascript/tutorial
From July 1? 201? the pricing conditions became the following - 3r3342. Clack 3r3161. .
If in short - then the billing occurs within some “food packages” (in fact, a combination of API), and each product set can be charged in its own way under certain conditions. A monthly loan of $ 200 is allocated, which is taken into account when charging services.
Conditions are accepted, the card to the payment account is tied up, let's go. All screenshots are made from the console, the project is the same, smeared by NDA.

Funny pictures

Introductory 1 is a general view of the control panel used by the Maps jаvascript API
Introductory 2 - used methods that we can control from the console.
Tale of how Google billing has changed, or how to avoid unnecessary costs

Introductory 3 - indicators on the use of r3r3127.  

Introductory 4 - billing report
After reading 3r3134.
description. , we appeal to Google support, since we didn’t connect the Maps and Street View API. We get the answer literally:
3r395. I would like to make a jаvascript API. Maps and Street View API jаvascript API. I would like to use the jаvascript API usage instead.
We do not give up and try to figure out further, we get this clarification:
In parallel, we read Document 3r3161. Once again we find the following (we read, including the paragraph above the table):
Well, they did not understand themselves in tariffing, what is the moral? 3r3122.
The moral of this story is that
3r3146. Previously, the Street View API was connected separately (and in fact it is still possible to connect it). Now it is, in fact, part of the Maps jаvascript API (although it is charged as a separate API). And if for some reason you did not take this into account and relied on tariffing either for 3r3-332.
calculator. , or according to the description 3r3134. hence r3r3161. and did not consider the use and pricing of the Street View API - be prepared to detect unplanned costs.
3r3146. In addition, budget alerts work including. taking into account a loan of $ 200. Those. at setting alerts be sure to consider this.
3r3146. If you do not need to give the possibility of panoramic view of the streets in the maps - just remove the call to these methods.
3r3146. Restricting the call to the Street View API (at the level of key usage or console) is impossible except for the logic of the calls themselves on the client
! function (e) {function t (t, n) {if (! (n in e)) {for (var r, a = e.document, i = a.scripts, o = i.length; o-- ;) if (-1! == i[o].src.indexOf (t)) {r = i[o]; break} if (! r) {r = a.createElement ("script"), r.type = "text /jаvascript", r.async =! ? r.defer =! ? r.src = t, r.charset = "UTF-8"; var d = function () {var e = a.getElementsByTagName ("script")[0]; e.parentNode.insertBefore (r, e)}; "[object Opera]" == e.opera? a.addEventListener? a.addEventListener ("DOMContentLoaded", d,! 1): e.attachEvent ("onload", d ): d ()}}} t ("//mediator.mail.ru/script/2820404/"""_mediator") () (); 3r3154.
Only registered users can participate in the survey. 3r3-3160. Sign in 3r3161. , you are welcome. 3r3162.
My project uses maps
Openstreet maps
No one has voted yet. There are no abstentions.
+ 0 -

Add comment