Legacy Dev Forum Posts

 View Only

Sign Up

  • 1.  Failed Web Services 403

    Posted 06-05-2025 18:45

    kike | 2022-05-06 12:04:39 UTC | #1

    Hi,

    Could you guide me as to why this error? Thank you very much

    { "message": "You are not authorized to perform the requested action.", "code": "not.authorized", "status": 403, "messageParams": {}, "contextId": "5855ddc9-9b9f-4f65-99df-03fc45a34e9f", "details": [ { "errorCode": "ACTION.REMOTEENDPOINT" } ], "errors": [ { "message": "REST call for action execute failed. Message: Request to backend service failed. Response from web service: {\"message\":\"'eyJraWQiOiJy****pLN4tD3p0TA' not a valid key=value pair (missing equal-sign) in Authorization header: 'Bearer eyJraWQiOiJy****N4tD3p0TA'.\"} [5855ddc9-9b9f-4f65-99df-03fc45a34e9f]", "code": "NOTAUTHORIZED", "status": 403, "messageParams": {}, "details": [], "errors": [] } ] }


    Jason_Mathison | 2022-05-06 12:03:53 UTC | #2

    This part of the error response seems key, but I don't know what it is supposed to mean.

    kike, post:1, topic:14617
    not a valid key=value pair (missing equal-sign) in Authorization header: 'Bearer

    This also looks like authentication information so I am redacting parts of your post, but you should probably regenerate this credential ASAP.

    --Jason


    kike | 2022-05-06 12:06:52 UTC | #3

    Hi Jason, I attach the data action, this is how I have configured it, it seems strange to me that it is from the configured authorization since it works well. It may be that they have to give us permissions in the /api/sms path?

    Thank you testgrua-20220506140555.custom.json|attachment (1.6 KB)


    Jason_Mathison | 2022-05-06 15:12:28 UTC | #4

    For situations like this I would always suggest going back to something like postman to verify you can get the endpoint working, and then go from there.

    If this is working in postman then you should check the troubleshooting guide. web services tab -> custom action fails for unexpected reason

    https://help.mypurecloud.com/articles/troubleshoot-the-data-actions-integrations/

    --Jason


    kike | 2022-05-09 09:16:57 UTC | #5

    Hello, Inspecting the api request, it gives status error: CORS error and type: fetch has been blocked by CORS policy: Request header field countryid is not allowed by Access-Control-Allow-Headers in preflight response.

    This is a client webservice problem, right? Thank you


    kike | 2022-05-09 09:18:08 UTC | #6

    Hello, I already solved it, it was a failure of the client's web service, on the other hand now I find that the "&" character in genesys gives me an error, is there another way to analyze this data?


    Jason_Mathison | 2022-05-09 14:09:40 UTC | #7

    Hi kike,

    Can you give me an example of a configuration where an & is causing you a problem?

    --Jason


    kike | 2022-05-09 14:31:55 UTC | #8

    Hi Jason, I fixed it. Thank you very much


    system | 2022-06-09 14:32:13 UTC | #9

    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: 14617