Pricing overview

TVDB provides API access through a tiered subscription model, designed to accommodate a range of users from individual developers to larger applications. The core offering revolves around access to extensive metadata for TV series, movies, anime, and related entities. The primary differentiator between plans is the daily API call limit, with higher tiers offering significantly increased allowances.

The pricing structure begins with a free tier, referred to as the Developer Plan, which offers a foundational level of access for testing and small-scale personal use. Beyond this, users can opt for paid plans that scale up in cost and API call capacity. All plans include access to TVDB's comprehensive metadata, covering details such as cast, crew, episode information, plot summaries, and image assets. Authentication for the API utilizes an OAuth 2.0 based system, requiring developers to obtain a token for authorized requests.

For detailed information on current pricing and specific plan features, the official TVDB API pricing page is the authoritative source. The API is suitable for various applications, including media organizers, content discovery platforms, and applications that enrich existing media libraries with detailed information.

Plans and tiers

TVDB's API access is structured into several plans, each with distinct daily API call limits and pricing. These plans are designed to scale with usage requirements, ensuring that developers can choose a tier that aligns with their project's needs.

Plan Name Monthly Price Daily API Call Limit Best For
Developer Plan Free 500 calls Initial testing, personal scripts, small development projects
Personal Plan $2.50 10,000 calls Hobby projects, small applications, individual media library management
Standard Plan $7.50 50,000 calls Growing applications, community projects, moderate user bases
Professional Plan $15.00 100,000 calls Commercial applications, larger user bases, content platforms
Enterprise Plan Contact Sales Custom Large-scale commercial applications, high-volume data needs

Each plan provides access to the full suite of TVDB's metadata, including endpoints for TV series, movies, anime, companies, and list management. The primary constraint across tiers is the number of requests per 24-hour period. Users can upgrade or downgrade their plans as their usage patterns change, providing flexibility. For custom requirements exceeding the Professional Plan's limits, an Enterprise Plan is available, requiring direct contact with TVDB sales for tailored solutions and pricing.

Free tier and limits

The Developer Plan serves as TVDB's free tier, offering a practical entry point for new users and small-scale projects. This plan provides 500 API calls per day, which is sufficient for initial development, testing API integrations, and managing personal media collections with infrequent updates.

Key aspects of the free tier:

  • Daily Limit: 500 API calls per 24-hour period.
  • Access: Full access to the TVDB API, including metadata for TV series, movies, and anime.
  • Target Audience: Ideal for students, hobbyists, and developers evaluating the API before committing to a paid plan.

While the Developer Plan offers full API functionality, developers should be mindful of the daily call limit. Exceeding this limit will result in rate-limiting, where subsequent requests may be temporarily blocked until the 24-hour window resets. For projects requiring more consistent or higher-volume access, upgrading to a paid plan is necessary. The free tier allows developers to build and test applications against real-world data without an initial financial commitment, aligning with common practices for cloud service free tiers.

Real-world cost examples

Understanding TVDB's pricing in practical terms helps developers estimate their monthly expenses based on projected API usage. Here are several scenarios:

Scenario 1: Personal Media Organizer

A developer creates a personal application to organize their home media library, fetching metadata for new additions. They might add 5-10 new series or movies per week, each requiring a few API calls for search and detail retrieval. This usage translates to approximately 50-100 API calls per week, well within the Developer Plan's 500 daily limit. The cost for this scenario is $0 per month.

Scenario 2: Small Community Fan Site

A fan site for a popular TV show displays episode information, cast details, and user ratings. With around 100 daily active users, each typically viewing 2-3 pages that trigger API calls, the site could generate 200-300 API calls per day. Occasional spikes for new episode releases might push this higher. The Personal Plan, offering 10,000 daily calls for $2.50 per month, would comfortably accommodate this usage, providing ample headroom.

Scenario 3: Niche Content Discovery App

An application focused on discovering obscure anime series experiences moderate growth, reaching 1,000 daily active users. If each user performs an average of 3-5 searches and detail views daily, this could result in 3,000-5,000 API calls per day. On days with higher engagement or new content releases, this could reach 7,000-8,000 calls. The Standard Plan, at $7.50 per month for 50,000 daily calls, would provide robust capacity for this level of activity, significantly exceeding the projected usage and offering room for further growth without immediate concern of rate limits.

Scenario 4: Commercial Media Management Platform

A startup developing a commercial platform for managing content across multiple streaming services requires frequent metadata updates and searches. With thousands of active users generating tens of thousands of API calls daily for various features like personalized recommendations, library syncing, and content discovery, the platform would likely require the Professional Plan (100,000 daily calls for $15.00 per month) or even the tailored Enterprise Plan for custom limits and support. The actual cost would depend on specific usage patterns and negotiated terms for the Enterprise tier.

How the pricing compares

When evaluating TVDB's pricing, it's useful to compare it against alternative metadata APIs available in the market. Key alternatives include TMDB (The Movie Database) and OMDb API.

  • TMDB (The Movie Database): TMDB offers a similar scope of movie and TV show metadata. Its API is generally free for non-commercial use, with commercial use requiring specific compliance and potentially higher-tier access depending on scale. TMDB's free access model for non-commercial projects can be attractive for hobbyists, but commercial users need to adhere to their terms of use which may involve attribution and other requirements. TVDB's clear tiered subscription model provides predictable costs for commercial applications.

  • OMDb API (The Open Movie Database API): OMDb API offers a free tier with 1,000 daily requests, which is double TVDB's free tier. It also offers a patron subscription for $10/month providing 100,000 requests/day. OMDb API's focus is primarily on movies and TV shows, similar to TVDB. Its pricing can be more competitive than TVDB's for mid-range usage, offering 100,000 calls for $10 compared to TVDB's $15 for the same limit. However, TVDB often boasts a more comprehensive dataset, especially for TV series and niche content, which might justify its pricing for specific use cases.

  • IMDb API (via RapidAPI): The IMDb API available through platforms like RapidAPI often operates on a pay-as-you-go or tiered subscription model set by the RapidAPI platform and the API provider. Pricing can vary widely and may include request-based fees, making cost prediction potentially more complex than TVDB's fixed monthly subscriptions. While IMDb's dataset is extensive, accessing it via third-party aggregators can introduce additional costs and platform dependencies, as described by API gateways.

Overall, TVDB's pricing is competitive, particularly for projects that require a predictable monthly cost and comprehensive TV series data. Its free tier provides a solid starting point, and its paid plans scale linearly with usage, offering clear value propositions at each level. Developers should consider not only the cost per call but also the breadth and accuracy of the metadata provided by each service when making a decision.