Glossary
Terms used across Relaygate documentation.
People and roles
| Term | Meaning |
|---|---|
| Developers | Addon developers — authors of Stremio (or similar) addons who integrate Relaygate on the server side. |
| Users | People who use debrid services with Relaygate: they manage a vault, proxy API keys, and access policies. |
| Relaygate operators | The team that runs the service, reviews developer applications, and handles abuse and status. |
Services
| Term | Meaning |
|---|---|
| (Debrid) providers | Upstream debrid services (e.g. TorBox, Real-Debrid, AllDebrid, Premiumize, SmokeDebrid) whose APIs Relaygate maps to the canonical API. |
| SmokeDebrid | A dummy debrid provider included in Relaygate for testing purposes. Requests use the smokedebrid provider slug (see the Canonical API guide capability matrix for what is mapped today). |
Technical terms
| Term | Meaning |
|---|---|
| Addon identifier | Unique public string chosen at developer registration; identifies the addon in the logs. |
| Developer API secret | Secret paired with the addon identifier; proves an approved addon is calling Relaygate. Not shown to end users. |
| End-user proxy API key | Single key the end user pastes into each addon UI; maps to their vault of per-provider debrid keys. |
| Provider hint | Per-request signal for which debrid service(s)'s adapter to use (canonical: X-Relaygate-Provider header — see API spec). |
| Vault | Encrypted storage of a user’s per-provider debrid tokens on Relaygate. |
| Gateway / API | The public HTTPS API your addon backend calls; JSON control plane only (no media byte proxying through Relaygate). |