Manage more one access_token for unique user and application

[BarryCarlyon]

@Sylvanus

I understand, however my two applications cannot communicate well. One is a bot for discord which can interrogate the API and the other is the bot rated TMI which may also want to obtain information on the API.

If your access token(s) are stored in a database, (and everything is on the same server for simplicity), then both separate processes can read the token from the database, and you use one service (or the other) or make another service for Key management.

Which comes back to the Web portal I suggested in the other thread.

• Web Portal - manages generating and refreshing keys, stores keys in database (or flat file)
• Discord Bot - reads the key to use from database (or flat file)
• TMI Bot - reads the key to use from database (or flat file)

@Sylvanus

The solution to create two applications on the Twitch side, with different client_id and client_secret is not good either I imagine?

Then you are managing two clients and making things harder