agilio | 2021-06-22 18:35:30 UTC | #1
Getting this error from a data action but the header when viewed in Postman doesn't show that. EST call for action execute failed. Message:We were unable to process the response from the remote endpoint because it had a 'content-type' header of 'text/html' instead of the required value of 'application/json'. [6729e479-6f05-4ce7-ba02-74d520397e8b
Rest API works in POSTMan the header information especially the Content-Type looks correct. Thoughts?
HTTP/1.1 200 OK
Content-Type: application/json
Server: Microsoft-IIS/8.5
X-Frame-Options: SAMEORIGIN
X-XSS-Protection: 1
X-Content-Type-Options: nosniff
Strict-Transport-Security: max-age=63072000; includeSubDomains; preload
Content-Security-Policy: default-src 'self'
Date: Tue, 22 Jun 2021 18:24:48 GMT
Content-Length: 1175
Jason_Mathison | 2021-06-22 19:51:09 UTC | #2
Hi agilio!
Two things come to mind. First, you can try the standard "Unexpected failure" fix: https://help.mypurecloud.com/articles/custom-action-fails-for-unexpected-reason/
The other thing that comes to mind is to take a look at the postman console and make sure that there wasn't a redirect that is confusing things. By default postman will silently follow 3xx redirect messages.
Any additional troubleshooting is going to have to go through customer care / support.
--Jason
agilio | 2021-06-22 20:18:38 UTC | #3
Thanks the transfer encoding was it. Any chance the error that comes back could be tailored to provide that as the reason versus the content-type error?
Jason_Mathison | 2021-06-22 20:30:04 UTC | #4
Try setting a "Transfer-Encoding" header to "chunked" in postman and see what you get back.
agilio | 2021-06-22 20:56:11 UTC | #5
LOL nothing says helpful when the error returned is Just "ERROR". I get the challenge
Thanks for the help.
system | 2021-07-23 20:56:12 UTC | #6
This topic was automatically closed 31 days after the last reply. New replies are no longer allowed.
This post was migrated from the old Developer Forum.
ref: 11282