Hi @Boopathy, Elango ,
this is likely caused by you loading a page of your site in the browser using HTTPS (secure), then a link (or some ajax call) on the page attempting to load content using HTTP (not secure). This is prevented to stop accidental loading of unsecured content into a page that was loaded using SSL.
The best way to remedy this is to configure your API to use SSL (if not already doing so), then use HTTPS for the call to the API.
Cheers.