Hi all,
We're currently integrating BMC Helix ITSM with Genesys Cloud using Web Services Data Actions.
The authentication endpoint (/api/jwt/login) returns a valid JWT token, however the response comes back as:
Content-Type: text/plain
The body is simply the raw JWT string.
When calling this from Genesys Cloud, the Data Action fails before mapping because the platform expects application/json responses.
We attempted to:
- Use Translation Map to capture the raw body (
"$")
- Wrap the response using a Success Template
- Adjust headers (Accept / Content-Type)
However, the call appears to be rejected at the HTTP validation layer before the mapping logic executes.
My questions:
- Does Genesys Cloud strictly enforce
application/json before running the Translation Map?
- Has anyone successfully consumed a
text/plain JWT login endpoint using Web Services Data Actions?
- Is there any supported workaround without introducing middleware?
We're evaluating whether to:
- Request the API provider to return JSON instead
- Use Basic authentication (if allowed)
- Introduce a lightweight proxy
Appreciate any insights from those who've handled similar integrations.
Thanks!
#Integrations------------------------------
Phaneendra
Technical Solutions Consultant
------------------------------