Error handling in API processor

If an error occurs during the API call, 400 with a stack trace is returned. Is it really correct to show our internals in public interfaces? Shouldn’t we just return empty 400?

For example calling API expecting a guid with invalid value produces such response.

I don’t think it is correct. Although I am not sure if someone does not depend on it. But I would rather remove it. Or at least made it optional as development is easier when you see the error straight instead of looking in logs.

The issue is solved in 2024.9 by removing the stack trace from the server responses.