NSW Land Registry Services (NSW LRS) operates the Torrens Title Register for New South Wales, Australia's largest property market, under a concession granted by the NSW Government on 1 July 2017 and held by Australian Registry Investments Pty Ltd (ACN 617 926 020) as trustee for the Australian Registry Investments Trust. It is a privatised operator of a public record: the Registrar General retains the statutory authority and the Office of the Registrar General regulates the concession, while NSW LRS runs the register, examines and registers dealings and plans, and sells access to the resulting data. It sits at the legal foundation of the Australian value chain, beneath the REA Group and Domain portal duopoly, beneath PropTrack and CoreLogic valuation, and beneath PEXA and Sympli, the Electronic Lodgment Network Operators through which every Real Property Act dealing must now be lodged. Its API posture is the sharpest example in this study of a registry that is technically modern and commercially closed. There is no developer portal, no developer or docs subdomain, no published API programme, no OpenAPI or Swagger document, no SDK, no Postman workspace and no GitHub organization. One documented, anonymously callable API does exist, and it is not about land: the NSW LRS status page is an Atlassian Statuspage with the public v2 API enabled and referenced at status.nswlrs.com.au/api, publishing 27 components — among them an "API Service" component under Information Broker Services that confirms from the registry's own mouth that a production API estate sits behind the broker licence — plus RSS and Atom incident feeds and webhook notifications on incident and component changes. Access to the register itself is gated behind a licence: the site states plainly that "Only an information broker we've authorised can access our records", and those brokers — InfoTrack, Dye & Durham, Equifax, CITEC Confirm, TriSearch, Landchecker, Fynd, PSI Global and others — "deliver and on-sell land titling and related property information through an official licence agreement with NSW LRS". Wholesale data products (Property Alerts, Lease Notifications, Mortgage Insights, Mortgage Verifications) are sold by emailing datasolutions@nswlrs.com.au, with no self-serve path and no published technical contract. What does exist, and what this profile records, are three genuinely reachable machine-readable surfaces that NSW LRS never advertises to developers: a Cantaloupe IIIF Image API 2.0 Level 2 endpoint serving the scanned historical land records behind the Historical Land Records Viewer, an anonymously callable Elasticsearch search proxy over 7,160,622 indexed historical documents, and a publicly downloadable W3C XML Schema for the ICSM ePlan Cadastral Information File enumerated types that pins the NSW LandXML jurisdictional vocabulary now mandatory for digital plan lodgment. The contracts are open; the licence is not — the HLRV terms of use prohibit on-supply, data aggregation, republishing and "any device, software or routine to abuse the service of HLRV or emulate human interaction and operation". RESO is entirely absent: NSW LRS appears nowhere in RESO's certified-organizations list, there is no RESO Web API or Data Dictionary certification, no OData $metadata document and no Universal Property Identifier, which is the expected answer for Australia, where RESO is a North American NAR construct with no adoption. No open, unlicensed dataset is published — NSW LRS is not a publishing organization on data.nsw.gov.au — and a privatised registry selling the public record back through a licensed broker channel is itself the finding. The registry does publish its language: a 257-term glossary of NSW land titling definitions, harvested here as the controlled vocabulary that stands in for the data dictionary it never wrote.
NSW Land Registry Services is listed with 3 APIs on the APIs.io network. Tagged areas include Real Estate, Australia, Land Registry, Title, and Conveyancing.
The NSW Land Registry Services catalog on APIs.io includes 1 event-driven AsyncAPI specification.
NSW Land Registry Services’ developer surface includes authentication, changelog, code examples, engineering blog, documentation, developer portal, pricing, and 29 more developer resources.
Regulatory Posture applies to this provider. Its tags matched the
Government & Public Sector regime, so
Regulatory Posture carries 15 points of the composite.
If this regime is wrong for your business, say so on your
provider repo — the
applicability map is public and we will correct it.
Create-or-Update Ergonomics could not be measured. We hold no machine-readable contract for
this provider to read, so there is nothing to measure a write surface against. Excluded rather than scored zero:
never-measured and measured-empty are different facts. Publishing an OpenAPI is what makes this facet — and
several others — scorable at all.
The six quality facets above are damped to 85 points between them,
because the conditional facet above carries the other
15. That is why each facet's contribution is shown against a damped
maximum: raising a quality facet moves the composite by 85% of its nominal
weight, not 100%. The full arithmetic is at apis.io/rating/.
Show this score on your site.
It updates itself when the score changes. Paste this where you link to your API docs:
<a href="https://apis.io/providers/nsw-land-registry/"><img src="https://apis.io/badge/nsw-land-registry/card.svg" alt="NSW Land Registry Services on APIs.io — Kin Score by API Evangelist"></a>
Other styles, a README pill and a shields.io endpoint are on the badge page.
Raise your score.
Agent readiness — checks not met, largest first (exact, from this profile):
MCP Server+12 pts — deployment.mode + probe verdict on the mcp/ manifest, not the pointer; an unprobed slug falls back to authorship
Idempotency+9 pts — OpenAPI mutating operations declare an idempotency key — a header, a request-body property, or a named de-duplication token whose own description says so (verified); else common[].type matches /idempoten/i (documented)
A2A Agent Card+8 pts — a2a/-a2a.yml manifest, graded on conformance.grade against A2A 1.0.0
Rate-Limit Signaling+7 pts — OpenAPI responses document X-RateLimit-* / RateLimit headers (verified), else a rate_limits artifact or RateLimits link (documented)
A live Cantaloupe Image Server exposing the International Image Interoperability Framework (IIIF) Image API 2.x over the scanned NSW land record images behind the Historical Lan...
An Elasticsearch search proxy that backs the Historical Land Records Viewer and answers anonymously. Verified on 2026-07-26: POST https://api.lrsnative.com.au/hlrv/documents/_ms...
The one documented, publicly callable API NSW Land Registry Services operates. The NSW LRS status page at status.nswlrs.com.au is an Atlassian Statuspage (page id jcfp2nmyt2j4) ...
aid: nsw-land-registry
url: https://raw.githubusercontent.com/api-evangelist/nsw-land-registry/refs/heads/main/apis.yml
name: NSW Land Registry Services
kind: company
description: 'NSW Land Registry Services (NSW LRS) operates the Torrens Title Register for New South Wales, Australia''s largest
property market, under a concession granted by the NSW Government on 1 July 2017 and held by Australian Registry Investments
Pty Ltd (ACN 617 926 020) as trustee for the Australian Registry Investments Trust. It is a privatised operator of a public
record: the Registrar General retains the statutory authority and the Office of the Registrar General regulates the concession,
while NSW LRS runs the register, examines and registers dealings and plans, and sells access to the resulting data. It sits
at the legal foundation of the Australian value chain, beneath the REA Group and Domain portal duopoly, beneath PropTrack
and CoreLogic valuation, and beneath PEXA and Sympli, the Electronic Lodgment Network Operators through which every Real
Property Act dealing must now be lodged. Its API posture is the sharpest example in this study of a registry that is technically
modern and commercially closed. There is no developer portal, no developer or docs subdomain, no published API programme,
no OpenAPI or Swagger document, no SDK, no Postman workspace and no GitHub organization. One documented, anonymously callable
API does exist, and it is not about land: the NSW LRS status page is an Atlassian Statuspage with the public v2 API enabled
and referenced at status.nswlrs.com.au/api, publishing 27 components — among them an "API Service" component under Information
Broker Services that confirms from the registry''s own mouth that a production API estate sits behind the broker licence
— plus RSS and Atom incident feeds and webhook notifications on incident and component changes. Access to the register itself
is gated behind a licence: the site states plainly that "Only an information broker we''ve authorised can access our records",
and those brokers — InfoTrack, Dye & Durham, Equifax, CITEC Confirm, TriSearch, Landchecker, Fynd, PSI Global and others
— "deliver and on-sell land titling and related property information through an official licence agreement with NSW LRS".
Wholesale data products (Property Alerts, Lease Notifications, Mortgage Insights, Mortgage Verifications) are sold by emailing
datasolutions@nswlrs.com.au, with no self-serve path and no published technical contract. What does exist, and what this
profile records, are three genuinely reachable machine-readable surfaces that NSW LRS never advertises to developers: a
Cantaloupe IIIF Image API 2.0 Level 2 endpoint serving the scanned historical land records behind the Historical Land Records
Viewer, an anonymously callable Elasticsearch search proxy over 7,160,622 indexed historical documents, and a publicly downloadable
W3C XML Schema for the ICSM ePlan Cadastral Information File enumerated types that pins the NSW LandXML jurisdictional vocabulary
now mandatory for digital plan lodgment. The contracts are open; the licence is not — the HLRV terms of use prohibit on-supply,
data aggregation, republishing and "any device, software or routine to abuse the service of HLRV or emulate human interaction
and operation". RESO is entirely absent: NSW LRS appears nowhere in RESO''s certified-organizations list, there is no RESO
Web API or Data Dictionary certification, no OData $metadata document and no Universal Property Identifier, which is the
expected answer for Australia, where RESO is a North American NAR construct with no adoption. No open, unlicensed dataset
is published — NSW LRS is not a publishing organization on data.nsw.gov.au — and a privatised registry selling the public
record back through a licensed broker channel is itself the finding. The registry does publish its language: a 257-term
glossary of NSW land titling definitions, harvested here as the controlled vocabulary that stands in for the data dictionary
it never wrote.'
deliveryModel:
model: saas
open_source: false
commercial: true
callable_host: false
label: Hosted service · you call their endpoint
confidence: medium
source:
- pricing
generated: '2026-08-28'
method: derived
accessModel:
pricing: unknown
onboarding: unknown
trial: false
try_now: false
public: false
label: Unknown
confidence: low
source:
- authentication
- security
generated: '2026-11-06'
method: derived
image: https://nswlrs.com.au/assets/f/1129775276948026/1a96a055c4/new_nsw-lrs-logo_colour.png
tags:
- Real Estate
- Australia
- Land Registry
- Title
- Conveyancing
- Property Records
- Torrens Title
- eConveyancing
- Government
- Geospatial
- PropTech
tags_raw:
- Real Estate
- Australia
- Land Registry
- Title
- Conveyancing
- Property Records
- Torrens Title
- eConveyancing
- Government
- Geospatial
- PropTech
- Real-Estate
created: '2026-07-26'
modified: '2026-07-26'
specificationVersion: '0.23'
apis:
- aid: nsw-land-registry:nsw-lrs-hlrv-iiif-image-api
name: NSW LRS Historical Land Records Viewer IIIF Image API
description: 'A live Cantaloupe Image Server exposing the International Image Interoperability Framework (IIIF) Image API
2.x over the scanned NSW land record images behind the Historical Land Records Viewer. Verified anonymously on 2026-07-26:
the endpoint root returned HTTP 200 with the Cantaloupe "IIIF Image API 2.x Endpoint" documentation page advertising the
sample patterns /{identifier}/info.json and /{identifier}/full/full/0/default.jpg, an image information document for identifier
eirOSD%2F0938-0939%2F0939_0937_0001.jp2 returned HTTP 200 with Content-Type application/json declaring compliance profile
http://iiif.io/api/image/2/level2.json, and a derivative render at /full/200,/0/default.jpg returned HTTP 200 with Content-Type
image/jpeg and 16,798 bytes. The saved info.json is the machine-readable contract: it declares @context http://iiif.io/api/image/2/context.json,
protocol http://iiif.io/api/image, the source dimensions, six pyramid sizes, tile geometry, the formats jpg/tif/gif/png,
the qualities bitonal/default/gray/ color and the full Level 2 feature list including cors, regionByPx, sizeByPct, rotationArbitrary
and profileLinkHeader. Identifiers are constructed by the HLRV client as URL-encoded location + "/" + fileName over JPEG2000
masters. NSW LRS publishes no documentation for this endpoint, no OpenAPI, no key issuance and no rate-limit statement;
it is an undocumented backend of a free public viewer, and the HLRV terms of use expressly prohibit scripted or emulated
access.'
humanURL: https://hlrv.nswlrs.com.au/
baseURL: https://api.lrsnative.com.au/hlrv/iiif/2
tags:
- Land Registry
- Historical Records
- IIIF
- Image
- Australia
tags_raw:
- Land Registry
- Historical Records
- IIIF
- Images
- Australia
properties:
- type: Schema
url: openapi/nsw-land-registry-hlrv-iiif-image-information.json
- type: Documentation
url: https://hlrv.nswlrs.com.au/
- type: Documentation
url: https://nswlrs.com.au/services/record-searches/historical-research
- type: Standard
url: https://iiif.io/api/image/2.1/
- type: TermsOfService
url: https://nswlrs.com.au/about-us/policies/terms-conditions
- aid: nsw-land-registry:nsw-lrs-hlrv-document-search-api
name: NSW LRS Historical Land Records Viewer Document Search API
description: 'An Elasticsearch search proxy that backs the Historical Land Records Viewer and answers anonymously. Verified
on 2026-07-26: POST https://api.lrsnative.com.au/hlrv/documents/_msearch with an ndjson body of {"preference":"probe"}
plus {"query":{"match_all":{}},"size":2} returned HTTP 200 with Content-Type application/json and hits.total 7160622 across
three shards, with no credential of any kind supplied. The HLRV single-page app configures the ReactiveSearch client with
ELASTIC_SEARCH_HOST https://api.lrsnative.com.au, INDEX_NAME hlrv/documents and an x-portal-token header, but that header
is not enforced on _msearch. Returned documents carry collectionId, collectionName (for example "General Register of Deeds
(Old System Deeds)"), documentId, documentRenderingId, imageType, imageName, bookAndNumber, scanTimestamp and an images
array of JPEG2000 files with fileName, location, imageId, imageStatus, seqNo and pixel dimensions — the exact fields needed
to build IIIF identifiers. Sibling routes are not open: GET /hlrv/documents returned HTTP 503, POST /hlrv/documents/_search
returned HTTP 400 with {"message":"Invalid Request: TypeError: query.includes is not a function"}, and POST /hlrv/lotsearch/search
returned HTTP 500. There is no published contract, no documentation, no versioning and no terms permitting programmatic
use; HLRV clause 3.6 prohibits using "any device, software or routine to abuse the service of HLRV or emulate human interaction
and operation" and clause 2.1 prohibits on-supply, republishing and data aggregation. Recorded here as an observed, reachable
surface, not as an offered developer product.'
humanURL: https://hlrv.nswlrs.com.au/
baseURL: https://api.lrsnative.com.au/hlrv/documents
tags:
- Land Registry
- Historical Records
- Search
- Elasticsearch
- Australia
properties:
- type: Documentation
url: https://hlrv.nswlrs.com.au/
- type: Documentation
url: https://nswlrs.com.au/services/record-searches/how-to-find-a-record
- type: TermsOfService
url: https://nswlrs.com.au/about-us/policies/terms-conditions
- type: Examples
url: examples/nsw-land-registry-hlrv-msearch-response.json
- aid: nsw-land-registry:nsw-lrs-status-api
name: NSW LRS Status API
description: 'The one documented, publicly callable API NSW Land Registry Services operates. The NSW LRS status page at
status.nswlrs.com.au is an Atlassian Statuspage (page id jcfp2nmyt2j4) with the public v2 API enabled and a published
endpoint reference at https://status.nswlrs.com.au/api, which documents each route with plain curl examples and a JavaScript
widget wrapper. Verified anonymously on 2026-07-26: /api/v2/status.json returned HTTP 200 with indicator "none" and description
"All Systems Operational"; /api/v2/summary.json returned 12,844 bytes; /api/v2/components.json returned 9,376 bytes describing
27 components and component groups; /api/v2/incidents.json returned 163,325 bytes covering 50 incidents; /api/v2/scheduled-maintenances.json
returned 366,516 bytes; and the unresolved and upcoming convenience routes both answered 200. Incident history is also
published as RSS 2.0 and Atom 1.0 feeds, and the page offers email, SMS and webhook subscriptions, the webhook fired whenever
NSW LRS creates, updates or resolves an incident or changes a component status. The component list doubles as the closest
public inventory of NSW LRS production systems — Secure Web Services, VPN, eConveyancing Services, NSW LRS Connect, Secure
File Transfer, Information Broker Services with its own "API Service" child component, ITS Services, Document Delivery
Services (DeX), RG Directions Website, Secure Upload Portal, DIIMS Services, Addressing Services, eCommerce, Portal Access,
Cadastral Records Enquiry, HLRV, NOS Enquiry and Street Address searches. It confirms from the registry''s own mouth that
a production API service exists behind the broker licence, even though nothing about that API is published. No authentication,
no key issuance and no rate limit is documented; the contract is Atlassian''s, not NSW LRS''s.'
humanURL: https://status.nswlrs.com.au/
baseURL: https://status.nswlrs.com.au/api/v2
tags:
- Status
- Incidents
- Land Registry
- Australia
tags_raw:
- Status
- Operations
- Incidents
- Land Registry
- Australia
properties:
- type: APIReference
url: https://status.nswlrs.com.au/api
- type: Documentation
url: https://status.nswlrs.com.au/api
- type: StatusPage
url: https://status.nswlrs.com.au/
- type: Webhooks
url: asyncapi/nsw-land-registry-status-webhooks.yml
- type: Examples
url: examples/_index.yml
- type: RSS
url: https://status.nswlrs.com.au/history.rss
- type: Atom
url: https://status.nswlrs.com.au/history.atom
common:
- type: DomainSecurity
url: security/nsw-land-registry-domain-security.yml
- type: Authentication
url: authentication/nsw-land-registry-authentication.yml
- type: Conventions
url: conventions/nsw-land-registry-conventions.yml
- type: Conformance
url: conformance/nsw-land-registry-conformance.yml
- type: ErrorCatalog
url: errors/nsw-land-registry-problem-types.yml
- type: Lifecycle
url: lifecycle/nsw-land-registry-lifecycle.yml
- type: ChangeLog
url: changelog/nsw-land-registry-changelog.yml
- type: ChangeLog
url: https://nswlrs.com.au/about-us/education-hub/lrs-connect-release-schedule
- type: Vocabulary
url: vocabulary/nsw-land-registry-glossary.yml
- type: DataModel
url: data-model/nsw-land-registry-data-model.yml
- type: Webhooks
url: asyncapi/nsw-land-registry-status-webhooks.yml
- type: Examples
url: examples/_index.yml
- type: LLMsTxt
url: llms/nsw-land-registry-llms.txt
- type: Blog
url: https://nswlrs.com.au/about-us/announcements
- type: Login
url: https://connect.nswlrs.com.au/
- type: Documentation
url: https://nswlrs.com.au/glossary-of-terms
- type: Documentation
url: https://nswlrs.com.au/current-processing-times
- type: Documentation
url: https://nswlrs.com.au/forms-guides/guides
- type: Documentation
url: https://nswlrs.com.au/about-us/education-hub
- type: Website
url: https://nswlrs.com.au/
- type: Documentation
url: https://nswlrs.com.au/services
- type: XSD
url: openapi/nsw-land-registry-eplan-cif-enumerated-types-4-0.xsd
- type: Standard
url: https://nswlrs.com.au/services/plans/digital-plans
- type: Portal
url: https://connect.nswlrs.com.au/
- type: Portal
url: https://online.nswlrs.com.au/
- type: Portal
url: https://hlrv.nswlrs.com.au/
- type: StatusPage
url: https://status.nswlrs.com.au/
- type: Pricing
url: https://nswlrs.com.au/services/fees-payments/fees
- type: TermsOfService
url: https://nswlrs.com.au/about-us/policies/terms-conditions
- type: PrivacyPolicy
url: https://nswlrs.com.au/about-us/policies/privacy-policy
- type: Copyright
url: https://nswlrs.com.au/copyright
- type: Support
url: https://nswlrs.com.au/about-us/contact-us
- type: Documentation
url: https://nswlrs.com.au/services/record-searches/how-to-find-an-information-broker
- type: Documentation
url: https://nswlrs.com.au/data-solutions
- type: Documentation
url: https://www.registrargeneral.nsw.gov.au/property-and-conveyancing/eConveyancing
- type: LinkedIn
url: https://www.linkedin.com/company/nsw-land-registry-services/
maintainers:
- FN: Kin Lane
email: kin@apievangelist.com
NSW Land Registry Services API — frequently asked questions
Does NSW Land Registry Services have an API?
Yes. APIs.io lists 3 APIs from NSW Land Registry Services, including NSW LRS Historical Land Records Viewer IIIF Image API, NSW LRS Historical Land Records Viewer Document Search API and NSW LRS Status API.
How do I authenticate with the NSW Land Registry Services API?
NSW Land Registry Services uses bearer-token authentication (none/contract-gated/session-login · 6 schemes). The details are profiled on APIs.io as Nsw Land Registry Authentication.
Is the NSW Land Registry Services API ready for AI agents?
NSW Land Registry Services has a Kin Score of 46.9 out of 100 (developing) and an Agent Readiness score of 23.9 (agent-aware), scored by API Evangelist on 2026-11-06.
Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.
Get an API key
Free tier, no form to fill in. Signing in shares your email address with us — we
store it to create your key and to recognise you if you sign in with another
provider. See our Privacy Policy and
Terms.