Webhooks contains the sender setup guides and the secret used to authenticate incoming events.

Setup guides

Plekt Webhooks setup guides for Plex, Emby, and Jellyfin
Setup Guides explains the sender-specific event switches and endpoint details.

Use the platform-specific setup guidance for Plex, Emby, or Jellyfin. Configure the sender to reach the Plekt host and include the authentication value exactly as shown by the app.

Plex normally uses Plekt’s realtime WebSocket notification channel. Emby and Jellyfin can send playback events through their Plekt plugin or webhook alternative, with scheduled polling providing reconciliation. Configure only one event sender per server.

After configuring a sender, play a short portion of a known title and confirm both a new History row and a Sync Activity result.

Test an Emby or Jellyfin sender

Emby and Jellyfin have a Test button beside Plugin configured or Webhook configured. It works for either sender. Plex has no button because it does not use a webhook.

  1. Select Test, then Start test. You have 5 minutes.
  2. Mark an unwatched episode or movie as played on that server, signed in as the account Plekt is connected to.
  3. Read the result in the same window. It updates without a refresh and gives the likely cause if nothing usable arrives, such as a rejected token or a missing mark-played event.

After a pass, choose Yes, remove it to unmark the item on the server, or No, leave it marked to keep the mark. Plekt’s next scan then treats a kept mark as a normal manual mark. The test itself adds nothing to your watch history and sends nothing to other apps or trackers.

Webhook secret

Plekt Webhook Secret settings card for the generated token and rotation controls
The Webhook Secret card keeps the generated token and rotation controls together; expand it in the app when you need to copy or rotate the secret.

Copy the complete generated URL when the sender cannot set a custom header. In that mode the secret is carried in the query string as ?token=....

When the sender supports headers, use X-Plekt-Webhook-Secret (the older X-Plembfin-Webhook-Secret still works) or the accepted Authorization: Bearer form exactly as shown by the guide.

To rotate the secret:

  1. Choose Rotate and confirm it.
  2. Update every configured sender with the new URL or header value.
  3. Send one test event.
  4. Confirm a new Sync Activity row.

Rotation immediately invalidates old webhook URLs. Never include a token-bearing URL in a public issue, log attachment, or screenshot. For a 401 response, follow Webhook returns 401.