/tmdb/movies/discover

POST /api/tmdb/movies/discover

Price: 5 credits

Discover TMDB movies by advanced filters: genres, certification, release date range, original language, user score and vote count, runtime, keywords, streaming providers and release type, with sorting.

How to use it

Advanced movie discovery with rich filters. Combine genres, certification, release_date_from/to, original_language, user_score_min/max, min_votes, runtime_min/max, keywords, watch_providers, watch_monetization and release_types, ordered by sort. Region selects the certification/availability market. Each result has id, media_type, url, document_title, date and image. Set count for how many to return.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• user_score_min number — Minimum user score (0-10) (default: 0; min: 0; max: 10)
• user_score_max number — Maximum user score (0-10) (default: 10; min: 0; max: 10)
• min_votes integer — Minimum number of user votes (default: 0; min: 0)
• runtime_min integer — Minimum runtime in minutes (default: 0; min: 0)
• runtime_max integer — Maximum runtime in minutes (default: 400; min: 0)
• original_language string nullable — Original language filter (ISO 639-1, e.g. 'en', 'ja') (pattern: ^[a-z]{2}$)
• keywords array — Filter by TMDB keyword IDs (default: [])
• watch_providers array — Filter by TMDB watch provider IDs (default: [])
• watch_monetization array — Filter by streaming availability types (default: []; one of: "flatrate", "free", "ads", "rent", "buy")
• region string — Country market for certification and streaming availability (default: "US"; one of: "AL", "DZ", "AD", "AO", "AG", "AR", "AU", "AT", "AZ", "BS", "BH", "BB", "BY", "BE", "BZ", "BM", "BO", "BA", "BR", "BG", "BF", "CM", "CA", "CV", "TD", "CL", "CO", "CR", "HR", "CU", "CY", "CZ", "CI", "CD", "DK", "DO", "EC", "EG", "SV", "GQ", "EE", "FJ", "FI", "FR", "GF", "PF", "DE", "GH", "GI", "GR", "GP", "GT", "GG", "GY", "HN", "HK", "HU", "IS", "IN", "ID", "IQ", "IE", "IL", "IT", "JM", "JP", "JO", "KE", "XK", "KW", "LV", "LB", "LY", "LI", "LT", "LU", "MK", "MG", "MW", "MY", "ML", "MT", "MU", "MX", "MD", "MC", "ME", "MA", "MZ", "NL", "NZ", "NI", "NE", "NG", "NO", "OM", "PK", "PS", "PA", "PG", "PY", "PE", "PH", "PL", "PT", "QA", "RO", "RU", "SM", "SA", "SN", "RS", "SC", "SG", "SK", "SI", "ZA", "KR", "ES", "LC", "SE", "CH", "TW", "TZ", "TH", "TT", "TN", "TR", "TC", "UG", "UA", "AE", "GB", "US", "UY", "VA", "VE", "YE", "ZM", "ZW")
• count integer required — Max number of results to return (min: 1)
• sort string — Result ordering (default: "popularity.desc"; one of: "popularity.desc", "popularity.asc", "vote_average.desc", "vote_average.asc", "primary_release_date.desc", "primary_release_date.asc", "title.asc", "title.desc", "revenue.desc", "revenue.asc")
• genres array — Filter by movie genres (all must match) (default: []; one of: "Action", "Adventure", "Animation", "Comedy", "Crime", "Documentary", "Drama", "Family", "Fantasy", "History", "Horror", "Music", "Mystery", "Romance", "Science Fiction", "TV Movie", "Thriller", "War", "Western")
• certification string nullable — Filter by content rating in the selected region (one of: "NR", "G", "PG", "PG-13", "R", "NC-17")
• release_date_from string nullable — Earliest release date (YYYY-MM-DD) (pattern: ^\d{4}-\d{2}-\d{2}$)
• release_date_to string nullable — Latest release date (YYYY-MM-DD) (pattern: ^\d{4}-\d{2}-\d{2}$)
• release_types array — Filter by release type (default: []; one of: "1", "2", "3", "4", "5", "6")

Response

• @type string (default: "TmdbMediaItem")
• id integer required
• media_type string required
• url string required
• document_title string nullable
• date string nullable
• image string nullable

Errors

• 422 — The request body did not validate Check the fields against this schema. A URN with the wrong prefix is the most common cause.
• 408 — The request ran past its time limit Raise `timeout` in the request body, up to the maximum this endpoint documents. Lowering `count` or turning off the `with_*` flags also helps, because less work finishes sooner.
• 412 — The entity was not found, or a precondition failed Retrying will not help: either the entity does not exist, or the input points at a different one.
• 429 — Too many requests: a rate limit or a usage window is exhausted When the response carries an X-Retry-After header, wait that many seconds and retry: the same number is in the body as `detail.retry_after`, and the limit clears once that window passes. The message in the body names the limit that was hit.
• 500 — Something broke on our side Retrying will not help. If it keeps happening, send us the X-Request-ID from the response headers.
• 529 — Rate limit reached, or the endpoint is overloaded Wait at least 30 seconds, then retry.

Response headers

• X-Error — Error message text (present only on error)
• X-Request-ID — Unique request identifier
• X-Execution-Time — Execution time in seconds
• X-Result-Count — How many records the body carries. 0 means an empty result, which is a normal answer and not by itself an error. A non-zero count can come back together with X-Error when the failure happened partway through — read this header and X-Error independently.
• X-Total-Available-Results — How many records exist for this query, when the endpoint can say. On a `dry_run` request this is the answer and the body is empty. It saturates: the endpoint's documented maximum means 'at least that many', any smaller number is exact.
• X-Warning — Present when the request body carried keys this endpoint does not document. They were ignored, so any filter you meant to apply through them did not apply. Check the spelling against this schema and retry.
• X-Retry-After — Seconds to wait before retrying. Present only on 429.