API Guidance for HTTPS transition on 9/30/2016

[in...@ncbi.nlm.nih.gov]

Dear Colleagues,

As we announced on June 10, 2016 (https://www.ncbi.nlm.nih.gov/news/06-10-2016-ncbi-https/), NCBI will be transitioning to using HTTPS-only protocols on September 30, 2016. This change may affect any software that uses NCBI APIs such as the E-utilities or NCBI software toolkits such as the C/C++ and SRA toolkits.

Based on a review of incoming API requests, we have identified your email address as being associated with API calls using the HTTP protocol. We are writing to ensure that you are aware of these upcoming changes so that you can make any necessary updates to your software. If you are not making such calls, please disregard this message and accept our apologies.

Recently we published a page that describes these changes and offers suggested actions you can take to mitigate any problems with your software that may arise. It also lists several test servers that you can use to check the performance of your current API calls.

http://www.ncbi.nlm.nih.gov/home/develop/https-guidance.shtml

This page is also linked from the NCBI Develop page (a direct link from the NCBI home page) and the NCBI API page:

http://www.ncbi.nlm.nih.gov/home/develop/
http://www.ncbi.nlm.nih.gov/home/develop/api.shtml

Please review these documents and plan to take action soon. If you have questions, please write to in...@ncbi.nlm.nih.gov.