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
¿No encuentras una película o serie? Inicia sesión para crearla:
¿Quieres puntuar o añadir este elemento a una lista?
¿No eres miembro?
Contestado por Travis Bell
el 23 de septiembre de 2012 a las 12:05
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.
Contestado por happycrappy
el 23 de septiembre de 2012 a las 13:37
thanks!
Contestado por rclai
el 1 de agosto de 2015 a las 18:22
Travis,
If I expose my API key in the client-side, is someone able to take it and use it somewhere else?
Contestado por Travis Bell
el 2 de agosto de 2015 a las 10:55
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.
Contestado por rclai
el 2 de agosto de 2015 a las 18:41
Thanks for the answer. I guess the IP based rate limiting helps relieve this issue too.