Hi,
I was wondering how guarded should my api key be? Is it ok to expose it to my users to be consumed by javascript (ala google maps key)? or should I consider it a private key that should only reside on serverside code?
If its the latter, whats the recommended method to implement a typeahead/autocomplete search?
Thanks
Non podes atopar unha película ou serie? Inicia sesión para creala.
Queres valorar ou engadir o elemento a unha listaxe?
Non es membro?
Resposta de Travis Bell
no 23 de setembro do 2012 ás 12:05PM
This is always a tricky issue. With any public facing JavaScript project it will be impossible to obfuscate our API key. I realize there is nothing you can do about this.
Just be responsible with it, we offer our API for free so hopefully anyone wishing to use it will simply ask us for a key.
Resposta de happycrappy
no 23 de setembro do 2012 ás 1:37PM
thanks!
Resposta de rclai
no 1 de agosto do 2015 ás 6:22PM
Travis,
If I expose my API key in the client-side, is someone able to take it and use it somewhere else?
Resposta de Travis Bell
no 2 de agosto do 2015 ás 10:55AM
Hi rclai,
Yes, someone would be able to. The thing to keep in mind, which is why we don't generally regard this to be a big problem is that we offer the API for free. Everyone can sign up an account and request a key themselves.
Cheers.
Resposta de rclai
no 2 de agosto do 2015 ás 6:41PM
Thanks for the answer. I guess the IP based rate limiting helps relieve this issue too.