Titles leaving and catalog change dates
Two different endpoints answer two different questions. Leaving dates say when a movie or TV season is known to leave a service. Change feeds say which title IDs changed so a stored catalog can be refreshed. Neither one streams video, and a departure date can move.
Leaving dates
GET /v1/title-leaving-dates/ returns known dates when movies and TV seasons leave streaming services. Each listing includes the Watchmode title id, title, title_type, region, type, leaving_date, provider_id, and season (null for a movie). Results are ordered by date, country, provider, title, and season. A successful page costs 1 credit.
- Developer: the next 10 departures starting today, in the account’s free-plan countries. regions and a limit of up to 10 are allowed. Date filters and later pages return 403 LEAVING_PREVIEW_LIMIT. total_pages is at most 1. total_results still counts matching departures in the next 90 days.
- Startup, Business, and Enterprise: choose start_date and end_date, request up to 250 listings per page, and read every page. The default window is today through the next 90 days. The maximum span is 90 days when regions are omitted and 366 days when regions are set.
- Omit regions on a paid plan for every supported country, or pass comma-separated codes from GET /v1/regions/. Coverage varies by service and country. An empty page does not prove that nothing is leaving. Historical rows are retained observations only.
Catalog change feeds
Paid plans can list titles and people that changed. These routes are badged Paid plan in the docs and cost 1 credit per successful page. They return IDs to refresh, not the full leaving calendar:
- GET /v1/changes/titles_sources_changed — titles whose streaming availability changed in a date range. A title matches when its sources changed in any requested country.
- GET /v1/changes/titles_details_changed — titles whose details changed.
- GET /v1/changes/titles_episodes_changed — titles whose episodes changed.
- GET /v1/changes/new_titles — titles added to the catalog.
- GET /v1/changes/new_people — people added to the catalog.
Upcoming and recent premieres are a third route, GET /v1/title-release-dates/, and it is paid only. A release row is not a leaving row. Release times are included when Watchmode has them. A null release time means the time is unknown, not midnight.
Who it is for
“Leaving soon” features, editorial calendars, and apps that tell a viewer a title is about to depart a service in a given country. Catalog sync jobs that store Watchmode data and need the IDs that changed since yesterday. Paid subscribers may keep data stored while the subscription is active. Developer-plan displays should refresh or delete cached data within 30 days. The terms have the full cache wording.
Which plan unlocks it
The leaving preview of 10 rows is on every plan, including Developer. The full leaving calendar, custom dates, and the change feeds require Startup, Business, or Enterprise. Monthly credits are shared with the rest of the API and are separate from the per-minute request limit. Allowances are on the pricing page.
Questions
Is the leaving calendar the same as the changes feed?
No. title-leaving-dates returns departure listings with a date, country, and provider. The changes routes return IDs of titles or people that were added or edited. A source change does not by itself include the leaving date.
Can a free API key filter leaving dates by month?
No. Free accounts get the next 10 departures from today in their free-plan countries. start_date, end_date, limits above 10, and page 2 return 403 LEAVING_PREVIEW_LIMIT. A paid plan is required for those filters.
Does a leaving date mean the title is gone at midnight?
The field is a calendar leaving_date. The docs say departure dates can change and that coverage varies by service and country. Do not treat the date as a confirmed hour.