Securing Web Services and MAR 2.0

The Office of the Chief Technology Officer (OCTO) will be securing all existing Web Service Operations over by moving them to HTTPS only on August 31st, 2017 - ensuring that all communication with these services is encrypted.  

If you have an application that uses one of these web services, for example the popular Master Address Repository service, you will need to modify the code in a minimal way. These API calls need to be repointed by just adding an 's' onto the http in the url – everything else stays the same. 

For example,'http://citizenatlas.dc.gov/newwebservices/locationverifier.asmx?op=findLocation' will need to become 'https://citizenatlas.dc.gov/newwebservices/locationverifier.asmx?op=findLocation'. 

This transition is part of an effort to further secure DC's data. Users of these services must update their code to HTTPS by August 31st, 2017. After this date, any URLs that use HTTP will not work.  

HTTPS helps protect the privacy of our users and improve confidence in, and integrity and authenticity of DC's data.  Read more information about the benefits of https security. Additional content can be found at OCTO Data Team Web Services. 

By the way, newer and better MAR web services are on its way. MAR 2.0 web services will include many improvements including API keys, REST endpoints,  and support for autocomplete. While capabilities are being expanded, some operations that are infrequently used be retired. A wealth of documentation about MAR 2.0 will be made available to you later this year.

Visit us on the web at http://dcgis.dc.gov and http://octo.dc.gov

Connect with us
on Twitter
@opendatadc

Contact open.data@dc.gov with any questions or comments.

Having trouble viewing this email? View it as a Web page.