> For the complete documentation index, see [llms.txt](https://sfdigitalservices.gitbook.io/dataset-explainers/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://sfdigitalservices.gitbook.io/dataset-explainers/open-data-portal-website-update.md).

# Open Data Portal website update

Read about DataSF's website change for the San Francisco Open Data Portal

DataSF is updating the Open Data Portal’s web address from **data.sfgov.org** to **data.sf.gov**. This helps us meet City and State requirements for using official .gov domains. The migration will not impact your use of the portal. All existing links, bookmarks, and API queries will automatically redirect to the new domain. If you experience any issues, please click “Contact us” on the home page or email [**support@datasf.org**](mailto:support@datasf.org).

### **What’s changing?**

The DataSF Open Data Portal moved to **data.sf.gov** on September 8, 2026.

### **Why?**

To comply with government standards requiring local agencies to use recognized .gov domains. 

[California Government Code § 50034](https://leginfo.legislature.ca.gov/faces/codes_displaySection.xhtml?lawCode=GOV\&sectionNum=50034.), enacted via AB 1637 (2023), requires all California cities and counties to use a“.gov” or“.ca.gov” domain for their public-facing websites and employee email addresses by January 1, 2029.

### **Will this affect me?**

No. Existing links, bookmarks, and API queries will automatically redirect to the new address. However, by December 31, 2026, any hardcoded links or API calls should be moved to use data.sf.gov directly to avoid issues. 

### **Need help?**

Use the “Contact us” link on the home page or email [**support@datasf.org**](mailto:support@datasf.org).

### Known issues & workarounds

{% hint style="warning" %}
As of 9/10/26, we are aware of the following issues with the web domain redirect and are actively working to resolve these. We will continue to provide updates here.
{% endhint %}

* SODA API queries to `data.sfgov.org` with `$SELECT` parameter do not redirect fully to data.sf.gov. All other API queries are redirecting correctly.
  * Workaround: the recommended workaround is to update the domain in the API query to `data.sf.gov` now. This will also avoid having to update your API queries by the December 31, 2026 deadline mentioned above. 
* Power BI connections/ refresh: some users are getting an invalid credentials error for existing data.sfgov.org queries when their Power BI report refreshes. 
  * Workaround: the recommended workaround is to update the domain in the API query to `data.sf.gov` now. This will also avoid having to update your API queries by the December 31, 2026 deadline mentioned above. You can also try to update (and/or clear) the data source credentials in Power BI Desktop and/or Power BI Service to refresh the connection.<br>