Watch Order developer API

Authentication

None. Every endpoint below is public and read-only. Responses are cached at the CDN: keep it under one request per second and cache responses on your side when you can.

Endpoints

GET /api/franchises — every franchise, with id, name, description, number of titles and available orders.

GET /api/franchises/{id}?order={orderId} — a franchise with its continuities, orders, routes and the titles of the requested order (the release order by default).

GET /api/titles/{id} — a title: kind, release date, runtime, seasons, overview, poster, TMDB and IMDb ids and its franchises.

GET /api/upcoming?franchise={ids} — releases, new seasons and new episodes in the next 365 days.

GET /api/providers?tmdbId=&type=movie|tv&region= — where to watch a title in a country (JustWatch data via TMDB).

GET /api/credits?tmdbId=&type=movie|tv — main cast.

GET /api/health — service status.

All of them take lang=en|es where there is text (English by default).

Examples

The MCU in chronological order:

curl 'https://watchlist.wxlter.dev/api/franchises/marvel?order=chronological'

Errors

Errors respond with JSON and the right HTTP status: error (the message), code (invalid_request, not_found, rate_limited, upstream_error, internal_error…), status, hint (how to fix the request) and docs. An endpoint that does not exist responds 404 in JSON.

{"error": "No existe la franquicia \"marvl\"", "code": "not_found", "status": 404, "hint": "List valid ids with GET /api/franchises.", "docs": "/developers#errors"}

For AI agents

/llms.txt sums up the app and when to use it. Every public page (home, franchises, titles, routes, FAQ and guide) responds with Markdown if you send Accept: text/markdown, and a path that does not exist responds 404.

Attribution and use

Title data comes from TMDB and “where to watch” from JustWatch: credit them if you show it. The orders, routes and importance of each title are Watch Order's; link to the franchise page when you use them. Use is subject to the terms.