Hi, I could do with some pointers on how best to use the API in lots of different clients.
The example here is integrating the freesound library with a game engine. I'm looking to create an addon for a game engine that allows users to browse/search the wonderful library on
freesound.org and use them within game projects.
I can see a few options for handling the API requests and key here.
- Bundle the API key into the addon, and use the same key for everyone. This would mean that all users of the addon would be using the same key, but I think this would hit the api limits quite quickly.
- Create my own endpoint on my server, which acts as a middle man for the requests. This keeps the API key a secret, but still has the issue of hitting limits quickly.
- Ask each user of the addon to request their own API key, and have them enter it into the addon before use. This has the benefit og having per user limits, but requires each user to request their own key.
There are probably a few more scenarios that could be taken.
Basically, I'm really interested in exposing the freesound library to game engines, but I want to do it in a way that doesn't disrupt the platform and is well within the terms of use.
Any pointers on how to start this journey would be really helpful.
Thanks,
Nick