Playback Check Ins

[kingargyle 19]

According to the documentation on the wiki (https://github.com/MediaBrowser/Emby/wiki/Playback-Check-ins), there is supposed to be a Sessions/Playing end point that takes a payload to update the playback position of a particular item for a user.   it should be sent approxiametly every 10 seconds to keep the servers time and the clients time in sync.   However,   looking at the Sessions API, everything there seems to require a Session Id be passed to it.

 

http://swagger.emby.media/?staticview=true#/SessionsService

 

Is the documentation out of date with what the actual API provides now.  I'm more concerned about the 3.3 API as that is what I'm currently developing against (mainly because my 32 bit server that is the only version that is supported any longer).

 

Update: Looks like I found what I was looking for, it is in the Playback Service in the Swagger documentation.  This might need to be updated in the Wiki.

 

http://swagger.emby.media/?staticview=true#/PlaystateService

 

 

Dave

Edited September 28, 2018 by kingargyle

[Luke 37009]

Thanks for the info !

 

@@softworkz

[softworkz 3326]

@kingargyle: So you found what you need?

 

And yes, eventually we'll need to document the PlayStateService in the Wiki as well.

[kingargyle 19]

@kingargyle: So you found what you need?

 

And yes, eventually we'll need to document the PlayStateService in the Wiki as well.

 

Yes.  I found what I need in the PlayStateService under the Users/{userId}/PlayingItems/{itemId}/Progress  API and the related PlayingItems and PlayedItems end points.  At least on the 3.3 API, it doesn't seem that MediaSourceId is required, as it updates the records just fine.  Not sure if it is required in later versions of the API or not.

[Luke 37009]

You're working against an older server version?

[kingargyle 19]

You're working against an older server version?

 

Yes, unfortunately, the "server" I'm using at home is only running a 32 bit version of Ubuntu, and 3.3 of Emby was the last version that will work on that machine.   Eventually I'll get around to installing a developer version of the latest server on my dev laptop or when I rebuild the server in the future.   For now, I have to work against the old API.

[Luke 37009]

Got it, ok. That should be fine. Was just curious.

[softworkz 3326]

You're working against an older server version?

 

Just for clarification:

 

The static API browser that is linked from the Wiki page lists the API of a recent version of Emby Server: http://swagger.emby.media/?staticview=true

 

Whereas the API browser that you're opening from your own server dashboard - as described here: https://github.com/MediaBrowser/Emby/wiki - will always exactly match and display the API of the server version that you are running.

 

 

You can also see the API version in the API browser. It's in the (very small) superscript bubble right to the title in the first row.

[kingargyle 19]

Just for clarification:

 

The static API browser that is linked from the Wiki page lists the API of a recent version of Emby Server: http://swagger.emby.media/?staticview=true

 

Whereas the API browser that you're opening from your own server dashboard - as described here: https://github.com/MediaBrowser/Emby/wiki - will always exactly match and display the API of the server version that you are running.

 

 

You can also see the API version in the API browser. It's in the (very small) superscript bubble right to the title in the first row.

 

Yep.  I realize that the external site will have more up to date information than the Swagger documentation locally.