Mendix should provide a native API Call History & Replay feature for both Published and Consumed REST services. Currently, developers have to build custom logging, extra microflows, or rely on external tools just to see what API calls were made, with which payload, and why they failed. This adds repetitive work and makes debugging production issues unnecessarily hard.
With a built-in solution, Mendix could automatically keep an API call history that includes basic information such as endpoint, method, timestamp, status code, duration, and correlation ID, with optional masked request/response data. The feature could be enabled per environment with configurable retention, and optionally allow replaying a request for debugging. This would remove a very common pain point, reduce custom boilerplate in almost every integration project, and strongly support Mendix’s low-code promise.
I usually set the lognodes REST Consume & REST Publish to TRACE to see all the info you are after (for short periods of time or debugging).