Skip to content
BrokerrBrokerr

SIMKL target

SIMKL is a production target for movies, regular television, and anime. Connect it with hosted OAuth through auth.brokerr.net, or use a custom SIMKL OAuth application with its own client ID, secret, and registered redirect URI.

Supported features

Section titled “Supported features”
  • Plan to watch, Watching, On hold, Dropped, and Completed status.
  • Exact watched episode coordinates and progress protection.
  • Continue Watching transitions to On hold or Dropped and back to Watching.
  • Integer 1..10 ratings through Brokerr’s normalized rating scale.
  • Movies, TV shows, and anime, including AniBridge split-season/cour mappings.

SIMKL does not currently expose managed custom lists, diary entries, notes, or a separate repeat-count feature in Brokerr.

Mapping

Section titled “Mapping”

Movies and regular shows can use compatible SIMKL, TMDB, IMDb, or TVDB IDs. Anime can additionally use MAL, AniDB, AniList, or Kitsu IDs. Source-provided AniBridge descriptors allow one source series to map into multiple SIMKL anime entries. Manual mappings accept values such as movie:simkl:123, tv:tvdb:81189, and anime:mal:5114.

Full and continuous reads

Section titled “Full and continuous reads”

Brokerr follows the official SIMKL Full Sync Guide:

  1. On the first read it captures /sync/activities, then loads /sync/movies, /sync/shows, and /sync/anime separately and sequentially.
  2. It stores the exact activity watermark and a safe account snapshot for that target instance.
  3. Later runs always check /sync/activities first. An unchanged account needs no library request.
  4. When state changed, Brokerr sends the exact saved timestamp to /sync/all-items?date_from=... and merges the returned delta.
  5. A missing cursor or a list-removal timestamp change triggers a safe sequential refresh rather than an unbounded all-items download.

The cursor is cleared when the target disconnects or reconnects. It does not contain credentials. Every request includes SIMKL’s required client_id, app-name, app-version, and descriptive User-Agent values.

Writes and safety

Section titled “Writes and safety”

Writes are grouped by operation and media bucket in batches of at most 50 items. The default HTTP policy permits one request per second, uses bounded retry/backoff, and honors Retry-After. Brokerr refreshes authoritative SIMKL state after writes and advances feature state only for confirmed outcomes. Apply and Revert use the same provider pacing and reconciliation path.