Tài liệu tham khảo API chỉ có bằng tiếng Anh.

People

Browse the people in the catalogue, most popular first or by name, filtered by the department they are known for. Spends no verification.

Tham số

• languageen | zh | zh-TW | es | pt | pt-PT | hi | ar | ru | ja | de | ko | fr | tr | it | vi | thkhông bắt buộcmặc định: en

  Response language, a supported BCP-47 tag. Default en.

  Thêm⌄

  One of the 17 supported tags - the enum is their canonical spelling - defaults to en. The server also accepts any letter case and _ for -. A region subtag on a supported language folds to it (en-US reads as en, pt_BR as pt), and zh-TW / pt-PT are matched as themselves. Only a region folds - a script subtag such as zh-Hant is a 400. Any other tag is a 400 whose message lists the 17 - never a silent fallback, because the catalogue matches its tags exactly and a degraded tag would answer an empty 200.

• departmentstringkhông bắt buộc

  Only people known for this department, e.g. Acting. Omit for all.

  Thêm⌄

  Only people known for this department, matched case-insensitively: Acting, Directing, Writing, Production, Camera, Editing, Art, Costume & Make-Up, Sound, Visual Effects, Lighting or Crew. Omit (or leave blank) for everyone; any other value is a 400 listing these.

• has_creditstruekhông bắt buộcmặc định: true

  Only people with a published credit. true, the default and only value.

  Thêm⌄

  The list holds only people credited on a published title, so the one accepted value is true, which is also the default. Any other value is a 400.

• sortpopular | namekhông bắt buộcmặc định: popular

  popular (default) or name.

  Thêm⌄

  popular (most popular first, the default) or name (A-Z). Case-insensitive; shown here in lowercase.

• limitintegerkhông bắt buộcmặc định: 20

  People per page, 1-50. Default 20.

  Thêm⌄

  Out of range is a 400, never a silent clamp - silent clamping hides client bugs until they surface as a support ticket.

• cursorstringkhông bắt buộc

  The previous page's next_cursor. Bound to the same department, sort and language.

  Thêm⌄

  Opaque and FILTER-BOUND. Replaying a cursor after any filter changes is a 400 CURSOR_INVALID, never a silently wrong page.

Các trường phản hồi

• itemsPersonListItem[]
  Hiện 6 trường
• next_cursorstringcó thể null
• totalinteger · int64có thể null

  Always null on this list: counting every listed person on each call would cost more than the page itself. Page until next_cursor is null.

Tiêu đề phản hồi

• 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-ID you send is honoured and echoed back, so you can use your own; otherwise we generate one. /v1 error bodies carry no trace id of their own.

• X-Ignored-Params

  The query parameters this request sent that the operation does not take, comma-separated and sorted (at most 20 names; a name that is not a plain token is percent-encoded). Such a parameter is accepted and has no effect, so this header is how a mistyped or unsupported filter shows up instead of silently widening the answer. Absent when every parameter sent was one the operation takes. Sent on every response an endpoint answered, an error included; a refusal of the key check before the endpoint carries none.

• 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-Reset is (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-Reset is. On a sources answer that spent a verification (verification_spent: true) it already counts that spend; an answer that spent none leaves it unchanged.

• X-Quota-Grace

  true when THIS request fell inside the 10% grace band above a monthly ceiling. A grace request is served and is not billed; treat true as "back off now", not as headroom. Always true or false, never absent when the other quota headers are present.

• RateLimit-Limit

  The size of the limit this response describes. On an admitted request it is your plan's monthly request allowance; on a 429 it is the limit that refused the call (for the bandwidth limit, in bytes; for the spending limit you set, the monthly verification allowance it binds past). Follows the three-field form of an earlier IETF draft for rate-limit headers; not a final standard. Sent beside X-Calls-Remaining and X-Quota-Reset, which keep their meaning.

• RateLimit-Remaining

  Requests left in the month after this one on an admitted request (the same figure as X-Calls-Remaining), and always 0 on a 429. Follows the three-field form of an earlier IETF draft for rate-limit headers; not a final standard.

• RateLimit-Reset

  Seconds until the limit this response describes resets: until the monthly request allowance rolls on an admitted request, and the same value as Retry-After on a 429. The request allowance rolls with the UTC calendar month, so on a paid plan whose billing period starts mid-month it can differ from X-Quota-Reset, which follows the billing period. Follows the three-field form of an earlier IETF draft for rate-limit headers; not a final standard.

• WWW-Authenticate429

  On every 401, and only on a 401. Bearer realm="api.wambesha.com" when no key was sent (or the Authorization header was not a Bearer token); Bearer realm="api.wambesha.com", error="invalid_token" when a key was sent and not accepted. The status and code are the same for both.

• 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-ModeChỉ với khóa demo

  Sent only on responses to the public demo key. The value interactive asks 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 in X-Demo-Challenge. Requests made with your own key never receive it.

Lỗi

• 400sort is not popular or name

  validation-failedmetadata.errorCodePUBLIC_API_SORT_UNSUPPORTED

• 400limit is not an integer or is outside 1-50

  validation-failedmetadata.errorCodePUBLIC_API_LIMIT_OUT_OF_RANGE

• 400language is not one of the 17 supported tags

  validation-failedmetadata.errorCodePUBLIC_API_LANGUAGE_UNSUPPORTED

• 400cursor is malformed, stale, or was issued for different filters or sort - start again from the first page

  cursor-invalidmetadata.errorCodeCURSOR_INVALID

• 400with the public demo key, a cursor past the second page or one the demo key was not given

  cursor-invalidmetadata.errorCodePUBLIC_API_DEMO_BOUNDS

• 400with the public demo key, limit above 10

  validation-failedmetadata.errorCodePUBLIC_API_DEMO_BOUNDS

• 400department is not one of the departments people are known for

  validation-failedmetadata.errorCodePUBLIC_API_DEPARTMENT_UNKNOWN

• 400has_credits is anything but true

  validation-failedmetadata.errorCodePUBLIC_API_HAS_CREDITS_UNSUPPORTED

• 401no key, or an Authorization header that is not a Bearer token

  unauthenticatedmetadata.errorCodePUBLIC_API_KEY_INVALID

• 401a key that is unknown, malformed, expired or revoked

  unauthenticatedmetadata.errorCodePUBLIC_API_KEY_INVALID

• 403the key's own scope, IP or referrer restriction excludes this request

  forbiddenmetadata.errorCodePUBLIC_API_KEY_RESTRICTED

• 403your key carries no plan, or the public demo key was used with a method other than GET or HEAD

  plan-requiredmetadata.errorCodePUBLIC_API_PLAN_REQUIRED

• 403a browser call with the public demo key sent no bot-check token, or the invisible check's token after being asked for the visible one

  challenge-requiredmetadata.errorCodePUBLIC_API_DEMO_CHALLENGE_REQUIRED

• 403a browser call with the public demo key sent a bot-check token the check refused, or the check could not be completed

  challenge-rejectedmetadata.errorCodePUBLIC_API_DEMO_CHALLENGE_REJECTED

• 405the HTTP method is not GET

  method-not-allowedmetadata.errorCodePUBLIC_API_METHOD_NOT_ALLOWED

• 429your plan's daily or monthly request ceiling is reached; the refused call is not charged

  quota-exhaustedmetadata.errorCodePUBLIC_API_QUOTA_EXHAUSTED

• 429too many requests from your address before any key is read; with the public demo key, more than 10 calls a minute or 100 a day from your address, 500 a day from your network or 20 a second from everyone, a temporary block (1 minute, then 10 minutes, then an hour; a day without one starts again), or too many demo requests in flight at once

  rate-limitedmetadata.errorCodePUBLIC_API_DEMO_RATE_LIMITED

• 503we could not meter or serve the request right now; retry with backoff

  upstream-unavailablemetadata.errorCodePUBLIC_API_UNAVAILABLE