Cases Read

Go to Product

Supports listing, retrieving, creating, updating, and deleting cases.

Creating cases:

POST /api/cases/?extract_refs=true with JSON body containing:

  • court_name (required): Court name for automatic resolution
  • file_number (required): Court file number
  • date (required): Publication date (YYYY-MM-DD)
  • content (required): Full case content in HTML
  • type (optional): Decision type (e.g., 'Urteil', 'Beschluss')
  • ecli (optional): European Case Law Identifier
  • abstract (optional): Case summary in HTML
  • title (optional): Case title
  • source (optional): Object with name (required) and homepage (optional). Looked up by name; created if not found. Default source used when omitted. Query parameters:
  • extract_refs (optional): Extract references from content (default: true)

The court is automatically resolved from the court_name. Returns 409 Conflict if a case with the same court and file_number exists.

Options

Id
Ein eindeutiger Ganzzahl-Wert, der case identifiziert.
Result Format

Specify how the response should be mapped to the table output. The following formats are available:

Structured Table: Returns a parsed table with data split into rows and columns.

  • Id:
  • Slug:
  • Court:
  • File Number: File number as defined by court
  • Date: Publication date as in source
  • Created Date: Entry is created at this date time
  • Updated Date: Date time of last change
  • Type: Type of decision (Urteil, Beschluss, ...)
  • Ecli: European Case Law Identifier
  • Content: Case full-text formatted in Legal HTML
  • Source Url: Identifier of source object (URL for web pages, file names or IDs for corpora)
  • Review Status: Review status for case visibility

Raw Response: Returns the raw response in a single row with the following columns:

  • body: Response body
  • status: HTTP status code

Input Ports

Icon
Configuration data.

Output Ports

Icon
Result of the request depending on the selected Result Format.
Icon
Configuration data (this is the same as the input port; it is provided as passthrough for sequentially chaining nodes to declutter your workflow connections).

Popular Predecessors

  • No recommendations found

Popular Successors

  • No recommendations found

Views

This node has no views

Workflows

  • No workflows found

Links

Developers

You want to see the source code for this node? Click the following button and we’ll use our super-powers to find it for you.