Tempe Junction Open Data Bylaw Guide

Technology and Data Arizona 4 Minutes Read · published February 21, 2026 Flag of Arizona

Tempe Junction, Arizona maintains public access expectations for municipal datasets and APIs while balancing privacy and operational needs. This guide explains how to find published APIs, request new datasets, and submit public-records requests locally. It summarizes who enforces access, what forms and technical endpoints are available, typical timelines, and practical steps to get machine-readable data for research, accountability, or app development. Where Tempe Junction does not publish a municipal code specific to "open data," this guide references the closest official Tempe resources and Arizona public-records statutes for process and authority; statements are current as of February 2026.

Published APIs and Portals

Tempe Junction commonly publishes machine-readable datasets and APIs through an open data portal or an IT/GIS program. Search the municipal open data catalog to find dataset schemas, API endpoints, and usage instructions. Many datasets offer Socrata or CKAN-style REST endpoints and downloadable CSV, GeoJSON, and shapefile formats; check dataset pages for rate limits, API keys, and terms of use on the portal listed below Tempe Open Data portal[1].

  • Look up dataset metadata and field definitions on the portal dataset page.
  • Use provided API endpoints for programmatic queries and exports.
  • Check licensing or terms of use attached to each dataset before reuse.
Not all municipal datasets are public; some contain restricted or exempt records.

How to Request a New Dataset or an API Endpoint

If the data you need is not already published, request dataset publication or a custom API feed through the city clerk or IT/open data contact listed on the public-records and IT pages. Describe the dataset fields, preferred formats, and intended use. For records not routinely published, submit a public-records request using the official process on the City Clerk page City Clerk public records page[2].

  1. Identify the dataset name, date range, and fields required.
  2. Search the open data portal for existing endpoints or similar tables.
  3. Contact the IT/Open Data or City Clerk office to ask about publication or request a records release.
  4. If needed, submit a formal public-records request via the City Clerk process.
When possible, request structured exports (CSV or GeoJSON) to avoid manual reformatting.

Data Formats, Privacy, and Redaction

Published datasets often include geospatial files, tabular CSVs, and JSON APIs. Personal data, active-investigation details, and protected health or safety information may be redacted under Arizona public-records exemptions; contact the City Clerk for redaction explanations. For legal interpretation of exemptions, see Arizona public records statutes Title 39, Arizona Revised Statutes[3].

  • Protected or exempt records may be withheld or provided with redactions.
  • Requesters should state format preferences to reduce processing delay.
  • Legal citations for redactions originate from state statutes and municipal procedures.
Requests asking for new automated APIs may require technical review and scheduling.

Penalties & Enforcement

Enforcement of open-data publication and public-records compliance typically falls to the City Clerk, the municipal IT or Open Data team, and the city attorney for legal disputes. Specific fines or statutory penalties for failure to publish datasets are not specified on the cited municipal pages; enforcement tends to follow public-records procedures and judicial review where statutory duties exist[2][3].

  • Monetary fines: not specified on the cited page.
  • Escalation: first, repeat, or continuing offences and per-day fines are not specified on the cited pages.
  • Non-monetary sanctions: orders to disclose records, court actions, and injunctive relief may be available under state law.
  • Enforcer: City Clerk, municipal IT/Open Data program, and city attorney handle compliance and enforcement.
  • Inspections/complaints: submit complaints or records requests via the City Clerk public-records page or contact IT for API issues.
  • Appeals/review: appeals proceed through administrative channels or court; specific statutory time limits are not specified on the cited municipal pages and should be confirmed with the City Clerk.
  • Defences/discretion: exemptions, confidentiality determinations, and reasonable-excuse defenses are governed by state public-records statutes and municipal procedures.

Applications & Forms

Use the City Clerk public-records request mechanism for unreleased datasets; the City Clerk page provides instructions and submission methods. If no specific open-data publication form is listed, request publication via email to the IT/Open Data contact or include the request in a formal public-records submission. The City Clerk page indicates how to submit requests and contact details but does not publish a single standardized "open data API request" form, current as of February 2026[2].

Action Steps

  • Search the open data portal for existing datasets and endpoints.
  • Contact the IT/Open Data team for publication or technical questions.
  • Submit a public-records request via the City Clerk if data is not published.
  • If fees apply, follow the City Clerk fee schedule and payment instructions.
Record requests that require redaction or extensive processing may incur time and cost.

FAQ

How do I find existing APIs and datasets for Tempe Junction?
Search the municipal open data portal for published datasets and API endpoints; dataset pages list formats and API call examples. See the Tempe open data portal for datasets and endpoints.[1]
Can I request unpublished data or a custom API?
Yes; submit a public-records request or contact the IT/Open Data team via the City Clerk public-records page to request dataset publication or a records extraction.[2]
How long will it take to receive requested data?
Processing times vary; specific statutory response timeframes or municipal timelines are not specified on the cited municipal pages and should be confirmed with the City Clerk.[2]

How-To

  1. Locate the dataset on the open data portal; note the dataset name and fields.
  2. If not found, draft a concise public-records request describing the records, date range, and preferred format.
  3. Submit the request via the City Clerk public-records page or email the IT/Open Data contact.
  4. If you require automated API access or a production feed, request technical review and include use case and expected volume.
  5. If denied or delayed, follow the City Clerk appeals process or seek statutory remedies under Arizona public-records law.

Key Takeaways

  • Always check the open data portal first before submitting a records request.
  • City Clerk and IT/Open Data are the primary contacts for dataset publication.
  • Provide clear field and format requirements to speed processing.

Help and Support / Resources

  1. [1] Tempe Open Data portal
  2. [2] City of Tempe City Clerk public records page
  3. [3] Arizona Revised Statutes - Title 39

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