mapshare.vic.gov.au APImapshare.vic.gov.au ↗
Access Victorian government geocoding via the MapShare Victoria API. Search addresses, parcels, suburbs, streets, postcodes, and Crown land with 14 endpoints.
No input parameters required.
curl -X GET 'https://api.parse.bot/scraper/99d712f4-a0d5-421c-9298-c62942b0adfc/list_geocoder_services' \ -H 'X-API-Key: $PARSE_API_KEY'
List all available geocoder services on the MapShare Victoria ArcGIS server. Returns the server version and an array of available geocoding service names and types.
No input parameters required.
{
"type": "object",
"fields": {
"services": "array of service objects each containing name and type",
"currentVersion": "number indicating the ArcGIS server version"
},
"sample": {
"data": {
"folders": [],
"services": [
{
"name": "Geocoder/Apiary",
"type": "GeocodeServer"
},
{
"name": "Geocoder/VMAddressEZIAdd",
"type": "GeocodeServer"
},
{
"name": "Geocoder/VMParcelLotStreet",
"type": "GeocodeServer"
}
],
"currentVersion": 10.81
},
"status": "success"
}
}About the mapshare.vic.gov.au API
The MapShare Victoria API exposes 14 endpoints for geocoding and address lookup across the state of Victoria, Australia, drawing on official Victorian government spatial datasets. You can search standard street addresses via find_address_candidates_ezi_address, resolve lot and parcel identifiers through find_address_candidates_parcel_lot_street, look up Crown land parcels, reverse-geocode coordinates to a nearest address, and retrieve autocomplete suggestions across addresses, localities, streets, and Standard Parcel Identifiers (SPI).
Address and Parcel Geocoding
The API covers two primary address datasets. find_address_candidates_ezi_address geocodes standard Victorian street addresses from the EZI dataset, returning a candidates array where each entry includes address, location (x/y coordinates), score, attributes, and extent. The companion suggest_ezi_address endpoint accepts a partial text string and returns suggestions with text, magicKey, and isCollection fields — pass the magicKey back to the geocode endpoint for a precise, unambiguous match. The same suggest-then-geocode pattern applies to lot/parcel/street queries via suggest_parcel_lot_street and find_address_candidates_parcel_lot_street.
Parcel Identifiers and Crown Land
find_address_candidates_spi accepts a Standard Parcel Identifier string (e.g. PS831714) and returns matching parcel locations. find_address_candidates_crown_parcel resolves Crown land parcel identifiers such as 2000\PP2277. Both return the same candidates structure with location, score, and spatialReference (including wkid and latestWkid for coordinate system identification). All coordinates are in WGS84/GDA94.
Locality, Street, and Postcode Lookups
For broader geographic queries, find_address_candidates_locality geocodes suburb and locality names, find_address_candidates_street resolves street names to their spatial extent, and find_address_candidates_postcode returns the centroid for a given 4-digit Victorian postcode. Each has a corresponding suggest_* endpoint for incremental search. The suggest_locality endpoint, for example, returns suburb name matches from a prefix like MEL.
Service Discovery and Metadata
list_geocoder_services returns the ArcGIS server currentVersion and a services array listing available geocoder names and types. geocode_server_info accepts a service_name parameter (e.g. VMAddressEZIAdd, VMLocality) and returns capabilities, addressFields with field definitions, and a serviceDescription — useful for confirming which fields a given service supports before building a query.
- Resolving user-entered Victorian addresses to coordinates for mapping applications
- Validating property addresses against the official EZI dataset during data entry
- Looking up land parcel boundaries by SPI for property conveyancing or title workflows
- Reverse-geocoding GPS coordinates to the nearest street address for field service apps
- Building suburb or street autocomplete in forms targeting Victorian addresses
- Identifying Crown land parcels by identifier for environmental or land management tools
- Geocoding postcode centroids to aggregate or visualise Victorian regional data
| Tier | Price | Credits/month | Rate limit |
|---|---|---|---|
| Free | $0/mo | 100 | 5 req/min |
| Hobby | $30/mo | 1,000 | 20 req/min |
| Developer | $100/mo | 5,000 | 250 req/min |
One credit = one API call regardless of which marketplace API you call. Exceeding the rate limit returns a 429 response. Authenticate with the X-API-Key header.
Does MapShare Victoria have an official developer API?+
What does reverse geocoding return, and how precise is it?+
reverse_geocode_parcel_lot_street takes x (longitude) and y (latitude) in WGS84/GDA94 and returns an address object containing Address, Match_addr, and additional component fields, plus a location object with the snapped coordinates and spatialReference. Results are based on the VMParcelLotStreet dataset, so the nearest match is a lot or parcel address rather than a rooftop point — precision depends on parcel geometry and is strongest in urban areas.Does the API cover addresses outside Victoria?+
Can I retrieve polygon or boundary geometry for a parcel or suburb, not just its centroid?+
extent rectangle — they do not return polygon geometries for parcels, suburbs, or streets. You can fork the API on Parse and revise it to add endpoints targeting the MapShare Victoria WFS or feature services, which expose polygon geometry for parcels and administrative boundaries.What is a magicKey and when should I use it?+
magicKey is an opaque identifier returned in the suggestions array from any suggest_* endpoint. Passing it as the magic_key parameter to the corresponding find_address_candidates_* endpoint constrains the geocoder to that exact suggestion, avoiding ambiguous matches when multiple addresses share similar text. It is optional — omitting it triggers a broader text search — but recommended whenever you are building a two-step suggest-then-geocode UI.