A free community database API is the best movie data API for titles, cast, plots, ratings and posters, and it'll carry a hobby or indie app a long way. Where a film is streaming tonight is a separate, usually paid, dataset, and official IMDb data is a licensed purchase of its own.
Getting a film's title, cast list and poster into your app costs you an API key and an afternoon. Telling a user which service it's streaming on in their country tonight is a different business altogether, with different suppliers and a very different bill. Your project probably needs one of those far more than the other, so it's worth knowing which before you sign up for anything.
The short answer for movie and TV data
If you're building a watchlist, a film diary, a quiz or a recommendation side project, start with a free community database. You'll get titles, release dates, cast and crew, plots, genres and images, and the trade is that you follow the community's terms and live within its rate limits.
If your product's whole promise is "where can I watch this", budget for a streaming availability API from day one. That data changes constantly as titles move between services and countries, and keeping it current is what those suppliers charge for.
If you need the IMDb name, its ratings and box office figures under a commercial licence, that's a licensed data purchase, not a free key. And for TV-first apps, a TV-focused database is built around shows, seasons and episodes from the start.
Free community databases
TMDB API
The community-built database behind plenty of movie apps, covering films, TV, actors and images, with a key from your own account.
OMDb API
A small, Patreon-supported web service that returns movie information by title or ID, a simple pick for quick lookups.
TVmaze API
For television rather than film, a free public REST API on shows, episodes and schedules, plus a user-level API for Premium members.
TheTVDB API
Community-contributed TV and movie metadata, offered as an API and as licensed data for commercial products.
MDBList API
Ratings gathered from several sources and user-made lists sit behind this API from mdblist.com, which hands out free keys.
Trakt API
Built on what people watch and track on Trakt, useful for apps that care about viewing history and lists.
Licensed and streaming availability data
IMDb API
Official IMDb metadata, ratings and box office data through a GraphQL-backed API, bought as a licensed dataset.
Watchmode API
Streaming availability together with metadata, cast and awards, made for where-to-watch features in movie and TV apps.
Streaming Availability API (Movie of the Night)
Developers who need to show which of the big streaming services carries a title, country by country, can start with this API.
Want AI doing the heavy lifting in your marketing?
I build the systems that handle the boring 80 percent, so you get your week back. Done properly, with the human kept in.
Metadata and where-to-watch are separate jobs
Metadata barely moves. A film's director, runtime and cast are the same next year as today, which is why community databases can serve it freely and why you can cache it hard on your side. Streaming availability is the opposite: a title can leave one service and arrive on another overnight, and the answer differs by country. That's the reason it's a paid niche of its own, and why the suppliers in it talk about credits, countries and services rather than films.
Mixing the two is common and sensible. Use a free database for the pages people browse, then call an availability API only when someone opens a title and wants to watch it. You'll spend availability credits on intent, not on every poster in a grid.
The terms that come with free data
Free doesn't mean unconditional. Read the terms before you design your screens, because some of them shape the layout.
- Attribution: community databases often ask you to credit them visibly, and TheTVDB asks for a direct link unless it's approved otherwise.
- Commercial use: a key that's fine for a personal project may need a commercial agreement once you charge users or show ads.
- Caching and storage: check how long you're allowed to keep data and images on your own servers.
- Images: posters and stills can carry their own rules, separate from the text metadata.
- Keys and accounts: some keys come from a developer account, others through a supporter scheme, and losing access can take your app down.
Open-source projects should look for discounts or free licences, as some providers offer them, and ask before assuming a commercial tier is needed.
Rate limits, daily caps and credits
This is where the money and the outages hide. Free APIs tend to protect themselves with rate limits: TVmaze, for instance, says it allows at least twenty calls every ten seconds per IP address. Others give a fixed number of calls a day on a free key, and once you pass it, requests fail until the next day.
Paid availability data is usually sold in monthly credit bundles, with a free developer tier at the bottom and larger bundles as your traffic grows. The tiers and what a credit buys sit on each vendor's pricing page, so model your likely calls per user per month before comparing them. Licensed IMDb data works differently again: it's bought as a data product through a cloud data exchange, so expect a sales conversation, not a sign-up form.
A cache in front of any of these is the single biggest saving. Store the metadata you've fetched, refresh it on a slow schedule, and keep the live calls for the data that changes. If you're planning other data feeds alongside this one, the guide to weather APIs covers the same caps-versus-credits trade in a different field.
Do you make movie data APIs? Tool makers can ask to be considered for a featured place on this list.
Matching one title across databases
Sooner or later you'll join data from two sources, and that's where movie data gets messy. Remakes share titles, foreign films go by different names, release years differ by country, and TV specials sit awkwardly between seasons.
Here's an hour-long test. Pick ten awkward titles: a remake and its original, a foreign-language film, a series with specials, a recent release, an old classic and a documentary. Look each one up in two APIs you're considering. Note whether the IDs line up, whether the year and runtime agree, whether the images are there, and how many calls each lookup took. Store every source's own ID against your record, plus any shared ID a source returns, and you'll be able to switch suppliers later without rebuilding your catalogue.
Building it so you can switch later
I'd keep each provider behind a thin layer in your own code, so swapping one free database for another, or adding an availability API later, is a change in one place. Free services change their terms and paid ones change their tiers, and the apps that cope best are the ones that never let a single supplier's field names leak into every screen. Building something with sports or live scores too? The sports data APIs list covers that side.
Want your tool on this list? Featured spots and reviews here are paid partnerships. Here's how to partner with me.

