On Oct 15, 9:37 pm, "Webmaster brouw-bier.nl" <[EMAIL PROTECTED]> wrote: > The old key was: > ABQIAAAAO6WVRbbJF3rimaZ9g9yRcBQGaqEdwtsnzxBDNY4mtBFQHu6UEBTMvPwKZgQPu3SboDv0X_2nVlkdIQ > The new key is: ABQIAAAALUTOmqv7- > sI_jPpHAzt9yxQGaqEdwtsnzxBDNY4mtBFQHu6UEBTn2zfCre8jp035EWk8AQoG0DFoPQ
Those keys were generated for the same URL/domain, but using different Google accounts. Keys are 86 characters long. The first 8 are always ABQIAAAA; characters 9 to 30 relate to the account used to generate the key; characters 31 to 59 relate to the URL; and 60 to 86 hash everything together. Using this key system it's possible to verify that the key relates to the domain of the map, and to identify which Google account is responsible for that key. So if Google identify a need (eg a violation of the TOU) it's possible to block access to the API for a single domain, or for a Google account and ALL its keys. I've never seen the message generated when a key has been blocked. It's possible that it's just the standard message you saw. But getting a "wrong key" message with one key and not with another for the same domain but generated with a different account might suggest that the first account had been blocked for some reason. And if they both work now, then the block has been lifted. Andrew --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google Maps API" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/Google-Maps-API?hl=en -~----------~----~----~----~------~----~------~--~---
