IMDb title connections API

Endpoint facts

Method

GET

API path

/imdb/title/connections

Auth

apiKey

Credits

3 credits/request

Platform

IMDb

Response schema

#/definitions/imdb.titleConnectionsResponseDoc

Overview

Returns a bounded slice of a title's public connections: other titles it references or is referenced by, such as remakes, spin-offs, "featured in" clips, and "edited into" compilations. `category` is upstream-supplied free text, not a closed enum. IMDb's connections list can run to hundreds or thousands of rows, so `total` can exceed the returned rows and `has_more` reports that condition. Limit defaults to 50 and clamps to 250. Pass exactly one of `id` or `url`. 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

3 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

- `connections[].category` is upstream-supplied free text (for example `Featured in`, `Referenced in`, `Spoofed in`, `Edited into`), not a closed enum — there is no filter parameter for it. - `connections[].note` is an optional editorial note IMDb attaches to some rows; many rows have none. - `connections[].associated_title.title_type` and `.year` are included when IMDb supplies them. - IMDb's connections list can run to hundreds or thousands of rows for a popular title. `total` is the upstream count and `has_more` is true whenever the returned slice is shorter than `total`. - A well-formed but unresolvable title ID returns a not-found error. - A real title with genuinely zero connections returns 200 with an empty `connections` list. - If IMDb changes the shape of this data, the endpoint fails closed with an upstream parser-drift error. Example response: ```json { "code": 200, "msg": "OK", "data": { "id": "tt0111161", "title": "The Shawshank Redemption", "limit": 50, "url": "https://www.imdb.com/title/tt0111161/", "total": 999, "has_more": true, "connections": [ { "category": "Featured in", "note": "Clips appear in the teaser for next week's show.", "associated_title": { "id": "tt1936736", "title": "Why Gump? Why Now?", "url": "https://www.imdb.com/title/tt1936736/", "title_type": "TV Episode", "year": 1994 } } ] } } ```

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