Jarec-au
commented
4 weeks ago You shouldn't need to enter the API key at all, this field is just there because it's something that was required for the 1.0 API (which is in old teams and microsoft don't support that anymore).
- Make sure that API 2.0 is selected.
- Clear the API key field (I don't believe this matters, but just in case)
- Make sure your target IP address is 127.0.0.1 and save (It won't work yet)
- Open teams, go to Settings -> Privacy -> Scroll down and press Manage API
- Make sure Enable API is selected.
Start a teams meeting (you can just set a meeting with yourself and join it). Once you're in the meeting, press a button to send a command, Teams should pop up and ask you to approve the device. You should then see that device added into the third party API list. By doing this, it will auto populate your API key into the companion config, you don't need to do anything else.
There are no functions of this API that operate outside of a Teams meeting. You must be in a meeting for any of this behaviour to work.
Hi, I have add this module in my connection.
I'am connected via satellite to Bitfocus. The connection I have tried teams 1.0 and 2.0 and the IP 127..... and the IP of my workstation.
Nothing happens. I have follow the instruction to get the API, but the connection in bitfocus still say "Bad Configuration API token is missing"
Now I'm confused.
When I get the Api key to put it in the Connection field?
I have tried it with Streamdeck and teams and there is still generate an entry in teams.