In POST call header key naming requirements change between local and test/acceptance

Instead of normal authentication you can set up a token system where the microflow manages access. In this method I generate a key for an API user and then that user passes the key into the header. This worked locally like so:   But in the Test and Acceptance environment in the Mendix cloud this didn’t work. We found that it didn’t even pass the API_Key value to the microflow. When we compared it to a REST service that was working the only difference was the name for the API_Key parameter which was ‘Authorization’ instead of ‘API_Key’. Once we changed that it worked. Why is this? And why was it only an issue once I moved it to the cloud?
1 answers

This is fixed in 7.23.4 – see the release notes: