IMDb-API

Name: IMDb-API
Brand: IMDb-API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentMediaContent DeliveryapiKey29 EndpointsREST

For Agents

Search IMDb for titles, people, and companies, and pull ratings, full cast, episodes, reviews, and trailers from a single REST surface.

Install Jentic One Beta

Connect the IMDb-API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the IMDb-API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with IMDb-API.

Search IMDb by title, movie, series, name, or company name

Look up full title details by IMDb ID including plot, runtime, and language

Retrieve the full cast and crew for a title

Pull aggregated and per-source ratings for a title

GET STARTED

Start building with IMDb-API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use IMDb-API for, with concrete tasks.

★ Movie Discovery and Recommendation Apps

Side-project recommendation apps and watchlist tools need a reliable source of titles, ratings, and metadata. IMDb-API exposes the search and lookup surface that powers a 'find movies similar to X' flow: search by title, retrieve the IMDb ID, and pull ratings plus poster art for each result. The 29-endpoint surface covers most fan-app needs without scraping IMDb directly.

GET /SearchTitle/{apiKey}/{expression} for the user's query, then for each result call /Title/{apiKey}/{id} and /Ratings/{apiKey}/{id} to assemble the result card.

TV Series Episode Trackers

Series tracking apps need season-by-season episode lists with air dates and short synopses. /SeasonEpisodes returns the episode list per season for a given series ID, which a tracker can store locally and refresh weekly. Combined with /UserRatings the same view shows community scores per episode.

GET /SeasonEpisodes/{apiKey}/{id}/{seasonNumber} for each known season of a series and persist the episode list with air dates.

Cast and Crew Enrichment for Editorial

Editorial sites running interviews and reviews want a structured cast credit list per article subject. /FullCast returns the cast and crew for a title and /Name returns biographical detail per credit. Editors can render filmographies and 'related people' sections without manual research.

GET /FullCast/{apiKey}/{id}, then for each top-billed cast member call /Name/{apiKey}/{id} to enrich the article with biography snippets.

Agent-Driven Movie Q&A

An assistant that answers movie trivia questions can search IMDb-API by title, fetch the canonical record, and cite ratings and awards in its answer. Through Jentic the agent finds the right operation by intent and runs it without juggling 29 endpoint signatures or remembering the path-based API key pattern.

Search Jentic for 'look up a movie by title on IMDb', execute /SearchTitle followed by /Title and /Ratings, and cite the returned data in the answer.

Key Endpoints

29 endpoints — jentic publishes the only available openapi specification for imdb-api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

GET

/SearchTitle/{apiKey}/{expression}

Search titles by free-text expression

GET

/Title/{apiKey}/{id}

Look up full title details

GET

/FullCast/{apiKey}/{id}

Retrieve full cast and crew

GET

/Ratings/{apiKey}/{id}

Retrieve aggregated ratings

GET

/SeasonEpisodes/{apiKey}/{id}/{seasonNumber}

List episodes in a season

GET

/Name/{apiKey}/{id}

Look up a person's details

GET

/SearchName/{apiKey}/{expression}

Search people by name

GET

/SearchTitle/{apiKey}/{expression}

Search titles by free-text expression

GET

/Title/{apiKey}/{id}

Look up full title details

GET

/FullCast/{apiKey}/{id}

Retrieve full cast and crew

GET

/Ratings/{apiKey}/{id}

Retrieve aggregated ratings

GET

/SeasonEpisodes/{apiKey}/{id}/{seasonNumber}

List episodes in a season

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

The IMDb-API key is stored encrypted in the Jentic vault and inserted into the path at execute time. Because the key sits in the URL path, vaulting is especially valuable - the agent never builds the URL by hand.

Intent-based discovery

Agents search by intent (e.g., 'look up a movie by title on IMDb') and Jentic returns the matching operation among the 29 endpoints with its parameter schema, removing the need to memorise the path-based key pattern.

Time to first call

Direct IMDb-API integration: half a day to handle the path-based auth and 29 endpoint signatures. Through Jentic: minutes per operation - search, load, execute.

FAQs

Specific to using IMDb-API through Jentic.

Why is there no official OpenAPI spec for IMDb-API?

IMDb-API.com is a third-party reseller of IMDb data and does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call IMDb-API via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.

What authentication does the IMDb-API use?

The API uses an API key passed as a path parameter on every endpoint, not a header. For example, /SearchTitle/{apiKey}/{expression}. Through Jentic the key is stored in the encrypted vault and inserted into the path at execute time.

Can I list all episodes for a series?

Yes. GET /SeasonEpisodes/{apiKey}/{id}/{seasonNumber} returns the episodes in a given season. Iterate through known season numbers to assemble a full episode list for a series.

Can I look up the full cast for a film?

Yes. GET /FullCast/{apiKey}/{id} returns the cast and crew for a title. For deeper biographical detail on a specific person, follow up with /Name/{apiKey}/{id}.

How do I search IMDb through Jentic?

Run pip install jentic, search for 'search IMDb for a movie title', load the /SearchTitle schema, and execute with the user's query expression. Jentic supplies the API key from the vault.

What are the rate limits for IMDb-API?

The OpenAPI spec does not list explicit rate limits. IMDb-API enforces per-plan request quotas on imdb-api.com; back off on HTTP 429 responses if running batch enrichment over thousands of titles.