> For the complete documentation index, see [llms.txt](https://za.docs.rechtlogisch.de/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://za.docs.rechtlogisch.de/beta/filings/message/universal.md).

# Universal

## Endpoint

`/v2/message/universal/{type}/{subtype}`

## Types

* [`appeal`](/beta/filings/message/appeal.md)
* [`deadline`](/beta/filings/message/deadline.md)
* [`other`](/beta/filings/message/other.md)
* [`subsequent`](/beta/filings/message/subsequent.md)

## Subtypes

Currently available only for type [`appeal`](/beta/filings/message/appeal.md) .

* [`new`](/beta/filings/message/appeal/new.md)
* [`addendum`](/beta/filings/message/appeal/addendum.md)
* [`withdrawal`](/beta/filings/message/appeal/withdrawal.md)

## Advantages

The universal message endpoint introduces an unified request structure, while performing pre-validation and generating a valid ELSTER XML-structure.

The ELSTER dataset is not consistent within context naming, field naming and element order. The universtal message endpoint uses consistent naming for alike fields, and takes care about the element order.

Every request must contain:

* at least one contact in `contacts[]` (with provided type `personA`)
* `elsterTaxNumber` or `elsterFileNumber` (or `bufaTaxOffice` only other and subsequent)

Other fields are message type dependant.

## Mapping

Correlation between universal key name and ELSTER field.

{% file src="/files/FHo15ZzIBqAKdyHWgcCI" %}
Last changed: 2025-03-14
{% endfile %}
