Hi Team,
I’m Emmanuel Katto from Dubai, United Arab Emirates (UAE) facing an issue while trying to mask sensitive data in the response using the Apigee Management API. We’re using the following Management API endpoint, but I’ve noticed that the masking doesn’t seem to work for GET requests, even though it functions fine for POST requests.
Here’s the odd part: when I make a GET request after a POST request for the same API, the data gets masked as expected. This has me wondering—does the configuration require a POST request to be made first for the masking to take effect for subsequent GET requests?
Since all of my endpoints are GET requests and not POST, I’m looking for a way to bypass this dependency and have the sensitive data masked correctly on the GET requests.
Has anyone encountered this behavior before? Any insights or suggestions on how to resolve this?
Regards
Emmanuel Katto