I’ve set up a Data Action in Architect to call the NICE Cognigy API for profile tokens, but the response keeps failing validation. The HTTP call itself returns a 200 OK, so the connection is fine, but the JSON parsing step throws a generic error. I’m using the standard GET request to /api/v1/profiles/get with the Authorization header set to Bearer {{oauth_token}}. The response body looks valid in the logs, yet the system can’t map it to the output variables. Here is the payload structure I’m expecting: {"profileId": "12345", "status": "active"}. I’ve tried adding a JSON parse step before the mapping, but it still fails silently. It feels like the response might have some trailing whitespace or a hidden character that breaks the parser, but I can’t see it in the debug view. The error message just says “Invalid JSON structure” without pointing to a specific line or character index.
I’ve checked the Cognigy docs and the endpoint seems standard. I’m using the exact same token that works in Postman, so auth isn’t the issue. I’ve also verified that the variable {{oauth_token}} is populated correctly before the call. The Data Action configuration uses the default JSON parser. Is there a known issue with how Genesys Cloud handles certain JSON formats from external APIs? I’ve tried wrapping the response in a try-catch block using a script step, but I don’t have much experience with the scripting language used in Data Actions. Any ideas on how to debug the raw response string? I need to map profileId to a local variable for routing logic. The timeout is set to 5 seconds, which should be plenty. I’m running out of places to check.