About

The register was a web page.

The European Commission publishes the Article 22(5) list of designated Trusted Flaggers as HTML. dsa-api turns it into something you can build on — refreshed every six hours, served as an API and an open dataset.

Why it exists

One register, many consumers

Under the Digital Services Act, platforms must give designated Trusted Flaggers priority when they report content. But the official list is a page meant for reading, not for querying. dsa-api keeps a structured, always-fresh copy so trust & safety teams, compliance tooling, researchers and journalists can all work from the same live data — without each re-scraping the same HTML.

How it works

Scrape, diff, publish

1 · Scrape every 6h

A scheduled job fetches the Commission's page and parses it into structured records.

2 · Diff & ingest

Each run is compared against the database. Created, updated, removed and restored events are recorded.

3 · Serve & export

The API reads from the database; a flat JSON/CSV export is pushed to the open-data repo.

EU register (HTML) ──▶ scraper (every 6h)
                          │  parse → diff → ingest
                          ▼
                    database  ◀── REST API ──▶ clients
                          │
                          ▼
                 export JSON/CSV ──▶ git push ──▶ open data

A watchdog raises an alert if the last successful scrape is more than 24 hours old, so staleness never goes unnoticed.

Coverage

21 member states, one place

Every entry is attributed to the national Digital Services Coordinator that designated it. Current breakdown of designated flaggers by country:

AT 8BE 3DE 4DK 2EE 3EL 4FI 3FR 8HU 1IE 1IT 10LT 6LU 1LV 2MT 1NL 4PT 2RO 4SE 2SI 3SK 2
Good to know

Questions

Is this official?

No. It's a community mirror for convenience. The authoritative source is the European Commission page. Verify there before any legal or compliance decision.

How fresh is it?

The scraper checks every six hours; the data and changelog update only when something actually changed. Responses carry an X-Data-Updated-At header.

Do I need a key?

No. Public, read-only, CORS-enabled, with fair-use rate limits. See the API reference.

Can I use it commercially?

Yes — data is CC BY 4.0, code is MIT. Please credit and link back. Details on the Data page.

Colophon

Who & what

Community mirror — not the authoritative source. We make no compliance guarantees. The Commission's page is the source of truth.

Start querying in one line.

Free, open, and always in sync with the EU register. No signup, no key, no catch.