Copy page

Getting Started

Titles

Domain Concepts

Before using this endpoint it helps to understand the land registry data model. Three concepts are central: parcels, titles, and properties.

Title (Certificate of Title)

A Certificate of Title is the legal record of ownership for a parcel of land. Typically a title covers one parcel, but there are many cases where a title covers multiple parcels: eg. in a consolidated title when the same owner consolidates neighbouring parcels into one administrative record (see AUTO_CONSOL below).

Parcel

A parcel is the fundamental unit of land in a cadastral survey. It is identified by a structured reference consisting of a lot number, an optional section number, and a plan number (for example, Lot 1 in Deposited Plan 123456). Parcels define the physical boundaries of land as recorded in the state land registry.

A single parcel can appear on multiple concurrent titles. This occurs when different ownership interests over the same land are each registered separately: eg. a life estate and the underlying fee simple, or a crown grant alongside the crown allotment.

This means the relationship between titles and parcels is not strictly one-to-one. The API returns title rows, not parcel rows; each result represents one Certificate of Title and includes its associated cadastral context.

Property

A property is a conceptual grouping of one or more addresses and one or more parcels for the purpose of sale.

Code
Address
  └── Property  (one or more addresses, one or more parcels)
        └── Parcel  (cadastre)
              └── Title  (Certificate of Title, one per ownership interest)

A single address lookup resolves through a property to one or more parcels, each of which may have one or more titles. The API returns all matching title rows as a flat list. The query.properties array in every titles response exposes these resolved property records so callers can understand which properties were traversed to find the returned titles.

Address-to-Title Lookup

Each hop in the chain above can be one-to-many. A single query can return multiple title rows for two distinct reasons:

One property, multiple parcels

When resolving an address, the API fetches all land parcels associated with the resolved property. A property that encompasses more than one cadastral parcel (a common occurrence for rural land, lots with separate common-area parcels, or historic consolidations) produces one set of title rows per parcel.

One parcel, multiple titles

More than one Certificate of Title can be registered against the same parcel simultaneously when different ownership interests are recorded separately — for example, a crown grant and a later freehold certificate, or a life estate alongside the underlying fee simple. The API returns all of them.

Example — concurrent interests (one parcel, two titles)

Code
{
  "titles": [
    { "lot": "5", "plan": "PS100001", "type": "FREEHOLD", "id": "abc...", "state": "VIC" },
    { "lot": "5", "plan": "PS100001", "type": "CROWN_GRANT", "id": "xyz...", "state": "VIC" }
  ]
}

Both rows share the same lot/plan but carry distinct id values — use id when passing a title into a downstream purchase flow.

Because the list is flat, use the kind field to group or filter rows — for example, exclude COMMON_PROPERTY rows when showing purchasable lots, or suppress ROAD and RESERVE rows entirely.

Endpoint

GET /api/v0/titles

Resolves one query mode at a time, then returns the matching title rows and the resolved query context.

Query Modes

Mode	Use it for
addressId	Title lookup from an address returned by GET /api/v0/addresses
gnafAddressId	Title lookup by encoded G-NAF address identifier
parcel	State-qualified cadastral lookup using lot/section/plan fields
title	State-qualified direct title lookup

Only one mode can be used per request. If you send more than one, the request is rejected.

addressId

Use addressId when you already have the encoded address identifier returned by GET /api/v0/addresses. This is the simplest path for clients that are chaining a free text address search directly into a title search.

gnafAddressId

Use a G-NAF identifier when you already hold a GNAF Address ID. GNAF (Geocoded National Address File) is Australia's authoritative national geocoded address dataset. Each physical address in GNAF is assigned a stable, unique identifier.

parcel

Use parcel when your workflow starts from a cadastral identifier/title reference rather than a street address. This is common in conveyancing, surveying, and planning workflows where the lot/plan reference is the primary identifier, not the address.

Pass the cadastral components as destructured fields; do not pass a raw provider string:

Field	Required	Description
parcel[state]	Yes	ACT, NSW, NT, QLD, SA, TAS, VIC, or WA
parcel[lot]	Usually	Lot or parcel identifier; not used for ACT
parcel[plan]	Usually	Plan identifier; optional for NT and not used for ACT
parcel[division]	ACT only	ACTLIS division code
parcel[section]	Varies	Required for ACT; optional for NSW and VIC
parcel[block]	ACT only	ACTLIS block number
parcel[location]	NT only	ILIS location code or exact provider location value
parcel[part]	NT only	Optional explicit NT parcel part
parcel[unit]	ACT/NT	Optional explicit legal unit

Parcel identifier types by state

Plan type codes belong in parcel[plan]; they are not separate query parameters. Lot or parcel type codes belong in parcel[lot] only where the state identifier itself requires them. The tables below describe every code that Fynd validates as a closed list and identify states where the registry instead accepts a provider-native code.

Australian Capital Territory (ACT)

ACT parcel mode requires division, section, and block, with an optional legal unit. G-NAF identifiers have the form DISTRICT/DIVISION/SECTION/BLOCK[/UNIT]; the district is contextual and is not submitted to ACTLIS.

Code
GET /api/v0/titles?parcel[state]=ACT&parcel[division]=AMAR&parcel[section]=65&parcel[block]=4

Northern Territory (NT)

NT parcel mode requires an ILIS location code or exact provider location value plus the parcel number. Numeric G-NAF location codes are accepted directly. parcel[plan] is the optional LTO plan; part and unit are sent only when the caller provides them explicitly.

Code
GET /api/v0/titles?parcel[state]=NT&parcel[location]=Town%20of%20Katherine&parcel[lot]=3301

NT G-NAF legal parcels commonly contain a fourth component whose ILIS meaning has not been established. Fynd preserves that source value but never guesses it as parcel[part] or parcel[unit].

New South Wales (NSW)

NSW uses parcel[lot]=<lot number or identifier>, optional parcel[section]=<section>, and parcel[plan]=<plan type><plan number>. The current NSW parser recognizes these plan prefixes:

Prefix	Full name	parcel[plan] example
DP	Deposited Plan	DP221864
SP	Strata Plan	SP5500
CP	Crown Plan	CP1234
AC	Auto Consolidation	AC1234
LF	Lease Folio	LF105

DP is optional for a Deposited Plan: 221864 and DP221864 identify the same plan, and Fynd removes DP before sending the NSW title reference to LRS. LF is accepted as a provider-native slash-reference plan code; it is not one of the plan categories Fynd uses for downstream plan-type classification.

NSW has no separate lot-type prefix field. Send the registry lot identifier unchanged, for example 149, A, or AA. CP in a strata title such as lot CP on plan SP5500 means Common Property and is the lot identifier, not a general lot-type prefix.

Code
GET /api/v0/titles?parcel[state]=NSW&parcel[lot]=149&parcel[plan]=DP221864

Queensland (QLD)

Use parcel[lot]=<lot number> and pass the combined G-NAF plan identifier without a delimiter in parcel[plan], for example RP12345, SP123456, or DW803415.

Prefix	Description
BPA	Building Units Plan of Amalgamation
BRP	Building Units Plan of Resubdivision
BUP	Building Unit Plan
CP	Crown Plan
GRP	Group Titles Plan of Resubdivision
GTA	Group Titles Plan of Amalgamation
GTP	Group Titles Plan
LB	Lower Building Units Plan
MCP	Mixed Community Plan
MPP	Mixed Precinct Plan
MSP	Mixed Stratum Plan Testing
PLP	Plantation Licence Plan
RP	Registered Plan
SBA	Leasehold Building Units Plan of Amalgamation
SBP	Leasehold Building Units Plan
SP	Survey Plan
SPA	Stratum Plan of Amalgamation (South Bank)
SPS	Stratum Plan of Subdivision (Southbank)
SRP	Leasehold Building Units Plan of Resubdivision
SSP	Stratum Plan (Southbank)
UB	Upper Building Units Plan

Fynd splits these supported prefixes from the plan number before calling Titles Queensland.

If the combined identifier has no recognised prefix, Fynd uses CP as the supplier plan type and preserves the entire identifier as the plan number. For example, DW803415 is sent as plan_type=CP and plan_number=DW803415. Numeric-only CP identifiers are also accepted. This fallback does not prove that a title exists; the supplier lookup remains authoritative and may return no current title.

Queensland has no typed lot prefix in this API. parcel[lot] is passed to the provider as lot_number, and parcel[section] is not accepted.

Confirmed-current title results include deduplicated registered proprietor names in preview. Missing or non-current references are excluded from titles and listed in query.warnings. For recognized supplier outcomes, the warning message explains whether the reference was not found, rejected as an invalid registry reference, fully cancelled, comatose, uncaptured, common property, or indefeasible.

Code
GET /api/v0/titles?parcel[state]=QLD&parcel[lot]=1&parcel[plan]=RP12345

South Australia (SA)

SA is the state with closed, explicitly validated plan-type and parcel-type lists. Use ${lotType}/${lotNumber} for parcel[lot] and ${planType}/${planNumber} for parcel[plan]. The / delimiter is required.

Plan types

Prefix	Full name
DP	Deposited Plan
CP	Community Plan
SP	Strata Plan
FP	Filed Plan
HP	Hundred Plan
RP	Road Plan
TP	Township Plan
GRODP	General Registry Office Divison Plan

Lot/parcel types

Prefix	Full name
A	Allotment
ACP	Allotment Comprising Pieces
AR	Allotment (Road)
ACPR	Allotment Comprising Pieces (Road)
AE	Allotment (Reserve)
ACPE	Allotment Comprising Pieces (Reserve)
AT	Allotment (Thoroughfare)
ACPT	Allotment Comprising Pieces (Thoroughfare)
L	Lot
LCP	Lot Comprising Pieces
DL	Development Lot
DLCP	Development Lot Comprising Pieces
CPCP	Common Property (Community Plan)
CPSP	Common Property (Strata Plan)
U	Unit
S	Section
B	Block
TA	Town Acre
CR	Closed Road Marked
P	Piece

For example, Allotment 51 is A/51 and Filed Plan 48540 is FP/48540:

Code
GET /api/v0/titles?parcel[state]=SA&parcel[lot]=A%2F51&parcel[plan]=FP%2F48540

Victoria (VIC)

VIC parcel mode reconstructs a provider Standard Parcel Identifier (SPI) from parcel[lot], optional parcel[section], and parcel[plan]. Fynd does not validate a closed list of Victorian plan or lot-type prefixes; the supplied values must be the provider-native SPI components.

The provider schema documents these plan forms:

Prefix	Full name	parcel[plan] example
PS	Plan of Subdivision	PS328573
TP	Title Plan	TP109554
PP	Parish Plan	PP5762

For an ordinary Lot on Plan, parcel[lot] is the lot number without a type prefix. For example, lot 569 and plan PS434021 become SPI 569\\PS434021. When supplied, parcel[section] is joined with a hyphen, so lot 12, section A, and plan PS434021 become 12-A\\PS434021.

VIC provider responses can classify parcels as LOT, UNIT, COMMON_PROPERTY, ROAD, or RESERVE, but those are response-side parcelType values—not prefixes accepted in parcel[lot]. Crown Allotment SPIs can contain additional provider-native structure (for example 12~10A\\PP5762) that cannot be represented by the current destructured lot/section/plan query fields; use an address-based lookup for those parcels.

Code
GET /api/v0/titles?parcel[state]=VIC&parcel[lot]=569&parcel[plan]=PS434021

Western Australia (WA)

WA parcel mode resolves the supplied parcel[lot] and parcel[plan] to WA G-NAF addresses by exact LEGAL_PARCEL_ID match, then replays the Landgate address-search flow. Supply the plan and lot in the form stored in the WA G-NAF dataset. parcel[section] is not accepted.

Code
GET /api/v0/titles?parcel[state]=WA&parcel[lot]=1&parcel[plan]=SP3244

Tasmania (TAS)

TAS parcel mode uses The LIST's volume/folio convention while keeping the public API fields consistent with other states: parcel[plan] is the volume and parcel[lot] is the folio. Sections are rejected.

Code
GET /api/v0/titles?parcel[state]=TAS&parcel[lot]=1&parcel[plan]=150228

Across most supported parcel states, consumers provide lot and plan fields. ACT instead uses division, section, block, and optional unit. NT requires location and lot, with optional LTO plan, part, and unit. Fynd handles the state-specific composition required by the registry provider.

title

Use title[state] with title[id] for a direct title lookup. Australian Capital Territory expects VOLUME/FOLIO, such as 1579/91; ACTLIS supplies the edition in the result. Northern Territory expects a register book, volume, and folio such as CUFT/886/405; Tasmania and Victoria expect a volume/folio such as TAS 150228/1 or VIC 9674/149; Queensland expects its title reference, for example 15023001; Western Australia expects a Landgate title reference such as 2535/174, 191/197A, or LR3001/10.

---

Response Shape

The response contains two top-level fields:

• titles — an array of title rows. Each row represents one Certificate of Title. See Title Row Fields below.
• query — the resolved query context, described below.

Query Context (query)

The query object tells you which mode was resolved and what search value was used. It also exposes the properties that were traversed during lookup.

Field	Description
query.mode	The resolved lookup mode: gnaf, address, parcel, or title.
query.search	The raw search input that was used.
query.properties	Property records resolved during the lookup. Shape differs by state — see Property above.

Each entry in query.properties contains:

Field	Description
id	State property identifier — GNAF Address ID for ACT/NSW/QLD/TAS, propertyPfi for VIC.
address	Primary address string for this property (eziAddress for VIC, formatted GNAF address for ACT/NSW/QLD/TAS).
aliasAddresses	Additional addresses associated with this property. Present for VIC; QLD includes addresses resolved from title parcels; ACT, NSW, and TAS generally return an empty list.

Title Row Fields

Each row in the titles array represents one Certificate of Title. The stable discovery fields clients should rely on are id, titleReference, lot, section, plan, kind, and description. The raw field contains vendor-native response fragments and is intentionally not normalised.

Field	Description
id	Opaque title identifier used by downstream purchase flows.
address	Human-readable address label for this title row.
description	Human-readable summary built from available cadastral and local government context.
kind	Normalised cross-state classification. See The kind Field.
lot	Lot number.
section	Section number, if applicable.
plan	Plan number.
lga	Local government area.
county	Cadastre county when known.
parish	Cadastre parish when known.
preview	Best-effort title preview lines when the provider exposes them. May be null or empty.
type	Normalised title type (e.g. freehold). May be null.
status	Normalised title status (e.g. active). May be null.
state	State the title belongs to: ACT, NSW, NT, QLD, SA, TAS, VIC, or WA.
raw	Provider-specific detail including the raw vendor response fragment.

---

The kind Field

The kind field is a normalised, cross-state classification applied to every title row. Its purpose is to give client applications a stable semantic label that means the same thing regardless of which state's data is being returned — so that UI behaviour (grouping, iconography, conditional logic) can be implemented once without needing to understand the underlying provider data structures.

Complete kind Reference

Value	Description
STANDARD_LOT	A standard freehold lot identified by lot and plan only, with no section number and no special classification.
SECTIONED_LOT	A lot that includes a section number in addition to lot and plan — common in older subdivisions and rural areas.
STRATA_UNIT	An individually owned unit within a strata plan. The owner holds the unit lot; the common property is held separately.
STRATA_COMMON_PROPERTY	The common property parcel within a strata scheme (NSW). This covers shared areas such as lobbies, driveways, and garden beds.
COMMON_PROPERTY	Common property within a community title or owners corporation scheme (VIC). Functionally equivalent to STRATA_COMMON_PROPERTY in NSW.
COMMUNITY_ASSOCIATION	NSW: Lot 1 in a Deposited Plan within the community title plan number range (DP 270001–279999). Represents the association lot for a community scheme.
PRECINCT_ASSOCIATION	NSW: Lot 1 in a Deposited Plan within the precinct association plan number range (DP 280001–284999).
NEIGHBOURHOOD_ASSOCIATION	NSW: Lot 1 in a Deposited Plan within the neighbourhood association plan number range (DP 285001–299999).
AUTO_CONSOL	An auto-consolidation title: a single Certificate of Title that covers multiple adjacent parcels because they share the same owner. Identified in NSW by a lot or plan number beginning with AC.
CROWN_ALLOTMENT	VIC: A parcel originating from a crown land allotment. Identified by an SPI containing ~ or \PP, or by the presence of an allotment value.
ROAD	VIC: A parcel classified as a road by the provider (parcelType: ROAD).
RESERVE	VIC: A parcel classified as a reserve by the provider (parcelType: RESERVE).
UNKNOWN	The data is valid but could not be confidently classified into any of the above categories. Clients should display these titles but must not apply business logic that depends on kind.

Mapping Logic

The kind value is derived from provider-native metadata using the logic described below. Clients should treat kind as a read-only output — do not attempt to re-derive it from the raw cadastral fields.

New South Wales (NSW)

Pattern / Metadata	Resulting kind
CP/SP... (Common Property lot in a Strata Plan)	STRATA_COMMON_PROPERTY
lot/SP... (Unit lot in a Strata Plan)	STRATA_UNIT
Lot or plan begins with AC	AUTO_CONSOL
lot/section/plan	SECTIONED_LOT
lot/plan	STANDARD_LOT

Plan-based association matching (Lot 1, DP plan number ranges):

Association matching is evaluated before the section/lot fallbacks above. A Lot 1 in a qualifying DP range takes precedence over STANDARD_LOT or SECTIONED_LOT.

DP Plan number range	Resulting kind
270001 – 279999	COMMUNITY_ASSOCIATION
280001 – 284999	PRECINCT_ASSOCIATION
285001 – 299999	NEIGHBOURHOOD_ASSOCIATION

Victoria (VIC)

Provider parcelType	Condition	Resulting kind
COMMON_PROPERTY		COMMON_PROPERTY
ROAD		ROAD
RESERVE		RESERVE
UNIT		STRATA_UNIT
LOT	section present	SECTIONED_LOT
LOT	no section	STANDARD_LOT
(any)	SPI contains ~ or \PP, or allotment value present	CROWN_ALLOTMENT

Western Australia (WA)

All WA title rows return kind: "UNKNOWN". Landgate does not expose a parcel classification that maps to the cross-state kind enum.

All TAS title rows currently return kind: "UNKNOWN". The LIST descriptions are retained as preview data rather than being used to infer a cross-state classification.