Universal
Endpoint
/v2/message/universal/{type}/{subtype}
Types
Subtypes
Currently available only for type appeal
.
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:
elsterTaxNumber
(orelsterFileNumber
)at least one contact in
contacts[]
(with provided typepersonA
)
Other fields are message type dependant.
Mapping
Correlation between universal key name and ELSTER field.
Work in progress. Will get extended without further announcement.
Last updated
Was this helpful?