What You Can Do With TheIntroDB's Free API

TheIntroDB's free API gives you programmatic access to community-verified timestamps for intros, recaps, credits, and previews in TV shows and movies. You can use it to build skip-button logic into a media player, automate skipping in your own playback setup, or feed timestamp data into tools that don't already have a TheIntroDB plugin. The API is described as free, but the available material doesn't specify rate limits, authentication requirements, or terms of use, so confirm those on the site before relying on it in production.

What the API actually provides

The core data is a set of exact timestamps marking where segments begin and end:

• Intros — the opening title sequence
• Recaps — "previously on" segments
• Credits — end credits
• Previews — next-episode or trailer segments

Timestamps are described as community-verified, meaning entries are contributed and checked by users rather than generated automatically. That matters for how you design around the API: coverage and accuracy will vary by title, so your integration should handle missing or unconfirmed data gracefully rather than assuming every episode has a complete set.

Practical ways to use it

Add skip controls to a player or frontend

If you maintain a media player, a custom web frontend, or a home-theater dashboard, you can query the API for a title's timestamps and render skip buttons at the right moments. The typical flow:

1. Identify the playing item (show, season, episode, or movie) using whatever ID scheme the API expects.
2. Request the timestamp record for that item.
3. When playback crosses a segment start time, show a skip action; seek to the segment end time when the user accepts.

The expected result is a skip prompt that appears at the correct moment without hardcoding times per episode.

Automate skipping in your own setup

For personal automation — a script that pre-fetches timestamps for a watchlist, or a scheduled job that caches data locally — the API removes the need to scrub through episodes manually. Fetch once, store the timestamps alongside your library metadata, and your playback tooling can skip without a network call mid-episode.

Fill gaps where plugins don't reach

TheIntroDB offers plugins for Jellyfin, Emby, Kodi, and similar players. The API is the path for everything else: a player without a plugin, a custom client, or a workflow that isn't a media player at all. If a supported plugin already covers your setup, using it is simpler than building against the API; reach for the API when no plugin exists or when you need the data inside another tool.

Build verification or curation tooling

Because the data is community-verified, there's room for tools that help review or improve entries — for example, a script that flags episodes with missing segments so contributors know where to look. This is a reasonable use of the API if you're active in the community, but treat it as a secondary use case until you've confirmed what write access, if any, the API allows.

What to check before you build

The available material doesn't cover several details you'll need for a real integration:

The practical takeaway: the API is positioned as free and open for building player integrations and automation, and the timestamp data is the same community-verified set behind the plugins. Start by confirming the endpoint and auth details on the site, then build your integration to tolerate missing segments, since community coverage won't be uniform across every title in your library.