Buildings API
Use this page to choose a building search or lookup, prepare your first request, and find guidance on footprints and attributes.
When to use this API
Retrieve Australian building footprints, characteristics, and relationships to addresses, cadastral parcels, and properties.
Start with the Buildings Quickstart to find buildings near a point, retrieve optional attributes, and follow address relationships. The current reference is labelled v2.1. Requests use /v2/buildings.
| You have… | Use |
|---|---|
| A building PID | Building Feature |
| Latitude and longitude | Find by point |
| A rectangular search extent | Find by bounding box |
| An address, property, or cadastre identifier | Find by identifier |
| A building PID and a need for related records | Building Addresses, Building Cadastre, or Building Properties |
For bulk data delivery, use the Datasets API. For map tiles, use the Maps API.
Access: Use a Geoscape Hub application with Buildings API access and a plan that permits premium data. Optional attributes can add credit costs.
Send its Consumer Key directly in the Authorization header. See Authentication for application and tester setup.
Responses
- Building geometry represents the roof outline as a
MultiPolygon. Geographic coordinates use[longitude, latitude, z]order - Building area is measured in square metres.
totalAreasums the building areas on the current response page - Follow
links.nextfor paginated searches and relationships. A single-building lookup has no pagination links - Read
messagesand retain the returnedattribution
Further guidance
- Additional Properties: choose height, roof, and solar data and check credit costs
- Field Migration: migrate legacy fields and additional-property requests
- Buildings Technical Description and Buildings Product Guide: review coverage, capture methods, and dataset definitions
- CRS & GDA2020: select input and response coordinate systems
- Error Handling, Rate Limiting, and Attribution: apply shared integration requirements
Versions
| Version | Reference |
|---|---|
| v2.1 (current) | Endpoint reference |
| v1 (legacy) | Endpoint reference |
Use the current version for new integrations. Legacy identifies an older version. Individual deprecated endpoints are marked in the reference.