domain: developer.themoviedb.org · 6 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Register for a TMDB account and generate an API Read Access Token from the API settings page.
To find a movie by title, send a GET request to the search/movie endpoint with a query parameter containing the movie title, optionally adding year to narrow results.
Include your Read Access Token as a Bearer token in the Authorization header.
From the search results array, identify the correct movie and note its id.
Retrieve full metadata by sending a GET request to the movie details endpoint (/movie/{movie_id}), optionally appending related data using the append_to_response parameter (e.g., credits, videos, release_dates).
Parse the response for fields such as title, overview, release_date, genres, runtime, and vote_average.
Known gotchas
TMDB uses two authentication methods: an older api_key query parameter and the newer Bearer token approach; the Bearer token method is preferred for new integrations.
Some data (adult content, certain regional data) may be filtered by default; consult the TMDB docs for account-level settings that affect API responses.
TMDB enforces rate limits; implement backoff logic if you receive 429 responses during bulk lookups.
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?