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

Changes

What changed in the catalogue since a moment you name - records added, updated, merged or removed - for keeping a mirror in step. Spends no verification.

Tham số

• sincestring · date-timebắt buộc

  Start of the window, RFC 3339, within the last 30 days. Required.

  Thêm⌄

  RFC 3339. Must be within the retention window; older is a 400, never an empty success.

• untilstring · date-timekhông bắt buộc

  End of the window, RFC 3339. Default: as fresh as your plan allows.

  Thêm⌄

  End of the window, an RFC 3339 timestamp after since. Omit it to read up to the freshest moment your plan allows; an explicit value fresher than that is a 403 plan-required.

• languagestringkhông bắt buộc

  Accepted for consistency; the feed carries no translated text.

  Thêm⌄

  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.

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

  Change rows per page, 1-500. Default 100.

  Thêm⌄

  Counts change-log ROWS, not emitted entries. See has_more on the response.

• cursorstringkhông bắt buộc

  The previous page's next_cursor.

  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

• itemsChangeEntry[]
  Hiện 6 trường
• sincestring · date-time
• untilstring · date-time
• next_sincestring · date-time

  The 'since' value to send next time. Pass it TOGETHER with next_cursor or the feed livelocks: on its own it is an inclusive bound that re-selects everything sharing that instant.

• next_cursorstringcó thể null
• has_moreboolean

  LOOP ON THIS, never on the length of items. The limit counts change-log ROWS while the response carries COLLAPSED entries - several rows become one entry per record - so a page legitimately returns fewer entries than the limit while more remain.

• retention_daysinteger · int64

  How far back the feed goes. A request older than this is a 400, never an empty success.

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-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.

• 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.

• 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

• 400since is missing, not an RFC 3339 timestamp, or older than the 30-day retention window

  validation-failed

• 400until is not an RFC 3339 timestamp, or is not after since

  validation-failed

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

  validation-failed

• 400language is not one of the 17 supported tags

  validation-failed

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

  cursor-invalid

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

  cursor-invalid

• 400with the public demo key, limit above 10

  validation-failed

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

  unauthenticated

• 403an explicit until is fresher than your plan's change-feed delay allows

  plan-required

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

  forbidden

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

  plan-required

• 403a browser call with the public demo key sent no valid bot-check token

  challenge-required

• 405the HTTP method is not GET

  validation-failed

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

  quota-exhausted

• 429too many requests from your address before any key is read; with the public demo key, its per-address, per-network or global limit, a temporary block, or too many demo requests in flight at once

  rate-limited

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

  upstream-unavailable