Get all items of one type in one status bucket

Preferred form: your client_id as a URL query parameter on every request. Self-describing in logs and curl commands. See Headers and required parameters.

OAuth 2.0 or PIN-flow access_token. Required for endpoints that read or modify the user's library, scrobble session, ratings, settings, or playbacks. See Authentication.

Descriptive identifier for your app, ideally name/version. Examples: PlexMediaServer/1.43.1.10540, kodi-simkl/0.9.2, MyApp/2.4.1 (https://myapp.com).

One of shows, movies, anime, or all. Pass all to skip filtering on type even when the runtime accepts the segment-less form, so for spec strictness this is true. To call without it in practice, just drop the segment from the URL.

One of watching, plantowatch, hold, completed, dropped, or all. Movies accept only plantowatch, completed, dropped, and all; TV and anime accept all six. Pass all to skip filtering on status — /sync/all-items/{type}/all returns every status for that type. User watchlist status. Movies skip watching and hold — see /conventions/list-statuses.

Opt into rewatch tracking. When yes, POST /sync/history records an additional rewatch session instead of being a no-op for already-watched items, and GET /sync/all-items returns one extra entry per saved rewatch session alongside the item's normal entry. Available to Simkl Pro and VIP users — non-Pro callers see no effect even with the flag set.

⚠️ Do not enable this flag until you've read the Rewatches guide end-to-end and implemented the precautions. Used carelessly (on retries, on every scrobble event, on importer re-runs, without pinning rewatch_id after the first write), it will pollute the user's history stats and rewatches panel with phantom sessions. The flag should be gated behind explicit user intent — a dedicated "Rewatch" button — never on background or automated flows. Also expose a per-user Track rewatches toggle in your app's settings (default off) — not every user wants the rewatch-session complexity.

Limits: up to 50 rewatches per item (movie, show, or anime), and any two watch events on the same item (movie or episode) must be at least 2 days apart — a new rewatch within 48 hours of the previous watch of that same item collapses into the same session (it's a rewatch, not a rewind 😄). Full walkthrough — session lifecycle (active / completed / closed with bidirectional transitions), episode-level tracking, reading sessions back from GET /sync/all-items, and ready-made code for simkl.com-style UI patterns — in the Rewatches guide.

ISO-8601 timestamp. Returns only items updated since this time. Use the value saved from /sync/activities.

full returns more info including a list of watched episodes

When yes, attaches a next_to_watch_info object to each watched item, indicating the next episode to watch.

When yes, includes TVDB IDs on each episode in episode-bearing responses.

Force English titles. Defaults to the user's profile language.

When movies, restricts the anime results to anime-movie subtype only.

yes adds per-episode watched_at timestamps to every episode in the response. Modifier only — episodes must already be loaded by extended=full / extended=full_anime_seasons (or by include_all_episodes=yes for completed/dropped statuses). Pair with date_from — significantly larger response.

Three-value flag that controls per-episode loading on canonical entries.

• no (default) — Episode lists are loaded only for items in watching, plantowatch, and hold statuses. Items in completed and dropped skip episode loading entirely.
• yes — Load episode lists for every status. Synthesizes virtual episode rows for completed entries that don't have per-episode data recorded (virtual rows fall back to the show's air-date timestamps).
• original — Load episode lists for every status, but skip virtual-episode synthesis. Completed entries get only their real per-episode rows.

Independent of allow_rewatch=yes — combine the two when you need both canonical episode lists AND rewatch session episode lists in one response. Pair with date_from since the response can be much larger when episodes load for completed-bucket items.

yes returns memos in addition all other data

Your client_id from your Simkl developer settings. Required on every request.

Short, lowercase identifier for your app (e.g. plex-scrobbler, kodi-bridge). Helps Simkl identify which apps are using the API.

Your app's current version (e.g. 1.0, 2.4.1). Helps Simkl debug issues you report.