Get a person's films by name: actor, director, writer, producer, composer and more.
Filmography returns the films a person worked on, newest first, from their name or Wikidata id: each film's title, year and the person's roles in it, such as director and writer. Filter by role to get only the films someone directed or acted in. When several people share a name, the best-known comes first and the others are listed with a film they are known for. Covers the cast and crew of about 450,000 films.
Try it — live request, no key required
No key required to try it. Get a key to use it in your app.
{
"status": "ok",
"error": null,
"data": {
"name": "Christopher Nolan",
"id": "Q25191",
"role": "any",
"count": 10,
"filmsTotal": 21,
"roles": {
"director": 17,
"writer": 15,
"producer": 13,
"actor": 3,
"cinematographer": 3,
"editor": 1
},
"films": [
{
"title": "The Odyssey",
"year": 2026,
"roles": [
"director",
"writer",
"producer"
],
"id": "Q131547207"
},
{
"title": "Oppenheimer",
"year": 2023,
"roles": [
"director",
"writer",
"producer"
],
"id": "Q108839994"
},
{
"title": "Tenet",
"year": 2020,
"roles": [
"director",
"writer",
"producer"
],
"id": "Q63985561"
},
{
"title": "Dunkirk",
"year": 2017,
"roles": [
"director",
"writer",
"producer"
],
"id": "Q21935651"
},
{
"title": "Behind the Scenes",
"year": 2017,
"roles": [
"actor"
],
"id": "Q108257926"
},
{
"title": "Quay",
"year": 2015,
"roles": [
"director"
],
"id": "Q21869743"
},
{
"title": "Interstellar",
"year": 2014,
"roles": [
"director",
"writer",
"producer"
],
"id": "Q13417189"
},
{
"title": "Transcendence",
"year": 2014,
"roles": [
"producer"
],
"id": "Q10384115"
},
{
"title": "Man of Steel",
"year": 2013,
"roles": [
"writer",
"producer"
],
"id": "Q622769"
},
{
"title": "The Dark Knight Rises",
"year": 2012,
"roles": [
"director",
"writer",
"producer"
],
"id": "Q189330"
}
],
"otherMatches": [],
"dataAsOf": "2026-11-22"
}
}
About the Filmography API
A filmography API for apps that browse movies by people: actor pages, director retrospectives, six-degrees games, trivia and recommendation engines that follow a favourite actor. Search by name in any case, with or without accents, or look up exactly by Wikidata id.
Every plan gets the person's name and id, the number of films on record and up to 10 films, newest first, each with its title, year, the person's roles in it and the film's Wikidata id, which Movie Lookup accepts for the full film record. A role filter narrows to director, actor, writer, producer, composer, cinematographer or editor. Paid plans return up to 50 films and a count of films per role. When a name is shared, otherMatches lists up to five other people with a film each is known for, so you can retry with their id.
Data is refreshed monthly from the same catalog as Movie Lookup.
How it works
Pass name or id. A name search ignores case, accents and punctuation; when several people share the name, the best-known (by worldwide encyclopedia coverage) is returned and up to five others appear in otherMatches with a film they are known for. No match returns 404.
Films come newest first; films without a recorded year come last. roles lists every role the person had on that film, so a writer-director shows both. role filters to one role, and filmsTotal counts the films matching it. Each film's id is its Wikidata id, which Movie Lookup accepts as id for the full record.
Credits come from Wikidata (CC0) and are refreshed monthly with Movie Lookup.
What people use it for
- Actor and Director Pages
- Build person pages that list every film someone made, newest first, with their role in each.
- Movie Discovery
- Let users jump from a film to everything else its director or lead actor worked on.
- Trivia and Connection Games
- Power six-degrees and who-directed-what games from credits across 450,000 films.
- Recommendation Engines
- Recommend films by following the people behind a viewer's favourites.
Ways to call it
One endpoint, many ways in — REST with JSON, XML, YAML and CSV, plus GraphQL and an MCP interface for AI agents.
- JSON
- Default REST response
- XML
- Markup format
- YAML
- Human-readable
- CSV
- Tabular export
- GraphQL
- Query language
- MCP
- For AI agents
Other ways to use Filmography
Same data, same APIVerve account, same credit balance — one key works on all of them.
Which people are covered?
What does the Free plan return?
What if two people share a name?
Which plan fits 50,000 lookups a month?
Where does the data come from?
Request parameters — GET /v1/filmography
Sent in the query string. Premium parameters are accepted on every plan but only take effect on plans that include them. Anything not listed here is dropped rather than passed through.
Optional
| Parameter | Type | Example | Description |
|---|---|---|---|
nameOptional | string | Christopher Nolan | Person name, e.g. Christopher Nolan. Use name or id length 0-120 |
idOptional | string | Q25191 | Wikidata id of the person, e.g. Q25191 length 0-12 |
roleOptional | string | director | Only films with this roleanydirectoractorwriterproducercomposercinematographereditordefault any |
limitOptionalPremium | integer | 25 | Maximum films to return (1-50) default 10 · range 1-50 |
curl "https://api.apiverve.com/v1/filmography?name=Christopher%20Nolan&id=Q25191&role=director&limit=25" \
-H "x-api-key: YOUR_API_KEY"Authentication
Send your key in the x-api-key header. That is the only auth step — no token exchange, and no per-endpoint scope to configure.
| Header | When | Value |
|---|---|---|
x-api-keyRequired | Every request | Your API key. Header names are case-insensitive, so X-API-Key is the same header. |
AuthorizationAlternate | Instead of the above | Bearer <key> — for clients that only expose bearer auth. Resolves to the same account and the same billing. |
A 401 means the key is missing, invalid or expired. A 403 means the key is valid but not permitted here — blocked by a key restriction or an IP allow-list. Running out of credits is a 429.
Response — GET /v1/filmography
Every APIVerve endpoint returns the same three top-level keys, so one response handler covers your whole integration: status, error and data. Only data changes shape.
{
"status": "ok",
"error": null,
"data": {
"name": "Christopher Nolan",
"id": "Q25191",
"role": "any",
"count": 10,
"filmsTotal": 21,
"roles": {
"director": 17,
"writer": 15,
"producer": 13,
"actor": 3,
"cinematographer": 3,
"editor": 1
},
"films": [
{
"title": "The Odyssey",
"year": 2026,
"roles": [
"director",
"writer",
"producer"
],
"id": "Q131547207"
},
{
"title": "Oppenheimer",
"year": 2023,
"roles": [
"director",
"writer",
"producer"
],
"id": "Q108839994"
},
{
"title": "Tenet",
"year": 2020,
"roles": [
"director",
"writer",
"producer"
],
"id": "Q63985561"
},
{
"title": "Dunkirk",
"year": 2017,
"roles": [
"director",
"writer",
"producer"
],
"id": "Q21935651"
},
{
"title": "Behind the Scenes",
"year": 2017,
"roles": [
"actor"
],
"id": "Q108257926"
},
{
"title": "Quay",
"year": 2015,
"roles": [
"director"
],
"id": "Q21869743"
},
{
"title": "Interstellar",
"year": 2014,
"roles": [
"director",
"writer",
"producer"
],
"id": "Q13417189"
},
{
"title": "Transcendence",
"year": 2014,
"roles": [
"producer"
],
"id": "Q10384115"
},
{
"title": "Man of Steel",
"year": 2013,
"roles": [
"writer",
"producer"
],
"id": "Q622769"
},
{
"title": "The Dark Knight Rises",
"year": 2012,
"roles": [
"director",
"writer",
"producer"
],
"id": "Q189330"
}
],
"otherMatches": [],
"dataAsOf": "2026-11-22"
}
}
Response fields
Paths are relative to data. Premium fields are absent rather than zeroed on plans that do not include them, so check for presence instead of comparing to 0.
| Field | Type | Example | Description |
|---|---|---|---|
name | string | "Christopher Nolan" | Person name |
id | string | "Q25191" | Wikidata id of the person |
role | string | "any" | Role filter applied |
count | number | 10 | Number of films returned |
filmsTotal | number | 21 | Number of films matching the role filter |
rolesPremium | object | {...} | Films per role across the whole filmography, e.g. director: 12 |
directorPremium | number | 17 | |
writerPremium | number | 15 | |
producerPremium | number | 13 | |
actorPremium | number | 3 | |
cinematographerPremium | number | 3 | |
editorPremium | number | 1 | |
films | array[10] | Films, newest first | |
title | string | "The Odyssey" | Film title |
year | number | 2026 | Year of first release |
rolesPremium | array | [director, ...] | The person's roles: director, actor, writer, producer, composer, cinematographer or editor |
id | string | "Q131547207" | Wikidata id of the film; pass it to Movie Lookup as id |
otherMatches | array | [] | Other people with the same name, best-known first |
dataAsOf | string | "2026-11-22" | Date the data was last refreshed (YYYY-MM-DD) |
Response headers
Every response carries your balance, so your own code always knows where it stands without polling anything. All four are exposed to browsers through CORS.
| Header | What it carries |
|---|---|
x-api-remaining-credits | Credits left in the current cycle |
x-api-credits-used | Credits spent in the current cycle |
x-api-max-credits | The allowance for the cycle |
x-api-version | Version of the endpoint that answered |
Errors
Read the HTTP status first, then error for the specific reason. The body names the parameter that has to change.
| Status | Meaning | What to do |
|---|---|---|
400 | Input was rejected | Read error; it names the parameter that has to change. |
401 | Key missing or invalid | Check the header name and the key value. |
403 | Key valid, but not permitted here | A key restriction or an IP allow-list — never a bad key. |
429 | Rate limited, or out of credits | Read error to tell them apart, then back off or top up. |
What a call costs — 1 credits per call
Credits are shared across every APIVerve API — one balance, one key, one bill. Failed requests never count against it, so a rejected input costs nothing.
| Plan | Per month | Credits | Filmography calls | Per 1,000 calls |
|---|---|---|---|---|
| Free | Free | 200 | 200 | Free |
| Starter | $29.99 | 200,000 | 200,000 | $0.15 |
| Pro | $99.99 | 1,000,000 | 1,000,000 | $0.10 |
| Mega | $299.99 | 4,000,000 | 4,000,000 | $0.07 |
Calls are what the credits buy at this API's rate — spend them here, on any of the other APIs, or across both. Nothing is reserved per endpoint.
Call it from cURL — GET /v1/filmography
No SDK to install — this is a plain HTTPS call to /v1/filmography with your key in the x-api-key header. Swap in a real key and it runs as-is.
curl "https://api.apiverve.com/v1/filmography" \
-H "x-api-key: YOUR_API_KEY"Resources
Call it from Node.js — GET /v1/filmography
No SDK to install — this is a plain HTTPS call to /v1/filmography with your key in the x-api-key header. Swap in a real key and it runs as-is.
const res = await fetch("https://api.apiverve.com/v1/filmography", {
headers: { "x-api-key": "YOUR_API_KEY" },
});
const { data } = await res.json();
console.log(data);Resources
Call it from Python — GET /v1/filmography
No SDK to install — this is a plain HTTPS call to /v1/filmography with your key in the x-api-key header. Swap in a real key and it runs as-is.
import requests
res = requests.get(
"https://api.apiverve.com/v1/filmography",
headers={"x-api-key": "YOUR_API_KEY"},
)
print(res.json()["data"])Resources
Call it from C# / .NET — GET /v1/filmography
No SDK to install — this is a plain HTTPS call to /v1/filmography with your key in the x-api-key header. Swap in a real key and it runs as-is.
using var client = new HttpClient();
client.DefaultRequestHeaders.Add("x-api-key", "YOUR_API_KEY");
var json = await client.GetStringAsync("https://api.apiverve.com/v1/filmography");
Console.WriteLine(json);Resources
Call it from Go — GET /v1/filmography
No SDK to install — this is a plain HTTPS call to /v1/filmography with your key in the x-api-key header. Swap in a real key and it runs as-is.
req, _ := http.NewRequest("GET", "https://api.apiverve.com/v1/filmography", nil)
req.Header.Set("x-api-key", "YOUR_API_KEY")
res, _ := http.DefaultClient.Do(req)
defer res.Body.Close()
body, _ := io.ReadAll(res.Body)
fmt.Println(string(body))Resources
Call it from PHP — GET /v1/filmography
No SDK to install — this is a plain HTTPS call to /v1/filmography with your key in the x-api-key header. Swap in a real key and it runs as-is.
$ch = curl_init("https://api.apiverve.com/v1/filmography");
curl_setopt($ch, CURLOPT_RETURNTRANSFER, true);
curl_setopt($ch, CURLOPT_HTTPHEADER, ["x-api-key: YOUR_API_KEY"]);
$response = curl_exec($ch);
echo $response;Resources
Call it from Ruby — GET /v1/filmography
No SDK to install — this is a plain HTTPS call to /v1/filmography with your key in the x-api-key header. Swap in a real key and it runs as-is.
require "net/http"
uri = URI("https://api.apiverve.com/v1/filmography")
req = Net::HTTP::Get.new(uri)
req["x-api-key"] = "YOUR_API_KEY"
res = Net::HTTP.start(uri.hostname, uri.port, use_ssl: true) { |h| h.request(req) }
puts res.bodyResources
Zero-code embed — one snippet, no backend
Drop an interactive Filmography form onto any page. The widget calls the API for you, so no key ever appears in your markup and there is nothing to deploy.
Changelog — Filmography API
Every change to this endpoint, newest first. Breaking changes ship as a new version and the previous one keeps serving — response fields are added, never removed or retyped in place, so an integration written against v1 keeps working.
Entries are picked up from dated catalog snapshots, so the first one appears after the next snapshot that moves something. A period where nothing changed produces no entry — silence is a valid changelog for the Filmography API.
Entertainment
- Advice Generator
- Bucket List
- Charades Generator
- Chess Move Validator
- Chuck Norris Jokes
- Compliment Generator
- D&D Generator
- Dad Jokes
- Filmography
- Fortune Teller
- Historical Events
- Love Calculator
- Magic 8-Ball
- Movie Lookup
- Music Note Generator
- Never Have I Ever
- Pictionary Generator
- Random Facts
- Random Joke
- Random Pun
- Random Quote
- Scrabble Word Scorer
- Sudoku Generator
- Trivia Generator
- Truth or Dare
- Wordle Helper