-
Notifications
You must be signed in to change notification settings - Fork 7
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Include ProviderIds in /sync/watched/ #363
Comments
The various IDs are included in method such as https://trakt.docs.apiary.io/#reference/episodes/summary/get-a-single-episode-for-a-show and several other methods as well. |
thanks, is there an endpoint suited to reading a users a Entire watched history which includes episode tvdbids? |
You may be using the wrong |
thank you..thats working for me and providing the info as you say. but i dont think its efficient for a full sync of a users watched status on epsiodes...not least because every instance of a watched action is communicated.rather than a single watched for each index. so undeterred i used what you showed about /users and tried so i tried so it maybe that i will have to iterate through each individual known show to get an efficient watched list with ids for a known show? (if you havent guessed yet im very unfamiliar with trakt api so appreciate all the pointers i can get) to a ley man it doesnt an unreasonable feature request to get the episode providerids added to the /watched endpoint[s]? |
Yeah your suggestion of a way to get episode ids from the |
Are there currently any plans to add episode ids to |
might it be possible to include the providerids (tvdb in particular) for episodes in the response. So that when the index on trakt does not match the index on the application it is still possible to map watched events to episodes with same providerids. The need is particularly prevalent on specials eg https://trakt.tv/shows/crazy-ex-girlfriend/seasons/0/episodes/2 does not agree with the index on tvdb (and my app) but does agree with the tvdbid.
thanks for considering
this is a feature request but havent worked out how to specify that (yet)
The text was updated successfully, but these errors were encountered: