Austin City Ordinance: Contractor Data & API Standards
Austin, Texas requires contractors working under city contracts to meet data publication and API standards where those requirements are included in contract terms. This article explains typical obligations, how enforcement works, and practical steps contractors should take to comply with Austin city requirements for publishing required datasets and APIs.
What the rule typically requires
When a City of Austin contract or solicitation includes data-publishing clauses, contractors are generally required to publish machine-readable datasets, maintain API endpoints or transfer mechanisms, document schemas and update schedules, and follow specified licensing and access rules. Contract clauses vary by department and procurement.
- Publish machine-readable datasets or provide API access for city-owned data derived from contract work.
- Provide data dictionaries, schemas, and example requests and responses.
- Adhere to update frequency and retention schedules specified in the contract.
- Follow security, privacy, and licensing provisions set by the city for data sharing.
- Support city acceptance testing and remediation when datasets or APIs fail to meet requirements.
Penalties & Enforcement
Monetary fines: not specified on the cited page.[1]
Escalation and repeat offences: specific fine amounts, daily penalties, or escalation steps are not specified on the cited page; contract remedies and procurement sanctions depend on the contract and department processes.[2]
Non-monetary sanctions commonly used in procurement include corrective action orders, withholding of payment, contract termination, suspension or debarment from future contracting, and referral to legal action; the Purchasing Office administers contract compliance and may pursue contract remedies or other administrative actions as allowed by the solicitation and procurement rules.[2]
Enforcer and inspection pathway: the City of Austin Purchasing Office handles contract compliance and enforcement for procurement clauses; Development Services or the relevant program office enforces requirements tied to permits, inspections, or project acceptance. Complaints or compliance questions should be submitted to the responsible department contact listed in the contract or procurement solicitation.[2][3]
Appeals and review: specific appeal procedures and statutory time limits for contesting findings are set by procurement rules or contract terms and are not specified on the cited pages; contractors should follow the dispute resolution clause in their contract and consult Purchasing for appeal timelines.[2]
- Common violation - failure to publish required dataset by deadline: remedies and penalties not specified on the cited page.
- Common violation - API does not conform to documented schema: corrective action and possible contract withholding, not specified on the cited page.
- Common violation - security or privacy breach of city data: contract remedies and legal actions apply per city rules, not specified on the cited page.
Applications & Forms
No universal city form is published specifically for contractor dataset/API certification; requirements and any submission templates or exhibits are issued with the solicitation or contract documents. For technical publication tools and dataset hosting guidance, see the City of Austin Open Data Portal and departmental procurement exhibits for template language and submission instructions.[1]
Action steps for contractors
- Review contract exhibits and solicitation terms for explicit data and API requirements before bid submission.
- Prepare a data management plan: schema, API spec (OpenAPI recommended), update cadence, and security controls.
- Plan for acceptance testing with the city and schedule remediation time in project milestones.
- Estimate costs for hosting, maintenance, and support and include them in the bid when required.
- Contact the contracting officer or Purchasing Office early with questions about technical or legal compliance.[2]
FAQ
- Do all contractors have to publish datasets or APIs?
- No, only contractors whose contracts include explicit data-publishing or API requirements in the solicitation or contract exhibits are required to publish; check your contract terms.
- Where can I find technical publishing guidance from the City of Austin?
- The City of Austin Open Data Portal provides hosting and technical guidance for datasets; consult the portal and your contracting department for specific templates and requirements.
- Who enforces data-publishing requirements and how do I report a compliance issue?
- Contract compliance is managed by the City of Austin Purchasing Office and the program department that issued the contract; report compliance issues to the contracting officer or the department contact listed in the contract.
How-To
- Identify any data or API clauses in the solicitation or contract exhibits.
- Develop a data management plan and API specification that meets the city's technical criteria.
- Implement dataset publication or API endpoints and conduct internal testing against the documented schema.
- Coordinate acceptance testing with the contracting officer and remediate any issues before final acceptance.
- Retain records of publication, updates, and communications for procurement audits and possible appeals.
Key Takeaways
- Data and API obligations are contract-specific; inspect solicitation exhibits carefully.
- Prepare schema, API docs, and an update schedule before starting contract work.
- Contact the City Purchasing Office or the contracting department early for clarifications.
Help and Support / Resources
- City of Austin Open Data Portal
- City of Austin Purchasing Office
- City of Austin Development Services
- City of Austin main contacts