Skip to main content
The API serves 119 national and regional registers, about 207 million records. GET /v1/jurisdictions is the authoritative, machine-readable list: it reports every register’s state, size, the span of filing years it holds, and when Pinakel last checked and changed it.

​
What each register reports

Counts come from precomputed aggregates, not from a live count, so they can trail the newest records slightly.

​
States

A reload republishes the whole register in the changes feed when it finishes. See How records change.

​
Freshness is two delays

How current a record is depends on two delays, and the API can only report the second:
  1. The office’s delay: between an event (a filing, a decision, a renewal) and the office publishing it. Some offices publish within a day; others publish weekly gazettes or monthly bulk files.
  2. Pinakel’s delay: between the office publishing and the change reaching the API. last_checked_at, last_changed_at and feed_published_through measure this part.
For a deadline that matters, confirm the office’s record before acting.

​
Checking coverage from code

GET /v1/jurisdictions returns about 120 entries in one response and is cached for 60 seconds. Call it at the start of a sync run, and:
  • skip registers that are reloading, and retry them later;
  • warn when a register you depend on is stale, or when last_checked_at is much older than its update_frequency;
  • build your jurisdiction filters from the codes it returns rather than from a hard-coded list.

​
Registers

The register table is generated from GET /v1/jurisdictions when this site is published. Until then, call GET /v1/jurisdictions for the current list.
Measured coverage and freshness, with sample sizes and method, are published as dated reports in Research.