Integration patterns

Three things to build on the Data API, and the endpoints each one combines. Parameters live in the reference.

Legislation and regulatory monitoring

Build it when your product tracks what changed: new case law, regulator guidance and legislative changes in chosen fields of law and jurisdictions.

• keyword_search on a schedule: one saved query per topic, a rolling from_date and until_date, and jurisdictions, documentTypes and fieldsOfLaw as scope. Page with page and num_results, up to 100 per page.
• jurisdictions_portals, documenttypes and trees give users the valid values to configure what they track.
• retrieve_document pulls the full text on demand.

One rule. The API returns what matches inside the window. Your integration remembers the identifiers it has seen between runs.

Compliance and regulatory research

Build it when a compliance decision starts from a business question in plain language and must rest on the text of regulations, enforcement actions and supervisory guidance.

• hybrid_search scoped to the jurisdictions and fields of law that matter.
• hybrid_search_reranked where precision matters more than latency.
• retrieve_document for the full text and summary.

Cross-border legal research

Build it when the same question must be answered per country and compared.

• One hybrid_search per jurisdiction; group the results.
• sources lists the courts and bodies per jurisdiction, so you compare at the same court level.

One rule. National jurisdictions are queried in the national language: Dutch for the Netherlands, German for Germany, French for France. EU sources work in English.