api

Api Changes

What changed in this country's corpus, oldest first.

The pull half of the webhooks: same events, same data payload, no endpoint to host. Poll it with since once, then follow next_cursor — that is the only gap-free way to resume, because a night's events all carry the same detection timestamp.

A change is what the daily sync found: a law added, its metadata or text updated, its status turned to repealed, or a new amendment recorded. It says what moved and when, with the sha to diff against — not which article was touched.

get/api/v1/{country}/changes

Request

  • Base URL: https://legalize.dev (the document declares no server; this is the origin it was published from)
  • URL: https://legalize.dev/api/v1/{country}/changes
  • Auth: API key in header Authorization

Path parameters

countrystring required

Query parameters

sincestring nullable

Only changes detected on or after this date (YYYY-MM-DD).

cursorinteger nullable

Resume after this change id. Use next_cursor from the previous page.

limitinteger

Response

Successful Response

countrystring required
countinteger required
next_cursorinteger nullable required
has_moreboolean required

Changes

No recorded changes to this operation across all 1 revision of this API.