DEVELOPER QUICK START

Reach verifiable Austrian legislative data in minutes.

Inspect the open data first. Then retrieve the optional integration pack without an account by using an x402-v2-compatible client.

1. Inspect live data and coverage

The open index contains only published, source-linked events. Empty periods are not filled with sample records.

GEThttps://lawwatch.rus.family/api/v1/events/index.json

Use /api/v1/status for service status and freshness. The complete HTTP contract is available in the OpenAPI document.

2. Preserve evidence for each event

Every published record carries a stable LawWatch URL and canonical RIS or ELI links. Treat LawWatch as a technical information layer; the official publication remains authoritative for legally consequential decisions.

GEThttps://lawwatch.rus.family/api/v1/events/at-bgbl-i-2024-156.json

Inspect the human-readable verified record →

3. Optional: retrieve the integration pack through x402

After successful settlement, the protected endpoint returns the current live index, official-source registry, coverage manifest, JSON Schema, field glossary and quality rules. Price: 0.05 USDC per successfully settled request on Base mainnet. No login or API key is required.

GEThttps://lawwatch.rus.family/api/v1/paid/integration-pack
  1. An initial request receives the expected HTTP 402 Payment Required response and a PAYMENT-REQUIRED header.
  2. An x402-v2-compatible payment client reads the requirement, creates payment authorization and repeats the request with PAYMENT-SIGNATURE.
  3. Only successful settlement returns HTTP 200 with the integration pack and a PAYMENT-RESPONSE header.

Discovery metadata is available at /.well-known/x402.json. Use the official x402 documentation for client and wallet setup. Never place private keys in HTTP headers or application source code.

DATA CONTRACT

What the API promises — and what it does not.

The collection currently covers promulgated Austrian federal laws in BGBl. I; historical coverage is incomplete. Each record exposes its sources, verification state and fields that are intentionally not asserted. A successful HTTP response proves technical delivery, not legal advice or a substitute for RIS.

Inspect OpenAPI