San Francisco Mandatory Open Data API Rules

Technology and Data California 3 Minutes Read ยท published February 06, 2026 Flag of California

San Francisco, California requires city data to be accessible and machine-readable where the city designates datasets for public release. This article summarizes the practical obligations for agencies and vendors operating Open Data APIs in San Francisco, outlines technical expectations, enforcement and appeal paths, and gives step-by-step actions for publishing or reporting noncompliance.

Scope & Requirements

Agencies must publish datasets and, when available, provide machine-accessible APIs, standard metadata, and licensing that allows reuse. Requirements typically cover data format (CSV, JSON), machine-readable metadata, dataset documentation, update cadence, and clear licensing. Specific dataset inclusion and exemptions are determined by the city program.

  • Data formats: JSON, CSV, GeoJSON as required by the portal.
  • Metadata: title, description, update frequency, contact point.
  • Update cadence: publish schedule or last-updated timestamp.
  • Exemptions: privacy, security, or legal restrictions where applicable.
Follow the city portal templates for metadata and licensing to ensure datasets are accepted and discoverable.

For dataset hosting, DataSF operates the city open data portal and maintains technical guidance and catalog pages for publishers [1].

Technical API Standards

APIs should support stable endpoints, documented request parameters, pagination, rate limits, and machine-readable responses. Publishers should include sample requests and clear error handling semantics. Authentication is usually not required for public datasets but may apply for restricted data.

  • Endpoints: stable, versioned URL patterns and consistent field names.
  • Schema: documented field types, units, and coordinate reference systems for geospatial data.
  • Rate limits and pagination: follow portal guidance to avoid service disruption.
  • Documentation: include examples, update notes, and contact info.

Penalties & Enforcement

Enforcement responsibility for Open Data publication rests with the Mayor's Office of Data and Innovation and the DataSF program; specific sanction amounts or statutory fines are not specified on the cited program pages [2]. The portal and program pages describe compliance expectations, reporting channels, and administrative follow-up rather than a published fine schedule.

  • Enforcer: Mayor's Office of Data and Innovation / DataSF program; they coordinate compliance and technical assistance.
  • Inspection & complaint: report dataset or API issues via the official contact or portal submission form.
  • Appeals/review: not specified on the cited page; contact the program for review timelines.
  • Fines and monetary penalties: not specified on the cited page.
  • Non-monetary sanctions: removal from portal, publication notices, and administrative directions to remedy data gaps may be used.
If you receive a compliance notice, contact the program promptly to request guidance or a correction timeline.

Applications & Forms

Published, standardized forms specific to Open Data compliance are not listed on the program pages; dataset publication is typically handled through the DataSF portal submission workflow and the program's intake process, or by contacting the Mayor's Office of Data and Innovation for guidance [2].

Common Violations

  • Missing or outdated metadata, which hinders reuse.
  • Failure to publish machine-readable formats; providing only PDFs or images.
  • Not publishing required updates or removing timestamps.
  • Incorrect licensing statements or ambiguous reuse terms.

FAQ

Who manages San Francisco's Open Data program?
The Mayor's Office of Data and Innovation and the DataSF program manage the open data portal and technical guidance.
Does the city charge fees to publish an open dataset?
The program pages do not list a publication fee; dataset publication is handled through the portal or program intake.
How do I report a missing or incorrect dataset?
Report issues via the DataSF contact or the Mayor's Office of Data and Innovation submission channels; the program triages requests and advises agencies on remediation.

How-To

  1. Prepare dataset: ensure fields, types, and descriptive metadata are complete.
  2. Format data: export to CSV/JSON/GeoJSON and validate schemas.
  3. Submit to portal: use the DataSF upload or intake workflow and attach metadata and contact details.
  4. Address feedback: respond to program review requests and fix schema or privacy issues.
  5. Monitor and update: keep the dataset current and respond to user reports.

Key Takeaways

  • Use standard formats and thorough metadata to ensure discoverability.
  • Contact DataSF early for technical assistance and intake guidance.
  • Enforcement emphasizes remediation and program-led compliance rather than a published fine schedule.

Help and Support / Resources

  1. [1] City of San Francisco DataSF portal
  2. [2] Mayor's Office of Data and Innovation - Open Data

Categories

General Governance and Administration Public Safety Public Health and Welfare Land Use and Zoning Housing and Building Standards Transportation Environmental Protection Parks and Public Spaces Business and Consumer Protection Taxation and Finance Labor and Employment Education Civil Rights and Equity Elections and Campaign Finance Events and Special Uses Signs and Advertising Utilities and Infrastructure Technology and Data