Connection Info for Emby, Jellyfin, and Plex

  • Updated

Overview

Infuse is able to connect to Emby, Jellyfin, and Plex servers, and provides various headers which include details about the connection type, such as User-Agent, Product, and Version. Server admins can use this header info to route and control requests that come from Infuse.

Connection Types

Infuse will use one of three connection types when making requests.

Infuse-Direct

This allows Infuse to access the server directly, and load content on-demand as needed. This is similar to how native apps interact with the server. There is no pre-caching of data or full scanning of libraries required. This is the default connection type in Infuse 7.7+.

Infuse-Library

This is the original connection method used in Infuse, and will pre-cache data from the server within the Infuse app. This is an optional connection type in Infuse 7.7+.

Infuse-Download

This connection type will be used when downloading files from the server for offline use.

In versions prior to 7.7, a connection type of ‘Infuse’ was used for all requests.

Example Requests

Emby/Jellyfin

GET Request HTTP/1.1
Host: IP:port
X-Emby-Authorization: MediaBrowser Token="#####", Client="Infuse-Direct", Version="7.7", Device="####", DeviceId="###-#-###"
Accept: application/json
User-Agent: Infuse-Direct/7.7
Accept-Language: en-US,en-GB;q=0.9,en;q=0.8
Accept-Encoding: gzip, deflate
Connection: keep-alive

Plex

GET Request HTTP/1.1
Host: IP:port
Accept: application/json
X-Plex-Device: ####
X-Plex-Container-Start: 0
X-Plex-Platform: ###
X-Plex-Product: Infuse-Direct
X-Plex-Client-Identifier: ####-#-###
X-Plex-Container-Size: 2000
Accept-Language: en-US,en-GB;q=0.9,en;q=0.8
Accept-Encoding: gzip, deflate
X-Plex-Device-Name: ###
X-Plex-Version: 7.7
User-Agent: Infuse-Direct/7.7
Connection: keep-alive
X-Plex-Token: ##########
Share this article

Was this article helpful?

1 out of 3 found this helpful

Have more questions? Submit a request