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
找不到电影或节目?登录并创建它吧。
Travis Bell 的回复
于 2012 年 09 月 23 日 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.
happycrappy 的回复
于 2012 年 09 月 23 日 1:37下午
thanks!
rclai 的回复
于 2015 年 08 月 01 日 6:22下午
Travis,
If I expose my API key in the client-side, is someone able to take it and use it somewhere else?
Travis Bell 的回复
于 2015 年 08 月 02 日 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.
rclai 的回复
于 2015 年 08 月 02 日 6:41下午
Thanks for the answer. I guess the IP based rate limiting helps relieve this issue too.