canonical: https://jentic.com/apis/themoviedb.org/themoviedb

# Themoviedb TMDb API

The Movie Database (TMDb) API v3. Community-based movie and TV data including search, details, ratings, and account management. The API exposes 37 endpoints secured with bearer authentication.

## For AI agents

Programmatically validate API key, create guest session. Covers 37 operations with bearer authentication.

## Scope

Does not handle payments, communications, or crm - use for developer tools only.

## Capabilities

- Validate API key
- Create guest session
- Get account details
- Mark as favorite
- Monitor TMDb API operational status and events

## Use cases

### Developer Tools Operations

Use the TMDb API to perform developer tools operations programmatically. The API provides 37 endpoints covering core functionality including validate API key, create guest session, create request token.

Example prompt: Call GET /3/authentication to validate API key

### Automated Authentication Management

Automate authentication operations by combining multiple TMDb API endpoints. Agents can create guest session and then create request token in a single workflow.

Example prompt: Call GET /3/authentication/guest_session/new to create guest session, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call TMDb API endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle bearer tokens manually.

Example prompt: Search Jentic for 'validate API key', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | /3/authentication | Validate API key |
| GET | /3/authentication/guest_session/new | Create guest session |
| GET | /3/authentication/token/new | Create request token |
| POST | /3/authentication/session/new | Create session |
| GET | /3/account/{account_id} | Get account details |
| POST | /3/account/{account_id}/favorite | Mark as favorite |
| GET | /3/account/{account_id}/favorite/movies | Get favorite movies |
| GET | /3/account/{account_id}/favorite/tv | Get favorite TV shows |

## Key resources

- **Authentication** — API key validation and session management
- **Account** — User account management, favorites, watchlists, and ratings
- **Movies** — Movie details, lists, and ratings
- **TV Series** — TV show details, lists, and ratings
- **People** — Person details and popular people

## Why Jentic

- **Setup:** Wiring TMDb by hand means handling its v4 bearer token, walking the session and request-token authentication flow, and coding your own retries. Through Jentic you install once, import TMDb from the API Directory, store the token once, and your agent calls it.
- **Permission scoping:** TMDb puts the account id in the URL path (/3/account/{account_id}/...), so a rule can pin your agent to one account: it can read details and manage favorites for that account and nothing else. You choose the operations it may call, so write actions like marking favorites or watchlist changes are not included unless you add them.
- **Credential handling:** Your TMDb token is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'search for a movie' or 'get account favorites', and Jentic returns the matching TMDb operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Github** — Alternative developer tools API
- **Gitlab** — Alternative developer tools API

## FAQ

### What authentication does the TMDb API use?

The TMDb API uses a Bearer token in the Authorization header. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context.

### Can I validate API key with the TMDb API?

Yes. Use the GET /3/authentication endpoint. The API returns structured JSON responses that agents can parse and act on directly.

### What are the rate limits for the TMDb API?

Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.

### How do I validate API key through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'validate API key'. Jentic returns the matching TMDb API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the TMDb API have?

The TMDb API exposes 37 endpoints covering authentication, account, movies operations.

### Can I limit what my agent is allowed to do with the TMDb API?

Yes. Because you run Jentic One yourself, your own rules decide which TMDb operations and credentials the agent may use. Since TMDb puts the account id in the URL path, such as /3/account/{account_id}/favorite/movies, you can pin the agent to a single account so it only reads that account's details and favorites and touches nothing else. You also pick the exact operations it may call, so write actions like POST /3/account/{account_id}/favorite are excluded unless you explicitly allow them.