Introduction
Fynd API for searching and purchasing Australian property records. It is designed for backend-to-backend integrations that need a predictable workflow for address lookup, title discovery, title search orders, and a range of other property, construction, and conveyancing documents.
Authentication
Every request is authenticated with an API key using the Authorization header:
Code
API keys are issued per API client and scoped to an organisation. If your oraganisation has API Access enabled (contact support@fynd.au for more information), then you can manage your API Keys from Settings.
Requests are rejected if the key is missing, invalid, expired, inactive, or linked to a disabled client or organisation.
Call GET /api/v0/identity first if you want to validate connectivity and confirm which API client is associated with the key you are using.
Code
From within API Reference the API Playground will let you use your logged in session instead of an api key. The identity request here will return null for your api client id.
Quickstart Example
A simple end-to-end workflow for finding an address, discovering available titles, and ordering a title search starts with an address lookup:
Code
Use the returned address id to resolve available titles:
Code
Create a title-search order with the returned title id as titleId:
Code
Depending on x-order-timeout-ms, the create-order request may return the order data immediately or accept the order for asynchronous processing. In either case, poll the order until the document is ready:
Code
API Specification
The API Playground is rendered directly from our OpenAPI spec.
Download the spec at OpenAPI downloads.
