เอกสารอ้างอิง API มีเฉพาะภาษาอังกฤษ
People{personRef}filmography
GET/v1/ people/ {personRef}/ filmography
Everything a person is credited on, with the character or job, paged and sortable by year or title. Spends no verification.
พารามิเตอร์
- personRefstring · ในพาธจำเป็น
A person's
pn_public id or the catalog UUID.เพิ่มเติม
The person: a
pn_public id or the catalog UUID. - languagestringไม่บังคับ
Response language, a supported BCP-47 tag. Default
en.เพิ่มเติม
A supported BCP-47 tag. Defaults to
en. An UNSUPPORTED tag is a 400 naming the accepted set, never a silent fallback - the catalogue stores match the 17 tags as exact strings, so degrading would answer an empty 200 that an integrator would ship before noticing. - departmentstringไม่บังคับ
Only credits in this department, e.g.
Acting. Omit for all.เพิ่มเติม
Only credits in this department, matched as the response spells it (for example
Acting,Directing). Omit for every department. - sortyear | title | -year | -titleไม่บังคับค่าเริ่มต้น: year
year(default),title, or either with a leading-to reverse.เพิ่มเติม
year(oldest first, the default) ortitle(A-Z); a leading-reverses either. There is no rating sort. Case-insensitive; shown here in lowercase. - limitintegerไม่บังคับค่าเริ่มต้น: 20
Credits per page, 1-50. Default 20.
เพิ่มเติม
Out of range is a 400, never a silent clamp - silent clamping hides client bugs until they surface as a support ticket.
- cursorstringไม่บังคับ
The previous page's
next_cursor. Bound to the samedepartmentandsort.เพิ่มเติม
Opaque and FILTER-BOUND. Replaying a cursor after any filter changes is a 400
CURSOR_INVALID, never a silently wrong page.
ฟิลด์ของการตอบกลับ
- itemsFilmographyEntry[]
- next_cursorstringเป็น null ได้
- totalinteger · int64เป็น null ได้
How many items the query matches in total, when that is known. Null when it is not known; it is never an estimate.
เฮดเดอร์ของการตอบกลับ
- X-Request-ID
The id of this request, on every response - success or error. Quote it to support: it is how we find your request in our logs. An
X-Request-IDyou send is honoured and echoed back, so you can use your own; otherwise we generate one./v1error bodies carry no trace id of their own. - X-Quota-Reset
RFC 3339 instant at which the billing period rolls. Present on every response to a request whose key was metered - every 2xx, every error a handler returned, and the quota 429. Absent on a refusal that happens before metering: a missing or unknown key (401), a restricted key or a plan that does not carry the endpoint (403), a public demo-key gate refusal, and the pre-authentication flood throttle.
- X-Calls-Remaining
Requests left in the period after this one, never below 0. Present whenever
X-Quota-Resetis (see there for when a response carries no quota headers). - X-Verifications-Remaining
How many verifications you can still make before a limit stops you. The daily limit and the monthly allowance are counted separately; this is whichever of the two runs out first. Sent whenever
X-Quota-Resetis. - X-Quota-Grace
truewhen THIS request fell inside the 10% grace band above a monthly ceiling. A grace request is served and is not billed; treattrueas "back off now", not as headroom. Alwaystrueorfalse, never absent when the other quota headers are present. - Retry-After429
Seconds to wait before retrying. On every 429 - the quota hard stop, the public demo key's limits, and the pre-authentication flood throttle (which carries this header alone, because no key has been read yet).
- X-Demo-Challenge-Modeเฉพาะคีย์เดโม
Sent only on responses to the public demo key. The value
interactiveasks the documentation page to show the visible verification widget - it is sent once a browser has made more than five runs in ten minutes or has received a 429. The page then repeats the header,X-Demo-Challenge-Mode: interactive, on its next request, with the widget's token inX-Demo-Challenge. Requests made with your own key never receive it.
ข้อผิดพลาด
รายละเอียด
One row per TITLE, not per credit, with every job that person did on that title.
sort supports year and title only. rating is deliberately absent rather than published and faked: a filmography entry carries no rating, so sorting by one would mean either one extra read per entry or a new field on the person projection. Publishing a sort we cannot honour would let an integrator build a "top rated" view on an ordering that silently was not one. A leading minus reverses.