Open qenu opened 3 years ago
I can see the thinking here. I'm thinking there'll need to be a bit of discussion around design of how this would look.
For example, I'm thinking this could be something done as a key in the cog's info.json
but that would cover the third-party stuff, not the built-in necessarily
Type of feature request
Other
Description of the feature you're suggesting
I am proposing that we should add a section in the document, or link a new page for shared-api-keys As it is crucial for cog creators to use the same key values for shared-api, making a list of existing key and api structures to prevent small differences in api namings
For example it could be something like:
List of existing shared api keys
Twitch API
https://dev.twitch.tv/docs/api/ API from twitch used to certifying twitch dev applications
key
parameters
YouTube API
...
Anything else?
No response