Add GET /people browse/discover endpoint

Extends the browse/discover pattern already built for movies/series to the fourth major entity type. No genre/year/status equivalent for people -- known_for_department is the one categorical filter that actually means something for a cast/crew list, and sort_by is just popularity (default) or name. No invalid-filter case either: unlike genre/status, known_for_department is a plain string compared directly, nothing to parse or validate. build_person_summary refactored to share row-to-summary logic with the new list path, same pattern used for movies/series/companies. Co-Authored-By: Claude Sonnet 5 <[email protected]>
2026-09-05 10:32:16 -05:00
parent 74adcf77bc
commit 6aa9f0b840
6 changed files with 257 additions and 10 deletions
@@ -150,9 +150,17 @@ carries the same `cast`/`crew`/`creators` three-way split as series detail.

 | Method | Path |
 |---|---|
+| GET | `/api/v1/people` |
 | GET | `/api/v1/people/{aurora_id}` |
 | GET | `/api/v1/people/{aurora_id}/credits` (movie and series filmography; guest-star episode credits are aggregated to one row per series rather than one per episode, but carry both `episode_count` and the individual `episodes` breakdown, sorted by season/episode number) |

+`GET /api/v1/people` is the browse/discover equivalent for people. No
+genre/year/status here — `known_for_department` (exact match, e.g.
+`Acting`, `Directing`, `Writing`) is the one categorical filter that
+actually means something for a cast/crew list, and `sort_by` is just
+`popularity` (default) or `name`. Otherwise the same `page`/`page_size`
+pagination and response shape as `/movies` and `/series`.
+
 ## Collections / Companies

 | Method | Path |