Connect Wizarr
Add Wizarr to Kochab with its API key to see pending invitations, recently joined users, and whether each media server behind it is readable.
Wizarr hands out invitations to your media servers so people can join without you creating accounts by hand. One Wizarr can front Jellyfin, Plex, and Emby at once.
Kochab reads it, so the question you actually get asked away from your desk - is anyone still waiting to get in? - has an answer on your phone.
What Kochab exposes through Wizarr
- Overview: how many users exist, how many invitations are pending, how many expired
- Pending invites: which servers each invitation covers and when it lapses
- Recently joined: the five most recent people to accept an invitation, and which server they landed on
- Backends: each media server Wizarr fronts, and whether Kochab can actually read its libraries
Wizarr also contributes to the Analytics page: accounts, pending invites and expired invites appear there alongside whatever your playback sources report, and add up across every Wizarr you have configured.
Read-only. Creating and revoking invitations, and enabling, disabling or extending users, stay in Wizarr’s own web interface - those are desk work, and doing them from a phone by accident is worse than not having them.
Default connection
| Field | Typical value |
|---|---|
| Port | 5690 |
| Scheme | http on LAN, https behind a reverse proxy |
| Auth | API key in the X-Api-Key header |
Connect it
- In Wizarr, open Settings and copy the API key.
- In Kochab, go to More > Stacks & Services > Add service and pick Wizarr.
- Enter the address Wizarr is reachable at on your network, for example
http://192.168.1.10:5690, and paste the API key.
What it will not show you
Invitation codes and links are deliberately never displayed. They grant entry to your server, so a screenshot of the invite list would hand that out. Kochab shows the invitation’s label, the servers it covers, and its expiry - never the code or the join URL.
Email addresses are not shown either. The username and the server the person joined answer the question; the address is not needed to answer it.
Backend health means readable, not configured
A backend is shown as healthy when Kochab can read libraries from it through Wizarr - not when Wizarr says it is verified.
Those are different things, and the difference is not theoretical. A Wizarr instance can report a server as verified while returning no libraries for it at all, which means invitations naming that server will not do what the person expects. Showing “verified” there would be reassuring and wrong, so Kochab shows what it can actually read.