San Diego Open Data API Limits - City Policy & Fees

Technology and Data California 3 Minutes Read · published February 05, 2026 Flag of California

San Diego, California maintains an Open Data portal for municipal datasets and API access. This article summarizes what the City publishes about API rate limits, fee schedules, enforcement, and practical steps to request higher-volume or commercial access. Where official numeric limits, penalties, or fees are not published on the City portal, this guide notes that and points to the City’s Open Data site for the authoritative resource. For the portal and platform details see the City of San Diego Open Data portal data.sandiego.gov[1]. Current as of February 2026.

Overview of API Access

The City hosts datasets and an API for programmatic access. Typical access methods include anonymous requests, keyed requests for registered users, and enterprise/bulk arrangements for high-volume needs. The portal documents dataset endpoints and method examples but does not list a citywide, consolidated fee schedule or per-endpoint rate numbers on the main portal pages.

  • Datasets and endpoints: listed per dataset on the portal.
  • Registration: developer keys or API tokens may be offered for higher request limits.
  • Platform: the portal indicates third-party hosting for datasets; check dataset metadata for platform notes.
Check each dataset's metadata page for endpoint-specific notes before building production workflows.

Penalties & Enforcement

The City portal itself does not publish a specific municipal bylaw listing fines or statutory penalties tied to exceeding API limits; numeric fines or per-day penalties are not specified on the cited page. Enforcement for misuse or abusive automated traffic is generally handled by the data platform administrators and City IT or Open Data program staff, who may suspend keys or block IPs for noncompliance. See the City Open Data portal for official terms and acceptable use policies.[1]

  • Monetary fines: not specified on the cited page.
  • Escalation: typical escalation (platform notice, key suspension, IP block) is used; specific first/repeat/continuing fine ranges are not specified on the cited page.
  • Non-monetary sanctions: suspension of API keys, IP blocking, termination of access, or referral to City legal counsel.
  • Enforcer: Open Data program and City IT; appeals or review routes are not detailed on the portal page.
If you require guaranteed throughput for production use, request an enterprise agreement in writing before deploying critical systems.

Applications & Forms

The portal does not publish a standardized municipal form or application number for fee-based or commercial API access; submission methods for special access are not specified on the cited page. Organizations seeking higher limits should contact the City Open Data program via the portal contact points or the City’s Open Government pages for current procedures.[1]

Operational Guidance and Common Violations

To avoid service interruption, follow these practical rules:

  • Rate-control: implement client-side throttling and backoff on 429 responses.
  • Request keys: register for an API key if the portal offers developer registration.
  • Contact before bulk pulls: notify the Open Data program if you plan large downloads or automated harvesting.
Common violations driving enforcement are excessive request volume, credential sharing, and automated scraping without notice.

Action Steps

  • Review dataset metadata and terms of use on the portal.
  • Contact the Open Data program to request higher limits or an enterprise agreement.
  • Obtain written terms for any fee-based access before initiating high-volume use.

FAQ

How do I find the City’s API rate limits?
The City portal lists dataset endpoints but does not publish a consolidated rate-limit table; check each dataset's metadata and the portal's platform documentation.
Is there a published fee schedule for commercial API access?
The portal does not publish a citywide fee schedule for API access; organizations should contact the Open Data program to request pricing or enterprise terms.
Who enforces API misuse and how do I appeal?
Enforcement is managed by the Open Data program and City IT; the portal does not provide a formal appeal timeline on its public pages.

How-To

  1. Review the dataset metadata and any terms listed on the dataset page.
  2. Prepare a written request describing required throughput, intended use, and data volumes.
  3. Submit the request via the City Open Data portal contact method or the Open Government contact page.
  4. Await City response and, if approved, sign any enterprise agreement before commencing high-volume access.

Key Takeaways

  • The City portal is the authoritative source for dataset endpoints; consolidated fees or fines are not published there.
  • Plan for throttling and contact the Open Data program for production or bulk access.

Help and Support / Resources

  1. [1] City of San Diego Open Data portal - data.sandiego.gov

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