APIリファレンスは英語のみで提供されています。
Changeschangelog
GET/v1/ changelog
Release notes for this API, newest first - what changed, when, and whether it can break an integration. Spends no verification.
パラメーター
- languagestring任意
Accepted for consistency; notes are written in English.
その他
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. - categoryadded | changed | deprecated | removed | fixed | security任意デフォルト: all categories
added,changed,deprecated,removed,fixedorsecurity.その他
Only entries of this kind. Omit for every category. Case-insensitive; shown here in lowercase. Anything else is a 400.
- breakingboolean任意
truereturns only changes that can break an integration.その他
Filter to entries that can break an integration, whatever their category.
- limitinteger任意デフォルト: 20
Entries 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 same filters.その他
Opaque and FILTER-BOUND. Replaying a cursor after any filter changes is a 400
CURSOR_INVALID, never a silently wrong page.
レスポンスフィールド
- itemsChangelogEntry[]
- next_cursorstringnull 許容
- totalinteger · int64null 許容
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.
エラー
詳細
What WE changed about the API, as data rather than prose, so it can be paged and filtered.
Not the catalogue change feed - /v1/changes is which titles moved.