The administration interface exposes operational state and commands. Treat it as a privileged surface even when an operation is issued through an ordinary GET request. A browser, monitoring agent or copied URL can otherwise trigger a change unexpectedly.
Read state before changing it
The pinned implementation registers stats, listmounts, listclients and managerelays. XML responses and XSLT views serve different consumers. /admin/streams supplies relay-oriented stream information and must not be treated as a general public status page.
This read-only shell example prompts for the administrator password. Replace the example hostname and use the configured protected endpoint:
curl --fail --silent --show-error --user admin 'https://stream.example.org/admin/listclients?mount=%2Flive.ogg'Do not put passwords in the command, URL, shell history or exported response. Responses may contain listener addresses and account identifiers. Keep collected XML private and apply a retention limit.
Select the actual command
| Task | Pinned command | What to check first |
|---|---|---|
| Inspect or enable a relay | managerelays | Local mount and intended enable state |
| Inspect listeners | listclients | Exact mount and privilege |
| Send a metadata update | metadata | Format, mode and URL encoding |
| Change a fallback | fallback | Destination compatibility and access rules |
| Move listeners | moveclients | Destination capacity and existing source |
| Disconnect one listener | killclient | Current listener ID and mount |
| Disconnect a source | killsource | Recovery and fallback behaviour |
| Maintain supported user accounts | manageauth | Selected authentication backend |
The old administration document spells the fallback path fallbacks; the current command table registers the singular fallback. Do not build automation around the stale spelling. function accepts a perform operation; it is not an unrestricted or automatically safe reload API. Confirm the named implementation before using it.
Verify the result separately
Use a disposable instance to exercise any changing request. Check its response body as well as HTTP status, then retrieve independent state and observe the affected listener. A response alone cannot prove audio continuity. This article documents registered interfaces; it does not claim these commands were executed against a running KH service.