Developer APIs
Query it, serve it, export it — every dataset behind open interfaces, so your data moves wherever your systems need it.
The platform, open at the seams.
One API across your own datasets and the curated public catalogue — automate, integrate, extend.
WMS, WFS and WCS on every dataset, so a desktop GIS client connects without an integration project.
GeoJSON, Shapefile, GeoPackage, KML and CSV — take the data with you. No lock-in by design.
Standards first, because your stack already speaks them.
Pull datasets, query the catalogue and push results into the systems that need them — the same governed data the app reads.
Standards-compliant services on every dataset: the fastest way into QGIS, ArcGIS and anything else that speaks OGC, with no per-extension licence.
Getting data out of the platform and into the work.
A national programme's facility dashboard reads boundary, facility and population layers straight from OGC WMS/WFS and the REST API, so the map it draws comes from the same governed data the GIS unit curates. Integration stops being a re-upload, and the roles that apply in the app apply to every call.
An engineering or planning firm connects QGIS or ArcGIS to the platform's OGC services — or installs the direct QGIS plugin — and keeps working in the desktop client it already uses, against layers that stay current. Deliverables are built on the current data, with nothing converted or re-hosted to get there.
When a team deploys where connectivity does not follow, it exports the layers it needs — GeoPackage, Shapefile, KML, GeoJSON or CSV — with provenance and licence attached. Field laptops open the format they already use, and it is clear which dataset version the work was done against.
Questions, answered.
What do the Developer APIs cover?
A REST API over datasets and the catalogue, OGC WMS/WFS/WCS services on every dataset, and exports to the open formats your tools expect — GeoJSON, Shapefile, GeoPackage, KML and CSV.
Do the APIs need a paid plan?
Catalogue API access and OGC services are part of Professional and above. The platform itself — maps, spatial analysis and the catalogue — is available on every plan, including Free.
Is there a QGIS plugin?
Yes. A direct QGIS plugin sits alongside the standard OGC services and the REST API, so QGIS users get the shortest path to live catalogue data.
Ready to connect your stack?
Point a REST call or an OGC client at the catalogue and see governed data arrive where your systems already work.