// Transmission RPC reference covering JSON-RPC 2.0 transport, session token handling, torrent methods, session methods, and protocol versioning.
rTorrent XML-RPC command reference focused on remote control, multicall patterns, load methods, and the torrent commands used by Electorrent.
Deluge Web JSON-RPC and core RPC reference covering session login, web methods, and commonly used core torrent operations.
qBittorrent WebUI API reference covering authentication, sync, transfer, torrent, RSS, and search endpoints for qBittorrent 5.0+.
Write code edits quickly without performing testing or validation
Synology Download Station Web API reference covering API discovery, authentication, request format, common errors, and Download Station task operations.
Safe Electron IPC patterns for renderer-main communication with preload bridges, channel design, replies, and serialization limits.
| name | transmission-api |
| description | Transmission RPC reference covering JSON-RPC 2.0 transport, session token handling, torrent methods, session methods, and protocol versioning. |
Use this skill when you need to integrate with Transmission's RPC API.
POSThttp://host:9091/transmission/rpcparamsresultExample request:
{
"jsonrpc": "2.0",
"params": {
"fields": ["version"]
},
"method": "session_get",
"id": 1
}
Most servers require X-Transmission-Session-Id.
409 ConflictX-Transmission-Session-IdAuthorization: Basic ...rpc_version_semver 6.0.0+) uses JSON-RPC 2.0 and snake_casekebab-case / camelCase strings are deprecated but still seen in existing clientstorrent_starttorrent_start_nowtorrent_stoptorrent_verifytorrent_reannounceCommon parameter:
ids: integer id, array of ids/hashes, or "recently_active"torrent_getRequest:
idsfieldsformat: objects or tableImportant field families:
id, hash_string, name, status, percent_done, eta, eta_idledownload_dir, files, file_stats, wanted, priorities, piece_count, piece_size, piecesrate_download, rate_upload, uploaded_ever, downloaded_ever, upload_ratiopeers, peers_from, trackers, tracker_stats, webseeds_exqueue_position, seed_ratio_limit, seed_idle_limit, labels, group, sequential_downloadStatus values:
| Value | Meaning |
|---|---|
| 0 | stopped |
| 1 | queued to verify |
| 2 | verifying |
| 3 | queued to download |
| 4 | downloading |
| 5 | queued to seed |
| 6 | seeding |
torrent_setCommon mutators:
download_limit, download_limitedupload_limit, upload_limitedpeer_limitfiles_wanted, files_unwantedpriority_high, priority_normal, priority_lowlocationqueue_positionlabelsgroupseed_ratio_limit, seed_ratio_modeseed_idle_limit, seed_idle_modesequential_downloadsequential_download_from_piecetracker_listtorrent_addSupply either:
filename for URL or .torrent pathmetainfo for base64-encoded .torrent bytesUseful optional parameters:
download_dirpausedlabelspeer_limitfiles_wanted, files_unwantedpriority_*sequential_downloadsequential_download_from_pieceSuccess returns torrent_added; duplicate adds return torrent_duplicate.
torrent_remove
ids, delete_local_datatorrent_set_location
ids, location, movetorrent_rename_path
ids (single torrent), path, namesession_get / session_setImportant keys:
peer_port, port_forwarding_enabled, preferred_transports, encryptiondownload_dir, incomplete_dir, incomplete_dir_enableddownload_queue_enabled, download_queue_size, seed_queue_enabled, seed_queue_sizespeed_limit_down, speed_limit_down_enabled, speed_limit_up, speed_limit_up_enabledalt_speed_*seed_ratio_limit, seed_ratio_limited, idle_seeding_limit, idle_seeding_limit_enabledrpc_version_semver, versionsession_statsblocklist_updateport_testsession_closefree_spacequeue_move_top, queue_move_up, queue_move_down, queue_move_bottomgroup_set, group_getJSON-RPC errors may include:
codemessagedata.error_stringdata.resultrpc_version_semver for compatibility checksrpc_version and rpc_version_minimum are deprecatedX-Transmission-Rpc-Version may be returned on HTTP 409 responses on newer serversElectorrent currently talks to Transmission using the legacy method names:
session-gettorrent-gettorrent-addThat works on current Transmission releases, but new integrations should prefer the JSON-RPC 2.0 snake_case forms from this spec.