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
дана 23. септембар 2012. у 12:05 PM
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
дана 23. септембар 2012. у 1:37 PM
thanks!
Одговор од rclai
дана 01. август 2015. у 6:22 PM
Travis,
If I expose my API key in the client-side, is someone able to take it and use it somewhere else?
Одговор од Travis Bell
дана 02. август 2015. у 10:55 AM
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
дана 02. август 2015. у 6:41 PM
Thanks for the answer. I guess the IP based rate limiting helps relieve this issue too.