Replies: 1 comment 1 reply
-
Can’t you just use the Get Watched Endpoint only to do this? Since this method has the entire watched history, there is no need to get history separately. Since you’re caching data in your app, you’ll know when new episodes show up in the Get Watched Endpoint. Another reason for using this endpoint is you can also handle when a user removes any plays and fully sync the state of all shows. |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
My Use Case (Daily Sync): I want to get all new episode watches, which were marked as watched in a given time frame (in my case all episode watches of the last 24 hours). What's important here is that I don't want to get episodes watches with watch dates in a given time frame (not
watched_at
date butlast_updated_at
timestamp!).Solution (with the current API): Retrieve all shows which were updated in a given time frame by Get Watched Endpoint. After that I would get the full history of each show with the Get watched history endpoint. Potentially I need to check each page for new episode watches because I can not filter the result by
last_updated_at
timestamp and they are sorted bywatched_at
timestamp.Suggestion: Either add a new endpoint to retrieve watched history by
last_updated_at
timestamp or add an option to sort the Get watched history bylast_updated_at
timestamp.I would think that syncing watches is used by many applications. By the above suggestion the load would be reduced and the API would be easier to use for syncing processes. What do you think? Is it a reasonable extension to the API? Or do I maybe miss something in the API?
Beta Was this translation helpful? Give feedback.
All reactions