How Can I Test Submission Statuses in the Submission API?

Tipp

Last updated on 2025-08-06.

Some submission statuses may occur in the live environment but cannot be deliberately triggered within our infrastructure. The following statuses are affected:

XML_GENERATION_FAILED: This status should not normally occur, as only data that passes all validations and business rules proceeds to XML generation.

TRANSMISSION_FAILED: This cannot be triggered manually, as it results from communication errors with ELSTER.

ERROR: Refers to rare internal system errors that cannot be deliberately tested.

INTERNAL_VALIDATION_FAILED: Occurs when users submit invalid data.

Testing Error States

To simulate these or other errors, we recommend implementing a mock proxy on your side that returns predefined responses. This gives you full control over your test scenarios.

Test Scenario for EXTERNAL_VALIDATION_FAILED

This status occurs when a submission is rejected by ELSTER. You can deliberately trigger it by setting the clientType to 4 (taximeter) or 5 (odometer) in the UpsertClientAdditionalData endpoint and leaving the remarks field empty. In this case, ELSTER will reject the submission.

Simulating Delays

We do not support simulating delays (e.g., VALIDATION_TRIGGERED, TRANSMISSION_IN_PROGRESS) within our environment. Mocking the behavior on your side is the most effective solution.