Eagle 3D Streaming has two kinds of key, one kind of token, and a version-control switch. They live in the Developer section of the Control Panel.
| API key | Streaming API key | |
|---|---|---|
| Can delete or replace your app | Yes | No |
| Use in a web integration | No — being withdrawn | Yes |
| Keep it | Server-side only | Server-side, and never longer than you must |
If you have an existing integration using the plain API key, move it to the Streaming API key now rather than when support ends. The change is one value, and the current arrangement means a key with the power to delete your application is being handed to every visitor's browser.
One per account, found in the Developer section.
A token authorises one streaming session. Single use, and it expires if it is not used within the time you set.
That is what makes tokens the right thing to give a browser: one expires harmlessly, where a leaked key does not. Generate them from the Token Generation tab, or from your server as part of an SDK integration.
Because a token is single use, restarting a stream needs a fresh one — reusing the previous token fails rather than reconnecting.
Both keys live here in the Developer section, but only one of them is used to stream. The Streaming API key exists to produce session tokens, and session tokens are a Web SDK concern — an iframe integration and a plain streaming URL use neither. If you are embedding with an iframe or sharing a link, you do not need this half at all.
A switch, and the two behaviours are quite different.
| Version control | Uploading a new build |
|---|---|
| On | Adds a version. Version 3 becomes version 4, and 3 remains. |
| Off | Replaces what was there. The previous build is gone. |
With it off there is nothing to roll back to — the previous build was overwritten, not archived. The moment you discover you want the old version is the moment it is too late to have kept it.
Where the streaming key and the token are actually used.
Last updated