Skip to main content
New in 0.9.0 Import from an existing Plex or Jellyfin server. The same endpoints are mounted twice:
  • /api/admin/import/*, which needs an admin token
  • /api/setup/import/*, which is open only while the first-run setup wizard is running
The Plex token or Jellyfin API key you send is used only for that request and the import it starts. It is never stored.

Connection

preview and run both take the connection fields:
string
required
plex or jellyfin
string
required
The source server’s address
string
required
Plex token or Jellyfin API key
object[]
[{"from": "/data/movies", "to": "/media/movies"}] when the source sees your files at different paths than Kernel does
In the preview, each source user comes back with a suggested_username, whether it was already_imported, and whether an existing Kernel account matched by name (with matched_username).

Run

On top of the connection fields, run takes what to import:
object
Source library ID → Kernel library ID, or "__create__" to create a matching library
object[]
One plan per source user: source_user_id, target (new, existing or skip), plus username for a new account or existing_user_id to merge into an existing one. PIN-protected Plex Home users also take a pin.
boolean
Import Watch History and progress
boolean
Also apply watch activity to accounts that already exist
boolean
Import Watchlists
boolean
boolean
boolean
Don’t bring over intro and credits markers
boolean
Import only Show Themes (Plex theme music)
Imported Show Themes are served at GET /theme/{item_id} (see Libraries & Items).

Plex Home PIN sync

A Plex Home user protected by a PIN can’t be synced during the admin’s import. That user can sync their own watch state and watchlist later by entering the PIN once:
  • GET /api/user/me/plex-sync: whether the signed-in user has a pending PIN sync
  • POST /api/user/me/plex-sync: run it. Body: {"pin": "1234"}
The PIN is used for that sync and never stored.