❓ Not directly related to the current PR but I have to ask somewhere:
The endpoint documentation contains some requirements to the acceptable values, but some of them we don't check.
For example:
"applicationType": "FIRST_APPLICATION", // Must be FIRST_APPLICATION
But I can submit RENEWAL_APPLICATION, and it will be accepted.
And for some values we have checks, but we return a 500 error with no meaningful description.
For example, if I send "givenInformationIsCorrectAndComplete": false, // Must be true
So I wonder if we actually need some user-friendly error handling here? (as a separate task maybe)

❓ and one more general question:
when verein360 application is submitted, the emails to the organisation ("Bestätigung notwendig") and to the user ("Antrag erfolgreich eingereicht") are sent, but I feel like it's not actually needed, isn't it? At least when isAlreadyVerified: true

❓ and one more general question: when verein360 application is submitted, the emails to the organisation ("Bestätigung notwendig") and to the user ("Antrag erfolgreich eingereicht") are sent, but I feel like it's not actually needed, isn't it? At least when isAlreadyVerified: true

Yes i think we decided on not sending mails in this case. For organizations it makes no sense and for the users we would have to adjust the texts because they not really submitted the application

❓ and one more general question: when verein360 application is submitted, the emails to the organisation ("Bestätigung notwendig") and to the user ("Antrag erfolgreich eingereicht") are sent, but I feel like it's not actually needed, isn't it? At least when isAlreadyVerified: true

You are right, this was a bug. I fixed it.

❓ Not directly related to the current PR but I have to ask somewhere: The endpoint documentation contains some requirements to the acceptable values, but some of them we don't check. For example: "applicationType": "FIRST_APPLICATION", // Must be FIRST_APPLICATION But I can submit RENEWAL_APPLICATION, and it will be accepted. And for some values we have checks, but we return a 500 error with no meaningful description. For example, if I send "givenInformationIsCorrectAndComplete": false, // Must be true So I wonder if we actually need some user-friendly error handling here? (as a separate task maybe)

Ok good point. I would split this:

1. I created a new issue for general validation for this endpoint: Input validation for application endpoint #1816
2. Validation that is specific for verein360 pre-verified requests: Will add this to this PR.

pls update the branch, I will re-test all together :)

pls update the branch, I will re-test all together :)

done