IMDb title public facts analysis API

Endpoint facts

Method

GET

API path

/imdb/title/public-facts-analysis

Auth

apiKey

Credits

5 credits/request

Platform

IMDb

Response schema

#/definitions/imdb.titlePublicFactsAnalysisResponseDoc

Overview

Returns derived public-page summary metrics for IMDb trivia, goofs, quotes, keywords, filming locations, and company credits. This endpoint is not viewing advice. Pass exactly one of `id` or `url`. The six sections are gathered from six independent sources, so a section that cannot be fetched is omitted and named in `missing_sections` with `partial` set to `true`, rather than failing the whole response; an error is returned only when no section could be fetched. Callers that require a complete analysis should check `partial`. Developers commonly use this endpoint for data enrichment, monitoring, research dashboards, internal automation, and agent-native workflows that need repeatable structured public web data. Authentication uses the documented Crawlora headers, and usage is metered with the credit cost shown on this page.

Authentication

Send your scraping API key in the x-api-key header. Use the console API Keys page to rotate or select the active key.

Billing

Endpoint usage is metered in credits. The plan prices, included credits, limits, and overage rates below match the active backend billing configuration.

Credit cost

5 credits/request

Charged response

Successful 2xx responses

Infrastructure behavior

This endpoint is executed through Crawlora's managed scraping infrastructure.

• Proxy strategy: managed automatically where needed
• Browser rendering: enabled for supported targets that require rendered HTML or JavaScript execution
• Browser cluster: supported dynamic workloads can be routed through distributed browser instances
• Retry behavior: automatic retry/fallback may be used depending on endpoint type
• Challenge handling: challenged pages or unusable upstream HTML are detected and surfaced clearly when they cannot be used
• Billing: credits are charged only for successful 2xx responses
• Observability: responses include request context where available

Response behavior

- `data.summary` includes counts for trivia, goofs, quotes, keywords, filming locations, company sections, companies, spoiler-marked public facts, public page signals, and source-page coverage. - `data.trivia`, `data.goofs`, `data.quotes`, `data.keywords`, `data.filming_locations`, and `data.company_credits` contain the underlying normalized page payloads. - The six sections come from six independent sources. A section that cannot be fetched is omitted from the response instead of failing the whole request: `data.partial` is then `true` and `data.missing_sections` lists the omitted section keys (`trivia`, `goofs`, `quotes`, `keywords`, `filming_locations`, `company_credits`). `data.summary` counts only the sections that arrived, so callers that require a complete analysis should check `data.partial` rather than infer completeness from the `200`. - An upstream error is returned only when no section could be fetched. - IMDb WAF or robot-verification pages return an upstream error. Example response: ```json { "code": 200, "msg": "OK", "data": { "summary": { "trivia_count": 12, "goof_count": 4, "quote_count": 8, "keyword_count": 20, "filming_location_count": 6, "company_section_count": 3, "company_count": 9, "spoiler_fact_count": 2, "public_page_signals": 64, "public_fact_coverage_pages": 6 }, "not_viewing_advice": true, "public_page_derived": true, "partial": false } } ```

Error behavior

Crawlora does not silently return bad data when the upstream page cannot be used.

When possible, Crawlora returns structured error context so your integration can retry, back off, or inspect the request.

Related