javascript - Google maps API vs Library -


what difference between google places api , google places javascript library?

the documentation library doesn't talk api keys, , developing locally seemed work fine without one. shortly after deploying web app, started throwing following errors:

get http://maps.googleapis.com/maps/api/js/authenticationservice.authenticate?1shttp%3a%2f%2fopensaq.dev%2f&5e1&callback=_xdc_._obke7w&token=16494 403 (forbidden)  https://maps.googleapis.com/maps/api/js/placeservice.findplaces?1m6&1m2&1d4…saq&6sliquor_store&8e1&18m2&1b1&10u43536&callback=_xdc_._266p5k&token=1150 403 (forbidden)  http://maps.googleapis.com/maps/api/js/quotaservice.recordevent?1shttp%3a%2f%2fopensaq.dev%2f&4e1&5e0&6u1&7s2v1zkm&callback=_xdc_._dacmzn&token=54694 403 (forbidden) 

did exceed quota or something? each option intended for?

the library javascript api make working api javascript easier, has set of objects replace direct api calls. call api, have conform requirements of api limits. library may download related js libraries needed perform operation too.

these rejections in theory js library relationships failing download, appear api rejections. due limit, or firewall restriction (if have 1 or proxy in place). depending on requirements of api, require signature generated, , if missing, forbidden too. in documentation returns 403; api documentation spells out.


Comments

Popular posts from this blog

javascript - jquery or ashx not working -

opencv - DataType<cv::detail::deriv_type>::depth what is it used for -

python 3.x - Mapping specific letters onto a list of words -