Knowledge base
Connect a Gcore API token from an account with Video Streaming enabled, and your live streams and stored videos appear in your Zinn® dashboard.
Connecting Gcore Video Streaming brings your live streams and stored videos from your own Gcore account into your Zinn® dashboard, so you can see them alongside your sites.
A Gcore account of your own, with Video Streaming enabled on it. This is bring-your-own only: we do not resell Video Streaming, so the product, the contract and the bill are between you and Gcore, and what you run there is charged to your Gcore account, not to your Zinn® plan.
In the Gcore Customer Portal, open your avatar at the top right, then Profile → API tokens → Create token. Name it, choose Never expire or an expiry date, and give it a role for each product it needs. Gcore shows the token once; copy it then.
The same token works for every Gcore product you connect, so if you have already connected one Gcore product you can paste the same token again — provided its roles cover this product too. A token cannot be given a higher role than your own login has.
Give the token a role for Streaming.
Open Integrations in your dashboard and choose Connect an account. Pick Video & streaming as the group and Gcore Video Streaming as the account, fill in API token, and press Connect account.
We test what you paste before anything is saved. A key that does not work is never stored, and the answer says what was wrong with it. A key that works is kept encrypted in our secrets vault — never in our database — and is never shown again, not even to you.
reached from the connection's Open your own services button on Integrations.
under your contract with them.
It says the product is not enabled. The token is valid, but Video Streaming is not switched on for that Gcore account — Gcore then refuses every read. Enable it in the Gcore Customer Portal (or ask Gcore to), then connect again. A token whose role does not include Video Streaming produces the same refusal; create one that does.
It says the key was rejected. Almost always one of three things: a space or a line break copied with it, a key that has expired, or a key that was revoked or regenerated after you copied it. Create a fresh one and paste it again.
It connects, but something later fails. The key authenticates but lacks a permission the action needs. Create a new key with the permissions listed above, then disconnect the old connection and connect the new key.
Open Integrations, find the account and press Disconnect. That deletes the stored key at once. Anything that was using it stops at its next action, and the screens that depended on it say so rather than failing quietly.
Disconnecting does not undo what was already done — records, deployments or settings we changed on your account stay as they are. If you think the key itself may have leaked, also revoke it at the vendor; disconnecting removes our copy, not theirs.
What we have been writing about hosting, SEO and running sites at scale.
How hosting shapes indexing and link equity in 2026: keeping pages indexed, vetting aged domains before you build on them, link building without a footprint, and an honest line on what infrastructure can and cannot do for SEO.
Read the post →A practical checklist for fast, secure WordPress: server-level caching, a per-site object cache, the handful of plugins worth running, keeping the stack current, and the WooCommerce pages you must never cache.
Read the post →What actually separates good managed hosting from a cheap box with a control panel — migrations, backups, isolation, real caching and honest scaling — and how to judge it before you commit.
Read the post →Support is included on every plan, the desk is open 24 hours a day, and you can write to us in any of our 58 languages — we answer you in yours.
Contact support → All articles →