Report Missing Route

Report an Aktenzeichen that is real but not in lawdb.

Bork's boundary, verbatim in the ticket: consumers REPORT, lawdb decides everything else. The whole contract is: authenticated, idempotent per (aktenzeichen, source), answer accepted or duplicate. What happens to a report afterwards (citation-graph attestation, the resolver, ingest) is service-internal and deliberately unpromised.

401 for the unkeyed/unknown-key/unresolvable-key trio alike — apikeys. identify's own rule, so nlk_ prefixes cannot be enumerated here.

post/v1/report-missing

Request

  • Base URL: https://recht.nulegal.eu (the document declares no server; this is the origin it was published from)
  • URL: https://recht.nulegal.eu/v1/report-missing
  • Auth: none declared

Request body

aktenzeichenstring required
courtstring nullable

The deciding court, if known. Deprecated spelling: gericht, still accepted.

decidedstring date nullable

The decision date, if known. Deprecated spelling: datum, still accepted.

evidence_urlsstring[]

Up to 10 http(s) URLs where the decision is attested. Deprecated spelling: beleg_urls, still accepted.

sourcestring required

Who is reporting, e.g. open-assistant; one report per (aktenzeichen, source). Deprecated spelling: quelle, still accepted.

contextstring nullable

Where the Aktenzeichen was encountered. Deprecated spelling: kontext, still accepted.

Response

Successful Response

unknown required

Changes

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