Skip to content

Library API: are the metadata fields staying, and can non-Plex media servers be marked as synced? #1012

Open

Description

@zotabee

Hi! Two questions about the Library (collection) API, from someone syncing a Jellyfin library to Trakt.

1. Media info fields (metadata)

The new API definitions in this repo don't include them:

  • the POST /sync/collection body uses the plain list schema
  • collectionResponseSchema only has collected_at, updated_at and available_on
  • extended only lists full, images and available_on

Yet the live v2 API still accepts and returns metadata (media_type, resolution, hdr, audio, audio_channels, 3d) with extended=metadata, and the Library JSON export includes it. The physical library update also says Format and Resolution will be required at every entry point, third-party integrations included.

Are these fields staying in the API, and will they be added to the new definitions? Tools like the Jellyfin Trakt plugin send them today, and CrossWatch has been asked to support them (CrossWatch #1510).

2. available_on for non-Plex media servers

The definitions say the digital filter keeps "items synced from a connected media server", and that synced items are labelled plex. Items added through the API by Jellyfin, Emby or Kodi tools never get it. None of the 18,800+ items in my library has available_on set.

Is there, or will there be, a way for apps that sync a Jellyfin, Emby or Kodi library to mark items as media-server items? The Oct 15 announcement only covers Plex Sync.

3. A smaller one: is a 4K Blu-ray media_type planned? Today a UHD disc has to be bluray + uhd_4k.

Thanks!

Activity

  1. zotabee commented on Oct 17, 2026

    @zotabee
    Author

    For context, the Jellyfin Trakt plugin sends these fields today, and these open PRs extend it with more values from the legacy docs' Add to Collection list (HDR10+, Dolby Atmos, DTS:X, DTS-HD MA/HRA, and channel fallbacks):

    Knowing whether metadata stays, and where its accepted values will be documented now that the legacy docs are deprecated, would help these land.

  2. zotabee commented on Oct 19, 2026

    @zotabee
    Author

    An update after running these PRs on my server since Oct 18:

  3. zotabee commented on Oct 20, 2026

    @zotabee
    Author

    Thanks for bc6f6b3! Does that mean Trakt will connect to Jellyfin servers itself, like Plex Sync? If so, will that sync send the media info too, and will items added through the API (the Jellyfin plugin, CrossWatch) stay without available_on?

  4. zotabee commented on Nov 6, 2026

    @zotabee
    Author

    @vladjerca, Jellyfin sync is now in the sync settings (trakt/trakt-web@6b1434fbe, open to free accounts since trakt/trakt-web@692f6ef92), which answers my question above. Thanks! And ae20b2f now documents the media info fields on collection add.

    What's still open:

    • Does the Jellyfin sync store media info (format, resolution, HDR, audio) for what it collects?
    • Items collected through the API (the Jellyfin plugin, CrossWatch) still have no available_on, and available_on=digital returns none of them. Will they stay that way?
    • The collection response and extended still don't list metadata, and there's no 4K Blu-ray media_type yet.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions