Liverpool Open Data Portal Bylaw & API Publication

Technology and Data England 3 Minutes Read ยท published February 12, 2026 Flag of England

Introduction

This guide explains how Liverpool, England public bodies should publish datasets and APIs from the municipal open data portal, balancing transparency obligations with data protection and local policy. It summarises the governing transparency code, practical publication steps, responsible teams and escalation routes for non-compliance, and points to official Liverpool and national sources for forms and complaints.[1]

Publish machine-readable datasets with metadata and licence information where possible.

Scope and Legal Basis

Local publishing of datasets and APIs is governed by the national transparency expectations for local authorities and by Liverpool City Council policy on open data and information access. Key constraints include copyright, licensing, and personal data protection under UK law; where the council relies on national guidance, that guidance is cited below.[2]

What to Publish

  • Core municipal datasets such as spending, contracts, and council decisions where no exemption applies.
  • APIs that provide machine-readable access to non-exempt datasets.
  • Metadata and licence statements to allow reuse.

Penalties & Enforcement

Liverpool City Council enforces information publication through its governance and information teams; financial penalty levels specific to open data publication are not provided on the cited Liverpool policy page and are therefore not specified on the cited page.[1]

  • Fine amounts: not specified on the cited page.
  • Escalation: first, repeat and continuing offence procedures are not specified on the cited page.
  • Non-monetary sanctions: orders to publish, information notices, or referral to oversight bodies may be used; exact sanctions are not specified on the cited page.
  • Enforcer: Information Governance/Legal Services at Liverpool City Council; complaints and inspection pathways are administered by the council and, for data protection matters, by the Information Commissioners Office (ICO).[3]
  • Appeal/review routes: internal review with the council; external complaint to the ICO for personal data matters; specific time limits for appeals are not specified on the cited council page.
  • Defences/discretion: exemptions for personal data, commercial confidentiality, or legal privilege apply; reasonable excuse provisions or formal variances are not detailed on the cited page.
If you believe a dataset should be published contact the council information team as a first step.

Applications & Forms

The Liverpool site does not publish a specific "open data publication" application form; publication is normally managed by the councils information or digital team and by dataset owners within services. If no form is published, submit requests or notices via the council contact channels listed below.[1]

Practical Publication Steps

  • Identify the dataset owner and confirm licence and copyright status.
  • Assess and remove personal data or apply anonymisation before publication.
  • Create machine-readable files and an API endpoint with documentation and metadata.
  • Record decisions and publish a dataset description and licence on the portal.
Publish metadata and a clear licence to enable lawful reuse.

Common Violations

  • Publishing personal data without lawful basis (may lead to ICO complaint).
  • Failing to provide machine-readable formats or metadata.
  • Omitting licence or reuse terms.

FAQ

Q: Who decides which datasets are published?
A: Dataset owners within Liverpool City Council, supported by the Information Governance and digital teams, prioritise publication according to transparency obligations and data protection constraints.
Q: Can I request a dataset that is not published?
A: Yes, you can request datasets via the councils contact channels; if personal data concerns arise you may be referred to the ICO. [3]
Q: Are there fees for accessing datasets or APIs?
A: The councils published policy does not specify fees for open datasets or API access; fees are typically not charged for open data but may apply to bespoke requests.

How-To

  1. Identify the dataset owner and confirm licensing and copyright status.
  2. Assess for personal data and apply anonymisation or seek legal advice if necessary.
  3. Create machine-readable files and document schema, fields and update cadence.
  4. Publish datasets and APIs on the council portal with clear licence and contact details.
  5. Monitor usage and respond to queries or complaints through the councils contact channels.

Key Takeaways

  • Follow national transparency guidance and local policy when publishing open data.
  • Ensure removal or lawful handling of personal data before publication.

Help and Support / Resources


  1. [1] Liverpool City Council  Open Data and Transparency
  2. [2] UK Gov  Local Government Transparency Code
  3. [3] Information Commissioners Office (ICO)