GET /search/<type> returns HTTP 500 whenever the comma-separated type list contains 2+ types where at least one of person or list is mixed with anything else. Single-type queries and movie,show work fine.
Repro:
curl "https://api.trakt.tv/search/movie,show,person,list?query=matrix" \
-H "Content-Type: application/json" \
-H "trakt-api-version: 2" \
-H "trakt-api-key: <redacted>"
Results (query=matrix, tested 2026-09-08):
/search/<types> |
Result |
movie, show, person, list (single) |
200 |
movie,show |
200 |
movie,person, show,person, person,list, movie,list, show,list, movie,show,list, movie,show,person, movie,show,person,list |
500 |
Same result via curl with only a trakt-api-key header (no OAuth token), so it's not an auth issue — reproduced consistently across 3+ runs, first observed 2026-09-06, still failing today (2026-09-08).
Response headers on the 500:
x-error-message: Internal server error. Please open a support issue and include your full API request and response, including all headers.
x-request-id: 6c9dcabe-1ff2-4b2d-b01a-924512b827f2
cf-ray: a37fa37738a0a79d-DEL
date: Tue, 08 Sep 2026 17:23:04 GMT
Body is empty.
Impact: This is the query our app's "All" search tab sends (movie,show,person,list), so search appears completely broken for every user hitting that default tab.
GET /search/<type>returns HTTP 500 whenever the comma-separated type list contains 2+ types where at least one ofpersonorlistis mixed with anything else. Single-type queries andmovie,showwork fine.Repro:
Results (query=matrix, tested 2026-09-08):
/search/<types>movie,show,person,list(single)movie,showmovie,person,show,person,person,list,movie,list,show,list,movie,show,list,movie,show,person,movie,show,person,listSame result via
curlwith only atrakt-api-keyheader (no OAuth token), so it's not an auth issue — reproduced consistently across 3+ runs, first observed 2026-09-06, still failing today (2026-09-08).Response headers on the 500:
Body is empty.
Impact: This is the query our app's "All" search tab sends (
movie,show,person,list), so search appears completely broken for every user hitting that default tab.