Yes something must have changed with the Journey API Endpoint. Location and Timetable API Endpoints still work but the Journey API Endpoint now always returns a 405 Method not allowed error. There seems to be a new Domain for the API but sadly changing to that one does not fix the problem.
Update: Found the cause. The Journey API Endpoint Version was updated from v8 to v9.
@poetaster Haven’t tested it yet but should be It’s enough to change v8 to v9 in the mime type parameter in the sendHttpRequestMovas call (last line of ParserMovasBahnDe::internalSearchJourney).