Configuration

Configuration Reference

transmission-telegram supports configuration through both command-line arguments and environment variables.

---

Configuration Flags & Environment Variables

Flag	Environment Variable	Default	Required?	Description
-token	TT_BOTT	—	Yes	Telegram Bot API token obtained from @BotFather.
-master	—	—	Yes	Authorized Telegram @username (e.g. @johndoe) or permanent numeric User ID (e.g. 123456789). Can be specified multiple times to authorize multiple administrators.
-url	TR_URL	http://localhost:9091/transmission/rpc	No	Full URL to Transmission's JSON-RPC endpoint.
-username	TR_AUTH (user:pass)	""	No	Transmission RPC HTTP Basic Authentication username.
-password	TR_AUTH (user:pass)	""	No	Transmission RPC HTTP Basic Authentication password.
-logfile	—	"" (stdout)	No	File path to write structured bot logs instead of standard output.
-transmission-logfile	—	""	No	Path to local Transmission daemon log file for legacy tailer-based completion notifications. If omitted, the bot uses native RPC polling watcher.
-no-live	—	false	No	Disables live message updating on /head and /tail commands (useful if hitting Telegram rate limits).

---

Authorizing Multiple Masters

You can authorize multiple users to control the bot by repeating the -master flag:

transmission-telegram \
  -token="123456789:ABCdefGhIJKlmNoPQRsTUVwxyZ" \
  -master="@alice" \
  -master="@bob" \
  -master="987654321"

Why use Numeric User IDs?

If a user does not have a public @username configured in Telegram settings, or if they frequently change their username, you can provide their permanent numeric Telegram user ID (e.g. 987654321). You can find your user ID by sending a message to @userinfobot on Telegram.