Track Streaming Catalog Additions and Changes
View all Streaming Availability endpoints →Poll catalog changes for a required country, change_type and item_type. Documented change types are new, removed, updated, expiring and upcoming; item types are show, season and episode. Use show_type to narrow show-level changes to movies or series. Optional catalogs uses the same service, service.access_type and service.addon.addon_id syntax as catalog search, with up to 32 comma-separated catalogs. The observed new/show request for Netflix US returned a raw object containing changes, a shows map keyed by show ID, hasMore and nextCursor. Change entries included changeType, itemType, showId, showType, streamingOptionType, service, link and timestamp; join showId to the shows map for title metadata and viewing options. Pages contain up to 25 changes ordered by timestamp, with order_direction selecting ascending or descending order. Pass from and to as inclusive Unix timestamps in seconds: new, removed and updated changes are limited to the past 31 days, while expiring and upcoming changes use the next 31 days. Omitted bounds span the corresponding documented window. Future dates may be unknown; include_unknown_dates controls whether those entries are included and does not affect past changes. Continue with nextCursor only when hasMore is true, keeping all other parameters unchanged. This is a polling feed, not a webhook or an unlimited historical archive; future-date coverage is not guaranteed for every service.
API Features
Live API Demo
🔒 Sign in to try it live
Log in to call this API with your own API key. New accounts get 100 free credits — no card required.
Log in / Sign upNo active API key found. Create one in your Dashboard, then reload this page. Dashboard →
/api/project/streaming-availability/get-changes API Response (JSON)
{} curl -X GET 'https://api.opendata-api.com/api/project/streaming-availability/get-changes?key=<API_KEY>&country=<country>&include_unknown_dates=false&output_language=en'
Query Result
Use Cases
- Generate a scheduled new-on-Netflix newsletter by joining new change records to their show metadata and streaming-service links.
- Maintain a local availability index using new, removed and updated records while retaining periodic snapshots for history beyond the feed window.
- Prototype leaving-soon watchlist reminders for services that supply expiring entries, distinguishing unknown dates from confirmed deadlines.
- Build a bounded upcoming-release digest that paginates changes and preserves country, catalog, item-type and date filters between requests.
Frequently asked questions
How can I build new-title notifications or leaving-soon watchlist reminders?
Schedule polling in your application with country, catalogs, change_type and item_type. Use new for additions or expiring for reported future expirations, then join showId to shows for title metadata. This endpoint does not push notifications, and future-date coverage depends on the returned data.
Can I retrieve streaming catalog changes from several years ago?
No. new, removed and updated cover the past 31 days; expiring and upcoming cover the next 31 days. Optional from and to are inclusive Unix-second bounds within the appropriate window. Retain your own snapshots and changes for longer-term history.
How do changes relate to the shows object?
changes is an array, while shows is an object keyed by show ID. Use each change's showId to find its metadata rather than joining by array position. Continue with nextCursor only when hasMore is true and preserve every other parameter.
Does include_unknown_dates fill in missing upcoming or expiration dates?
No. It controls whether undated future entries are included, does not generate dates and has no effect on past changes. Unknown timestamps sort before known dates in ascending order and after them in descending order. Treat them as date unknown, not confirmed reminder deadlines.