Do not scrape Domain.com.au directly. Domain’s Conditions of Use prohibit scraping, indexing, and automated data gathering, and also prohibit using the site to build a competing property database. For a permitted use, start with Domain’s official Developer API or a licensed data product, confirm that your intended purpose and fields are approved, and follow the relevant licence terms.
Why direct scraping is not the right route
Domain’s Conditions of Use prohibit directly or indirectly scraping or indexing the site, including deploying data-mining tools, robots, or similar methods to gather and extract information. They also prohibit using the product to build a property-information database, a derivative product, or something that competes with Domain or its products.
That means changing the tool does not make an otherwise prohibited collection method acceptable. A browser automation script, headless browser, parser, or screenshot-based workflow used to collect Domain property information would still be an indirect way of gathering data. Do not treat a page being publicly viewable as permission to harvest its contents.
If your requirement is Australian property data, distinguish the desired outcome from the method: identify the fields and use case first, then seek access to an authorised source with terms that cover them. Domain’s Developer API and its licensed products are the relevant Domain routes described here.
#1 Best Overall
Compare the Domain routes before building
| Route | What it is suited to | What to verify |
|---|---|---|
| Direct website scraping | Not an appropriate route for collecting Domain property data under the stated Conditions of Use. | The terms prohibit scraping, indexing, data-mining robots, and building a competing property database. |
| Domain Developer API | Approved integrations needing data from documented Domain packages. | Approved purpose, package coverage, API agreement, call limits, privacy duties, credential handling, and any re-publication rules. |
| Domain Data Extract | Use cases involving customer-supplied property data where the customer has lawful provenance and the required rights and consents. | Rights to disclose the data, required consents and disclosures, and a prior, continuing relationship with the relevant properties or individuals. |
The available API packages are described as covering agencies and listings, properties and locations, property enrichment, comprehensive property packages, PropertyRadar, rental estimates, schools data, and webhooks. The exact fields, access conditions, and call limits depend on the applicable package and agreement; confirm them in Domain’s Developer Platform rather than assuming a package contains a particular field.
Plan an API integration in six steps
- Write down the approved purpose. State who will use the data, what the integration will do, and whether information will be shown to users, stored, or sent to another system. The API licence is limited to the approved purpose, so a vague request makes it harder to choose the right package and assess the planned use.
- Specify only the fields you need. Separate essential fields from optional ones and map each to a documented package or endpoint in the Developer Platform. Do not infer that a web page field is available through the API, or that API access grants permission to collect other page content.
- Create a developer project and select the smallest suitable package. Domain’s portal workflow is to create an account and project, choose packages, and explore the Live API Browser or sandbox. Confirm package terms and any call limits before implementing production traffic.
- Authenticate on a trusted server. Keep credentials out of browser code, public repositories, logs, and client-side applications. Restrict who can read the secret, rotate it under your organisation’s process, and use only the access granted for your project.
- Test the documented request shape. Use the Live API Browser or sandbox to inspect the current request and response for the package you selected. Generate code from the currently documented endpoint and authentication method; do not copy an endpoint, parameter, or token format from an unrelated example.
- Review the agreement before launch. Check that the actual product behaviour stays within the approved purpose and that the people responsible for privacy, storage, publication, and deletion understand the API terms.
Build safeguards around the documented API
The following are implementation practices, not additional Domain endpoint guarantees. Apply them around the specific API behaviour and limits stated in your agreement and current documentation.
Pagination and call limits
Follow the pagination fields documented for the selected endpoint. Keep a per-job record of the page or cursor processed, and stop when the API indicates there is no next page. Enforce your approved call limits in your own client: reserve capacity for retries and operational tasks, and avoid launching unbounded parallel requests. If the documented response indicates a limit has been reached, pause and resume according to the API’s documented behaviour rather than repeatedly retrying.
Rank #2
Retries, timeouts, and partial runs
Set a finite request timeout. For transient failures, use bounded retries with increasing delays and random jitter; do not retry a permanent validation or permission error as if it were temporary. Persist progress so a failed run can resume without reprocessing every record. Record the response status and enough context to diagnose the failure, but redact credentials and unnecessary personal information from logs.
Do these 3 things before closing this tab:
1Scan for outdated or missing drivers - takes under a minute2Repair Windows errors before they cause bigger problems3Fix the driver behind crashes, sound loss and screen glitchesCaching and deduplication
Cache responses only as allowed by the agreement and for a retention period your use case is authorised to keep. Use stable identifiers documented by the API for deduplication; do not assume an address is a unique or permanent key. Store the source identifier and retrieval time with each record so that downstream systems can distinguish a newly retrieved value from an old copy.
Schema validation and change management
Validate responses against the documented schema before storing or publishing them. Treat absent, null, and changed fields as distinct cases where the API schema permits them. Keep a versioned mapping from API fields to your internal model, and re-check the documentation and terms when the API version, package, or product schedule changes.
Store provenance and retention decisions with the data
For every stored record, keep enough metadata to answer where it came from, when it was retrieved, under which approved purpose and package it was accessed, and what retention or deletion decision applies. Keep consent and licence information linked to records when relevant. This helps your team identify data that must be corrected, removed, or excluded from a particular use.
Domain’s API terms describe a limited, non-exclusive, non-transferable, non-sub-licensable licence during the agreement term, for use only in accordance with the approved purpose and agreement. They require reasonable use, secure credentials, compliance with privacy legislation, and compliance with call limits. They also prohibit re-identification, unauthorised third-party access, derivative works, and direct marketing. Do not assume that access for one integration permits a second purpose, onward sharing, or a new product; get confirmation under the applicable agreement.
What changes if you re-publish listing data?
Displaying data from an API is not automatically the same as having permission to republish it in any form. Where listing data is re-advertised, Domain requires property-detail pages to be no-indexed with major search providers, attribution such as “Powered by Domain Insight” where applicable, and listing-engagement events to be sent back through the Developer Platform.
- Confirm that the agreement covers the specific form of display and audience.
- Apply the stated no-index requirement to property-detail pages where it applies.
- Use the required attribution where applicable.
- Send listing-engagement events through the Developer Platform as required.
- Do not silently copy images, descriptions, or other listing content into a competing database.
For Domain Data Extract, the rules are different from simply requesting API access: customer data must have been obtained directly and lawfully; the customer must hold the rights and authorisations to disclose it and have obtained relevant consents and disclosures; and there must be a prior, continuing relationship with the properties or individuals in the supplied data. If you cannot establish those conditions, do not treat an extract as a workaround for website scraping.
Or skip the browser setup
ScreenshotNeo is a screenshot API and MCP server, not a Domain property-data API. It does not authorise collecting Domain listings or bypass Domain’s terms, so do not use it to extract property data. For sites and captures you are permitted to make, one GET request can return an image or PDF; the API documentation is at ScreenshotNeo docs.
curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://stripe.com -o shot.webpFor permitted captures, ScreenshotNeo accepts cookie or consent banners and removes more than 60 known consent platforms, newsletter popups, and chat widgets before capture; each step can be turned off. Bot checks, blank pages, timeouts, failed loads, and cache hits are not billed, and responses identify the page verdict and billing status. Its MCP server offers the tools take_screenshot, get_page_info, and capture_pdf for AI agents and MCP clients. The free plan includes 1,000 shots per month without a card; paid plans start at $5 for 3,000 shots. Sign up for 1,000 free screenshots a month, with no card required.
The Tool Desk
Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Troubleshoot common integration problems
The API request is rejected
Check that the project has access to the relevant package, the credential is being sent in the documented way, and the requested purpose and endpoint are covered by the agreement. Use the current Live API Browser or sandbox output to compare the request with the documented example. Do not try to work around an access denial by switching to automated page collection.
The response lacks a field you expected
Confirm that the field is included in the package and endpoint you selected. A field visible on a website is not proof that the API returns it or that you may use it for your purpose. Ask Domain about package coverage or an appropriate licensed product before changing your collection method.
A job is failing partway through
Inspect the documented error response and your own logs, then distinguish transient failures from validation, permission, or limit errors. Resume from saved pagination state after a transient interruption; correct the request or obtain the required access for a permanent failure. Keep retries bounded so a failing integration does not consume calls indefinitely.
Your use case has changed
Pause the affected processing and compare the new use with the approved purpose, retention, and disclosure terms. A change from internal analysis to public listing display, for example, can introduce different obligations. Confirm the change with Domain before expanding access or reusing existing data.
Recommended Free Tools
Practical conclusion
For Domain property information, replace direct scraping with an authorised data route. The Developer API is the starting point for a documented integration; Data Extract has specific provenance, consent, and relationship conditions. Choose by approved purpose and package coverage, then build around the licence rather than treating website content as unrestricted input.
Frequently Asked Questions
Does a publicly accessible Domain listing mean I can collect its contents?
No. Public visibility is not permission to scrape, index, or harvest the listing under Domain’s stated Conditions of Use.
Can I use Domain API data for a different project later?
Do not assume so. API use is licensed for the approved purpose; confirm the new use and any required access with Domain.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
