Sorry to be the bearer of bad news but the issue is with your site and there's no way to prevent a obviously intended notification. The notification informs users that the site is not fully secure, which its not if you are using 3rd party scripts over HTTP. If you want to solve the problem then you must use HTTPS:// on all local and external resources.

So if you want users knowing that your site is fully secure and you want Google to reward a bit of SEO value to the site because of it, then you must either have them upgrade to SSL or ditch the widget all together... there is no workaround for this issue...

Your three options are:

1. Remove the widget.
2. Accept the notification
3. Ask them to upgrade the API service to HTTPS.

Sorry to be the bearer of bad news but the issue is with your site and there's no way to prevent a obviously intended notification. The notification informs users that the site is not fully secure, which its not if you are using 3rd party scripts over HTTP. If you want to solve the problem then you must use HTTPS:// on all local and external resources.

So if you want users knowing that your site is fully secure and you want Google to reward a bit of SEO value to the site because of it, then you must either have them upgrade to SSL or ditch the widget all together... there is no workaround for this issue... Also rather than using https:// you should opt to use //example.com/image.jpgif the site is accessible via both protocals.

Your three options are:

1. Remove the widget.
2. Accept the notification
3. Ask them to upgrade the API service to HTTPS.