Additional Webhook Data

Feature Suggestions
1

At Trakt, we use the Plex webhooks to scrobble what someone is watching and to add library items to their Trakt collection. There are a few updates that would make this feature a lot more powerful and accurate.

  1. Additional GUID IDs (basically this but extended to the webhooks). With the new movie agent, we rely on name/year matching which isn’t accurate, so additional IDs would be great!
  2. Technical metadata (resolution, audio codec, audio channels, etc) about the file added to library. This greatly enhances the Trakt collection feature since we can tag the library items with metadata.
  3. One webhook per episode or additional episode data in the show level webhook. For example, if you add 2 or more episodes of a show to your library, it only sends a single show level webhook and we don’t know which specific episodes were added.

Thanks for considering!

2

The episode one would be useful because I always seem to catch things a little bit late. I would also like to throw out the possibility that a metadata agent could potentially fix this? Assume a lookup is a acquisition event.

3

+1 here

4

This will automatically be included with the payload with new Plex Movie libraries in 1.20.1 (on new items or once a user has refreshed their metadata).

It will show up in the Metadata element like this:

"Metadata": {
      "librarySectionType": "movie",
...
...
...
      "Guid": [
        {
          "id": "imdb://tt1231583"
        },
        {
          "id": "tmdb://41733"
        }
      ],
...
...
5

Oh awesome, I was hoping that would make it in the next update! Thanks.

6

Is this only for the library.new event, or also for all the media.play/stop events?

7

Just tested it, … are tv-shows also getting these guid id’s?

8

Another useful update for the webhooks integration with Trakt would be to issue a webhook when using fix match. I have a couple items that frequently gets matched wrong, I have to go to Plex and fix the match and then to Trakt to add it to my collection manually. A fix match is effectively the same as an initial match in respect to how users add to their collection.

Thanks!

1 Like
9

A fix match is effectively the same as an initial match in respect to how users add to their collection

I couldn’t agree more.

10

Agreed, I just created a request before I sore this. It particularly relates to your third point:

One webhook per episode or additional episode data in the show level webhook. For example, if you add 2 or more episodes of a show to your library, it only sends a single show level webhook and we don’t know which specific episodes were added.

If removing the “Metadata.type”:“show” is unrealistic, adding additional data of per episode would be adiquite for me.

11

Please also add framerate!

12

Any updates on this? It continues to be an issue when 2+ episodes are added to the library at one time. We have no way of knowing the specific episodes without sending 1 web hook per episode or including all the episode info in the show level web hook.

1 Like
13

Any updates? This is still an outstanding bug when 2+ episodes are added to the library at one time.

1 Like
14

I’m in the process of building a Plex to Trakt service and noticed the Webhooks don’t currently include the media meta fields:

  • ID
  • Duration
  • Bitrate
  • Width
  • Height
  • AspectRatio
  • AudioChannels
  • AudioCodec
  • VideoCodec
  • VideoResolution
  • Container
  • VideoFrameRate
  • VideoProfile

I got those fields from MediaContainer.Metadata[0].Media[0]

Please add the meta to the event payload, so each event doesn’t require a call to Plex for additional info. I’m using the duration for calculating the progress when scrobbling and a few of the other fields are used when adding items to a Trakt collection. I was surprised to find duration isn’t returned considering viewOffset is.