Legacy Dev Forum Posts

 View Only

Sign Up

Integration - Data Action/ WebService API/ Consuming HTTP not HTTPS

  • 1.  Integration - Data Action/ WebService API/ Consuming HTTP not HTTPS

    Posted 06-05-2025 19:20

    alialjohani | 2018-09-09 11:11:47 UTC | #1

    Dears,

    The following error is shown to me when I test the API based on HTTP.

    However, this should be fine according to help.PureCloud: https://help.mypurecloud.com/articles/requirements-web-services-data-actions-integration/

    Please, let me know if this is possible or not? Am I doing something wrong?

    Best Regards, Ali


    Jason_Mathison | 2018-09-09 19:36:15 UTC | #2

    Hi Ali,

    The web page that you linked to includes this requirement: An HTTPS endpoint on port 443.

    --Jason


    alialjohani | 2018-09-10 06:38:56 UTC | #3

    Hello Jason,

    Thank you for the feedback. Do you mean this requirement is coming from the backend API? (Not from PureCloud)? If so, then I am wondering why it works with Postman and Rested?

    Best Regards, Ali


    Jason_Mathison | 2018-09-10 11:56:37 UTC | #4

    Hi Ali,

    The "Requirements for the web services data actions integration" is documenting that PureCloud Data Actions only support secure communications via HTTPS over port 443. Because Data Actions are communicating over the public Internet we made the decision to only support secure connections.

    If it is not possible to secure the web service you are attempting to connect to, there are a couple of options. You could make an intermediary service that is secure to proxy from PureCloud to the third party. The other option is to use a bridge web service connector. The second option requires you to manage a windows server and is much less flexible than data actions.

    --Jason


    alialjohani | 2018-09-11 12:46:20 UTC | #5

    Thank you very much, Jason.

    Best Regards, Ali


    system | 2018-10-12 12:46:22 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: 3516