CKAN Action API

CKAN is the closest thing open government data has to a de facto standard, and it achieved that by being software rather than a specification. Its Action API — a uniform JSON interface with stable endpoints like package_search, package_show and datastore_search — comes with the platform, so every deployment exposes the same shape without anyone writing an API design document.

• Uniform across deployments - a client written against one CKAN portal works against most others. That is portability achieved by shared implementation rather than shared schema.
• Search-first - package_search exposes the catalog’s full-text and faceted search, which makes the whole portal discoverable programmatically.
• Bulk retrieval is normal - datasets are downloadable in full, which is exactly the exit path most commercial APIs never publish.
• Open source - the API surface cannot be revoked by a vendor, because there is no vendor.

What the evidence shows

The State of Canadian Travel APIs records Transport Canada publishing through CKAN Action API 2.8, alongside OGC WMS 1.3.0 and Esri ArcGIS REST, under the Open Government Licence – Canada: worldwide, royalty-free, perpetual, non-exclusive, commercial use permitted, terminating only on breach — no minimum term, no exclusivity, no fees, nothing to sign.

Against the rest of the sector that is close to unrecognisable. Across the travel quartet, only seven of forty newly researched organizations are self-serve, thirteen gate behind a commercial agreement, and seven more behind accreditation or a licence. Only seven of forty publish a documented exit path, and four of those seven are regulators. Transport Canada is one of them, and CKAN is why: bulk export is a property of the platform, not a concession negotiated per customer.

The reading worth carrying: an off-the-shelf open-data platform gave a regulator a better agent-reachable surface than any commercial travel organization in its market built deliberately.