Get information about the matched properties including the associated titles and parcels. You may provide only one of the three identifiers - an address, Council Property Number (CPN) in combination with Municipality or Property Persistent Feature Identifier (PFI). This helps to confirm the right title and/or property before then making an order for available certificates.
- Retrieve Crown allotment parcels including parcel SPI
Discovery API (1.9.0)
Property Persistent Feature Identifier (PFI) which uniquely identifies a property. A PFI is generated by the state once for each property at the point of creation and remains constant until a property is retired. Only a single property will be returned when this identifier is used. This parameter cannot be used in conjunction with propertyNumber + municipalityName or eziAddress.
Property Number assigned by the local government authority of the property. This parameter must always be paired with municipalityName. Also known as Council Property Number (CPN). Only a single property will be returned when this identifier is used. This parameter cannot be used in conjunction with propertyPfi or eziAddress.
Municipality of the property. This parameter must always be paired with propertyNumber. Only a single property will be returned when this identifier is used. This parameter cannot be used in conjunction with propertyPfi or eziAddress.
Property address as a single string (not broken into fields). It is the concatenation of key address attribute fields to provide a unique address for data matching. Format - blg_unit_, house_, road_name/type/suffix, plus locality & postcode fields. Multiple properties may be be returned when this identifier is used. This parameter cannot be used in conjunction with propertyNumber + municipalityName or propertyPfi. Note that a single property can have multiple addresses, e.g. 113 MEW LANE BAMAWM 3561 and 50 TWADDLE LANE BAMAWM 3561 An address can also be linked to multiple properties, such as BASEMENT 2 LONSDALE STREET MELBOURNE 3000. As a result, this identifier should be considered less specific than propertyPfi.
For customers who have premium access, specifies whether to include premium-only results in the discovery responses. If set to true, premium information (such as unencrypted title IDs) will be included in the response. Note that enabling this option may incur discovery charges.
Identifier of the customer this request is on behalf of. For premium discovery requests only.
Optional description to identify a transaction, used for billing purposes. Note that we'll be providing a separate order ID once the order has been submitted. For premium discovery requests only.
Unique UUID used to prevent duplicate premium discovery orders. For premium discovery only. This allows requests to be retried after a network failure without accidentally submitting two premium discovery orders. If you receive a network error or timeout, you should resend the request with the same idempotency-key. If the server is still processing the original POST, you will receive 429 Too Many Requests. Idempotency keys expire after 24 hours.
- Mock serverhttps://developer.servictoria.io/_mock/portal/rest/ddp-discovery-api/openapi/discovery/v1/properties
- Production environmenthttps://api.servictoria.io/ddp/discovery/v1/properties
- Test environmenthttps://test.api.servictoria.io/ddp/discovery/v1/properties
- curl
- JavaScript
- Node.js
- Python
- Java
- C#
- PHP
- Go
- Ruby
- R
- Payload
curl -i -X GET \
'https://developer.servictoria.io/_mock/portal/rest/ddp-discovery-api/openapi/discovery/v1/properties?propertyPfi=208045633&propertyNumber=603787&municipalityName=MELBOURNE&eziAddress=328%2F800+SWANSTON+STREET+CARLTON+3053&premium=true' \
-H 'Authorization: Bearer <YOUR_TOKEN_HERE>' \
-H 'customer-id: 12345' \
-H 'customer-reference: customer-reference-001' \
-H 'idempotency-key: cc4d91e3-17af-4d11-b333-eb449e62ff07' \
-H 'x-correlation-id: 824993ab-7366-4faa-963d-c456dec227a5'Successful Operation
Property persistent feature identifier (PFI) which uniquely identifies a property.
The status of a property identifies whether it is active or proposed. Proposed properties are attached to proposed parcels. This is where a parcel sub-division has not yet been fully completed but has gone through a significant way through the approval stage and so recognised as proposed.
This identifies whether the property has an associated Council Property Number (true) or not (false). There are properties which do not have a council property number and are typically common property areas of apartments and as such, cannot be bought or sold. If false then the councilPropertyDetails section will be omitted
If the property is known as Multi-assessment, then this is where more than one property belong to the same parcel. A typical example might be where individual shops belong in a shopping centre property.
Date the property and its PFI was created by the state.
Property address as a single string (not broken into fields). It is the concatenation of key address attribute fields to provide a unique address for data matching. Format - blg_unit_, house_, road_name/type/suffix, plus locality & postcode fields.
List of alias addresses associated with the requested property. Note, if a property has no alias addresses, an empty array will be returned.
List of parcels associated with the requested property(s). A parcel is generally a piece of physical land as defined by a geographic shape. It is also possible for a parcel to not be a physical piece of ground, but be defined also by where it is vertically. Note, if no associated parcels are found, an empty array will be returned.
A Standard Parcel Identifier (SPI) uniquely identifies a parcel. An SPI typically consists of either a Lot on Plan or a Crown Allotment. A Lot on Plan defines the allocated lot number on a particular plan. For example '101\PS328573' is lot 101 on the plan of subdivision 328573. There are instances of an SPI not containing a lot, eg: 'TP109554'. A Crown Allotment parcel is defined by up to five different factors including Allotment, Block, Portion, Section and SubDivision. For example '12~10A\PP5762' is Allotment 12 in Section 10a on the Parish Plan 5762.
The parcel types determine what can be done with the parcel. The type can be a lot (a normal parcel of land), a unit (belonging to an apartment development), Common property (jointly owned land as defined by something such as a body corporate), roads or reserves.
The lot type gives an indication of the use of the parcel or describes any lot limitations. Generally when the parcel has a parcel type of ‘lot’ or ‘unit’. They can be restricted (meaning it must be sold with another parcel), unrestricted (it does not need to be sold along with another parcel), an accessory unit like a storage area in an apartment complex or a carpark.
The status of a parcel identifies whether it is active or proposed. This is where a parcel sub-division has not yet been fully completed but has gone through a significant way through the approval stage and so recognised as proposed.
Crown Allotment. Crown Allotment descriptor.
Crown Block. A part of the parcel descriptor. It is utilized in combination with either Lot and Plan number or Allotment and Parish code.
Section. A part of the parcel descriptor. It is utilized in combination with either Lot and Plan number or Allotment and Parish code.
Crown Portion. Crown Portion descriptor.
List of titles associated with the requested property(s). Note, if no associated titles are found, an empty array will be returned.
An encrypted title identifier. Access to Vol/Fol is available only for premium discovery due to associated charges. This value is not guaranteed to remain stable over time. Customers should avoid relying on its persistence or consistency across API calls or over extended periods.
For premium discovery responses, this field contains the Volume/Folio (Vol/Fol) of a title.
The status of the title informs whether it is currently active, has become cancelled or partially cancelled.
Describes the ownership type of the title, the main two being Freehold for property owned by individuals and companies, and Crown land which is administered by public authorities.
{ "propertySummaries": [ { … } ], "orderSummary": { "orderId": "10219435", "totalPrice": 891, "totalGst": 89 } }
Request
Get information about the matched titles including the associated properties and parcels. You can provide a Volume and Folio number or the encrypted title identifier provided from other discovery APIs. This supports confirmation of the right title and/or property.
Title identifier, this can be either a volume/folio (eg: '10940/843') or an encrypted titleId as returned by operations on this API (eg: 'qp0gjuieZ5VzbNKtT/eZvqPryobRkEYxMA==' - this example is valid for the TEST environment only). The encrypted titleId's value is not guaranteed to remain stable over time. Customers should avoid relying on its persistence or consistency across API calls or over extended periods.
For customers who have premium access, specifies whether to include premium-only results in the discovery responses. If set to true, premium information (unencrypted title IDs) will be included in the response. Note that enabling this option may incur discovery charges. Customer will not be charged if the titleId is a volume/folio, rather than an encrypted titleId.
Identifier of the customer this request is on behalf of. For premium discovery requests only.
Optional description to identify a transaction, used for billing purposes. Note that we'll be providing a separate order ID once the order has been submitted. For premium discovery requests only.
Unique UUID used to prevent duplicate premium discovery orders. For premium discovery only. This allows requests to be retried after a network failure without accidentally submitting two premium discovery orders. If you receive a network error or timeout, you should resend the request with the same idempotency-key. If the server is still processing the original POST, you will receive 429 Too Many Requests. Idempotency keys expire after 24 hours.
- Mock serverhttps://developer.servictoria.io/_mock/portal/rest/ddp-discovery-api/openapi/discovery/v1/titles
- Production environmenthttps://api.servictoria.io/ddp/discovery/v1/titles
- Test environmenthttps://test.api.servictoria.io/ddp/discovery/v1/titles
- curl
- JavaScript
- Node.js
- Python
- Java
- C#
- PHP
- Go
- Ruby
- R
- Payload
curl -i -X GET \
'https://developer.servictoria.io/_mock/portal/rest/ddp-discovery-api/openapi/discovery/v1/titles?titleId=10940%2F843&premium=true' \
-H 'Authorization: Bearer <YOUR_TOKEN_HERE>' \
-H 'customer-id: 12345' \
-H 'customer-reference: customer-reference-001' \
-H 'idempotency-key: cc4d91e3-17af-4d11-b333-eb449e62ff07' \
-H 'x-correlation-id: 824993ab-7366-4faa-963d-c456dec227a5'Successful Operation
An encrypted title identifier. Access to Vol/Fol is available only for premium discovery due to associated charges. This value is not guaranteed to remain stable over time. Customers should avoid relying on its persistence or consistency across API calls or over extended periods.
For premium discovery responses, this field contains the Volume/Folio (Vol/Fol) of a title.
The status of the title informs whether it is currently active, has become cancelled or partially cancelled.
Describes the ownership type of the title, the main two being Freehold for property owned by individuals and companies, and Crown land which is administered by public authorities.
The identifier of a title made up of a volume number and a folio number separated by a slash. It is the numbering system used for titles, Crown Grants, Crown Leases and Mineral Leases. If volume folio was provided in the search, then, this field will return volume folio
The certificate of title may either be stored only electronically in the the Victorian Online Titles System (VOTS) or a duplicate may exist in physical paper format.
Address recorded against the title
The parcel(s) associated with the title are described in the Land Description.
{ "titleSummaries": [ { … } ], "orderSummary": { "orderId": "10219435", "totalPrice": 891, "totalGst": 89 } }
A Standard Parcel Identifier (SPI) uniquely identifies a parcel. An SPI typically consists of either a Lot on Plan or a Crown Allotment. A Lot on Plan defines the allocated lot number on a particular plan. For example '101\PS328573' is lot 101 on the plan of subdivision 328573. There are instances of an SPI not containing a lot, eg: 'TP109554'. A Crown Allotment parcel is defined by up to five different factors including Allotment, Block, Portion, Section and SubDivision. For example '12~10A\PP5762' is Allotment 12 in Section 10a on the Parish Plan 5762. If the input SPI contains a suffix character at the end and there is no matching parcel found, the suffix will be removed and the search retried. Note: due the backslash () in SPI's it's important URL encoded this parameter, many HTTP clients will do this automatically.
For customers who have premium access, specifies whether to include premium-only results in the discovery responses. If set to true, premium information (such as unencrypted title IDs) will be included in the response. Note that enabling this option may incur discovery charges.
Identifier of the customer this request is on behalf of. For premium discovery requests only.
Optional description to identify a transaction, used for billing purposes. Note that we'll be providing a separate order ID once the order has been submitted. For premium discovery requests only.
Unique UUID used to prevent duplicate premium discovery orders. For premium discovery only. This allows requests to be retried after a network failure without accidentally submitting two premium discovery orders. If you receive a network error or timeout, you should resend the request with the same idempotency-key. If the server is still processing the original POST, you will receive 429 Too Many Requests. Idempotency keys expire after 24 hours.
- Mock serverhttps://developer.servictoria.io/_mock/portal/rest/ddp-discovery-api/openapi/discovery/v1/parcels
- Production environmenthttps://api.servictoria.io/ddp/discovery/v1/parcels
- Test environmenthttps://test.api.servictoria.io/ddp/discovery/v1/parcels
- curl
- JavaScript
- Node.js
- Python
- Java
- C#
- PHP
- Go
- Ruby
- R
- Payload
curl -i -X GET \
'https://developer.servictoria.io/_mock/portal/rest/ddp-discovery-api/openapi/discovery/v1/parcels?spi=3A2%5CPS515587&premium=true' \
-H 'Authorization: Bearer <YOUR_TOKEN_HERE>' \
-H 'customer-id: 12345' \
-H 'customer-reference: customer-reference-001' \
-H 'idempotency-key: cc4d91e3-17af-4d11-b333-eb449e62ff07' \
-H 'x-correlation-id: 824993ab-7366-4faa-963d-c456dec227a5'Successful Operation
A Standard Parcel Identifier (SPI) uniquely identifies a parcel. An SPI typically consists of either a Lot on Plan or a Crown Allotment. A Lot on Plan defines the allocated lot number on a particular plan. For example '101\PS328573' is lot 101 on the plan of subdivision 328573. There are instances of an SPI not containing a lot, eg: 'TP109554'. A Crown Allotment parcel is defined by up to five different factors including Allotment, Block, Portion, Section and SubDivision. For example '12~10A\PP5762' is Allotment 12 in Section 10a on the Parish Plan 5762.
The parcel types determine what can be done with the parcel. The type can be a lot (a normal parcel of land), a unit (belonging to an apartment development), Common property (jointly owned land as defined by something such as a body corporate), roads or reserves.
The lot type gives an indication of the use of the parcel or describes any lot limitations. Generally when the parcel has a parcel type of ‘lot’ or ‘unit’. They can be restricted (meaning it must be sold with another parcel), unrestricted (it does not need to be sold along with another parcel), an accessory unit like a storage area in an apartment complex or a carpark.
The status of a parcel identifies whether it is active or proposed. This is where a parcel sub-division has not yet been fully completed but has gone through a significant way through the approval stage and so recognised as proposed.
Crown Block. A part of the parcel descriptor. It is utilized in combination with either Lot and Plan number or Allotment and Parish code.
Section. A part of the parcel descriptor. It is utilized in combination with either Lot and Plan number or Allotment and Parish code.
List of titles associated with the requested property(s). If no associated titles are found an empty array will be returned.
{ "spi": "3A2\\PS515587", "parcelType": "LOT", "lotType": "RESTRICTED", "parcelStatus": "ACTIVE", "isPartParcel": true, "parcelDetails": { "lot": "3A2", "planNumber": "PS515587S", "parish": "YEO", "township": "BARWON DOWNS TP", "allotment": "15D", "block": "1", "section": "A", "portion": "105", "subdivision": "16" }, "titles": [ { … } ], "properties": [ { … } ], "orderSummary": { "orderId": "10219435", "totalPrice": 891, "totalGst": 89 } }
Crown Allotment descriptor. At least one of Allotment OR Portion OR Section MUST be provided Note that Allotment is a more specific identifier than Section and Portion, so may return a smaller, more specific list of Crown allotment parcels.
Section is a part of the parcel descriptor. It is utilized in combination with either Lot and Plan number or Allotment and Parish code. Note that Section is less specific of an identifier than Allotment, so may return a larger, less specific list of Crown allotment parcels. At least one of Allotment OR Portion OR Section MUST be provided.
Crown Portion descriptor. Note that Portion is less specific of an identifier than Allotment, so may return a larger, less specific list of Crown allotment parcels. At least one of Allotment OR Portion OR Section MUST be provided.
Crown Block descriptor. A part of the parcel descriptor. It is utilized in combination with either Lot and Plan number or Allotment and Parish code.
Crown Subdivision descriptor.
Parish code. A list of parish names and their associated codes can be obtained from the GET /parishes endpoint. If only parishCode is used, townshipCode will not return in the response. At least one of Parish code OR Township code MUST be provided.
Township code. A list of township names and their associated codes can be obtained from the GET /townships endpoint. Note that townshipCode will only return in the response if townshipCode is used in the request At least one of Parish code OR Township code MUST be provided.
- Mock serverhttps://developer.servictoria.io/_mock/portal/rest/ddp-discovery-api/openapi/discovery/v1/parcels/crown-allotments
- Production environmenthttps://api.servictoria.io/ddp/discovery/v1/parcels/crown-allotments
- Test environmenthttps://test.api.servictoria.io/ddp/discovery/v1/parcels/crown-allotments
- curl
- JavaScript
- Node.js
- Python
- Java
- C#
- PHP
- Go
- Ruby
- R
- Payload
curl -i -X GET \
'https://developer.servictoria.io/_mock/portal/rest/ddp-discovery-api/openapi/discovery/v1/parcels/crown-allotments?allotment=H§ion=9&portion=105&block=1&subdivision=16&parishCode=2796&townshipCode=2796B' \
-H 'Authorization: Bearer <YOUR_TOKEN_HERE>' \
-H 'x-correlation-id: 824993ab-7366-4faa-963d-c456dec227a5'{ "crownAllotmentSummaries": [ { … } ] }
Last name of the proprietor. Either last name or company name must be populated. This will search for individual with the provided input. The search is case insensitive. If a given name is not provided, the results will include proprietors with the matching last name, but any given name.
Given name(s) of the proprietor. Can be used in conjunction with a last name. Not applicable for companies.
Company name. Either company name or last name must be populated. This will search for companies with the provided input.
- Mock serverhttps://developer.servictoria.io/_mock/portal/rest/ddp-discovery-api/openapi/discovery/v1/proprietors
- Production environmenthttps://api.servictoria.io/ddp/discovery/v1/proprietors
- Test environmenthttps://test.api.servictoria.io/ddp/discovery/v1/proprietors
- curl
- JavaScript
- Node.js
- Python
- Java
- C#
- PHP
- Go
- Ruby
- R
- Payload
curl -i -X GET \
'https://developer.servictoria.io/_mock/portal/rest/ddp-discovery-api/openapi/discovery/v1/proprietors?lastName=Smith%2C+Van+Doorn%2C+Ewing-Pistos%2C+O%27Reily&givenName=Mary-Anne&companyName=SERV&pageNumber=1' \
-H 'Authorization: Bearer <YOUR_TOKEN_HERE>' \
-H 'x-correlation-id: 824993ab-7366-4faa-963d-c456dec227a5'Successful Operation
An encrypted title identifier. Access to Vol/Fol is available only for premium discovery due to associated charges. This value is not guaranteed to remain stable over time. Customers should avoid relying on its persistence or consistency across API calls or over extended periods.
For premium discovery responses, this field contains the Volume/Folio (Vol/Fol) of a title.
The status of the title informs whether it is currently active, has become cancelled or partially cancelled.
Describes the ownership type of the title, the main two being Freehold for property owned by individuals and companies, and Crown land which is administered by public authorities.
The parcel(s) associated with the title are described in the Land Description.
{ "proprietorSummaries": [ { … } ], "pagination": { "pageSize": 0, "nextPage": 2 } }
- Mock serverhttps://developer.servictoria.io/_mock/portal/rest/ddp-discovery-api/openapi/discovery/v1/proprietor-names/individual
- Production environmenthttps://api.servictoria.io/ddp/discovery/v1/proprietor-names/individual
- Test environmenthttps://test.api.servictoria.io/ddp/discovery/v1/proprietor-names/individual
- curl
- JavaScript
- Node.js
- Python
- Java
- C#
- PHP
- Go
- Ruby
- R
- Payload
curl -i -X GET \
'https://developer.servictoria.io/_mock/portal/rest/ddp-discovery-api/openapi/discovery/v1/proprietor-names/individual?lastName=Smith&givenName=Mary-Anne' \
-H 'Authorization: Bearer <YOUR_TOKEN_HERE>' \
-H 'x-correlation-id: 824993ab-7366-4faa-963d-c456dec227a5'- Mock serverhttps://developer.servictoria.io/_mock/portal/rest/ddp-discovery-api/openapi/discovery/v1/proprietor-names/company
- Production environmenthttps://api.servictoria.io/ddp/discovery/v1/proprietor-names/company
- Test environmenthttps://test.api.servictoria.io/ddp/discovery/v1/proprietor-names/company
- curl
- JavaScript
- Node.js
- Python
- Java
- C#
- PHP
- Go
- Ruby
- R
- Payload
curl -i -X GET \
'https://developer.servictoria.io/_mock/portal/rest/ddp-discovery-api/openapi/discovery/v1/proprietor-names/company?companyName=SERV' \
-H 'Authorization: Bearer <YOUR_TOKEN_HERE>' \
-H 'x-correlation-id: 824993ab-7366-4faa-963d-c456dec227a5'{ "proprietorNames": [ { … } ] }
- Mock serverhttps://developer.servictoria.io/_mock/portal/rest/ddp-discovery-api/openapi/discovery/v1/parishes
- Production environmenthttps://api.servictoria.io/ddp/discovery/v1/parishes
- Test environmenthttps://test.api.servictoria.io/ddp/discovery/v1/parishes
- curl
- JavaScript
- Node.js
- Python
- Java
- C#
- PHP
- Go
- Ruby
- R
- Payload
curl -i -X GET \
https://developer.servictoria.io/_mock/portal/rest/ddp-discovery-api/openapi/discovery/v1/parishes \
-H 'Authorization: Bearer <YOUR_TOKEN_HERE>' \
-H 'x-correlation-id: 824993ab-7366-4faa-963d-c456dec227a5'{ "parishSummaries": [ { … } ] }
- Mock serverhttps://developer.servictoria.io/_mock/portal/rest/ddp-discovery-api/openapi/discovery/v1/townships
- Production environmenthttps://api.servictoria.io/ddp/discovery/v1/townships
- Test environmenthttps://test.api.servictoria.io/ddp/discovery/v1/townships
- curl
- JavaScript
- Node.js
- Python
- Java
- C#
- PHP
- Go
- Ruby
- R
- Payload
curl -i -X GET \
https://developer.servictoria.io/_mock/portal/rest/ddp-discovery-api/openapi/discovery/v1/townships \
-H 'Authorization: Bearer <YOUR_TOKEN_HERE>' \
-H 'x-correlation-id: 824993ab-7366-4faa-963d-c456dec227a5'{ "townshipSummaries": [ { … } ] }