API Terms and Conditions

Microburbs Pty Ltd — Last updated 25 August 2026

These are the standard terms for self-serve access to the Microburbs API. If your use case does not fit them — publishing publicly, redistribution, bulk licensing, or anything else below that would otherwise be prohibited — a custom agreement is available. Book a time to discuss it or email [email protected].

The Data must not be published to the open web

You may not display the Data on any publicly accessible website or platform without requiring user authentication, and you may not publish it anywhere it can be indexed by search engines or collected by AI crawlers. Put it behind a login.

You may not resell or redistribute the Data, or make it available to anyone outside your own authenticated users.

You must attribute Microburbs as the source of the Data, visibly, on each page where the Data appears, with a link back to microburbs.com.au.

See Section 2.2, Section 2.3 and Section 6 below for full details.

1. Definitions

In this Agreement, unless the context otherwise requires:

"Agreement" means these Terms and Conditions together with any Schedules, Order Forms, and amendments agreed upon in writing between Microburbs and the Client.
"API" means the Application Programming Interface provided by Microburbs that enables the Client to access and retrieve Property Data and/or Suburb Data.
"API Client" means your website, application or software used or developed by you in relation to which the API is used.
"API Key" means the unique authentication credential issued by Microburbs to the Client for accessing the API.
"Approved Purpose" means the intended use case for the API as agreed upon in writing between Microburbs and the Client.
"Authorised User" means an end user who has created an account with the Client and who has been granted access to the Client's products or services that incorporate the Data.
"Confidential Information" means all information provided by one party to the other in connection with this Agreement that is marked confidential or would normally be considered confidential, including but not limited to the API Key, business plans, customer data, and proprietary algorithms.
"Data" means the Property Data and/or Suburb Data provided through the API.
"Derivative Works" means any modification, adaptation, or transformation of the API or Data that creates a new product or service outside the Approved Purpose.
"Property Data" means data relating to residential and commercial properties, including but not limited to property details, valuations, historical sales data, growth forecasts, and other property-specific metrics.
"Suburb Data" means data relating to suburbs, including but not limited to demographic information, amenities, median prices, growth forecasts, safety ratings, and other suburb-specific metrics.
"Security Incident" means any actual or reasonably suspected unauthorised access, use, disclosure, or breach of the Data or the API.
"Test Data" means the limited set of sample data provided for one suburb and one property to allow the Client to test the API integration.

2. Grant of Licence

2.1. Subject to the terms and conditions of this Agreement, Microburbs grants to the Client a non-exclusive, non-transferable, revocable, limited licence during the Term to:

access and use the API in accordance with the API Documentation;
incorporate the Data into the Client's products or services;
permit Authorised Users to access and use the Data solely through the Client's products or services; and
process, analyse, and present the Data to create property analytics and location insights for Authorised Users, provided that such analytics and insights are only available to Authorised Users and comply with all other restrictions in this Agreement.

2.2. The Client shall not, and shall ensure that its Authorised Users do not:

sublicence, sell, rent, lease, transfer, assign, distribute, or otherwise make available the API or the Data to any third party;
modify, decompile, reverse engineer, disassemble, or create derivative works based on the API or the Data outside the scope of the Approved Purpose;
use the API or the Data in any manner that could damage, disable, overburden, or impair Microburbs' servers or networks;
display the Data on any publicly accessible website or platform without requiring user authentication;
use the Data for lead generation without requiring users to create an account with the Client;
publish the Data in a manner that would compete with Microburbs in search engine results or for search engine optimisation purposes;
pipe, stream, or otherwise redistribute the Data to any third party; or
use the API or the Data for any purpose not expressly permitted by this Agreement.

2.3. Attribution. As a condition of the licence granted in clause 2.1, the Client must:

attribute Microburbs as the source of the Data on each page, screen, or view of the Client's products or services where the Data is displayed;
make that attribution visible to Authorised Users without requiring them to expand, hover over, or navigate away from the content in which the Data appears;
include a hyperlink to microburbs.com.au in that attribution wherever the medium allows a link; and
not remove, obscure, or alter any attribution, copyright, or proprietary notice supplied with the Data.

2.4. A failure to attribute is a breach of this Agreement and may result in suspension or termination of API access under Section 13.

3. Integrations

3.1. The Client agrees that the integration of the API with the Customer Application must adhere to the Approved Purpose.

3.2. The Client is solely responsible for all costs of any development and maintenance work required to integrate the Customer Application with the API and for all costs to modify, alter or develop the Customer Application to enable the Client to comply with the terms of this Agreement.

3.3. Microburbs reserves the right to review the Customer Application and the Client's use of the Data in the context of the Client's obligations under this Agreement, at any time. This is a right of review, not an approval gate: the Client does not need to wait for Microburbs before going live. The Client is asked to let Microburbs know when the integration reaches a live production environment — a public URL, screenshot or screen recording is enough — and to respond to a review request within a reasonable time.

3.5. The Client must incorporate an authenticator token into an integration of the Customer Application with the API to ensure the integration is only made available to Authorised Users.

3.6. The Client must provide and adhere to a privacy policy for its API Client that clearly and accurately describes to Authorised Users what Personal Information the Client collects and how the Client uses and discloses such information.

3.7. The Client must operate (and keep up to date) anti-scraping software on any Customer Application that enables an Authorised User to access any product data via the internet.

4. API Access and Security

4.1. Microburbs will provide the Client with an API Key for accessing the API. The Client shall:

keep the API Key secure and confidential;
not share the API Key with any third party;
use the API Key solely for the purpose of accessing the API in accordance with this Agreement;
implement industry-standard technical and organisational security measures to protect the API Key, including but not limited to encryption, access controls, and secure coding practices;
ensure the API Key is stored securely and not embedded in publicly accessible code; and
notify Microburbs immediately upon becoming aware of any unauthorised use of the API Key.

4.2. The Client is responsible for all activities that occur using its API Key, whether or not such activities are authorised by the Client.

4.3. Microburbs reserves the right to monitor the Client's use of the API to ensure compliance with this Agreement.

4.4. Microburbs may suspend or terminate the Client's access to the API if Microburbs reasonably believes that the Client is in breach of this Agreement or that the Client's use of the API poses a security risk.

4.5. The Client shall:

implement and maintain appropriate technical and organisational security measures to protect any Data received through the API;
comply with all applicable data protection and privacy laws;
conduct regular security assessments of its systems that interface with the API; and
notify Microburbs within 24 hours by email of becoming aware of any Security Incident.

5. User Authentication Requirements

5.1. The Client must require all Authorised Users to create an account and authenticate before accessing any Data through the Customer Application.

5.2. The Data must not be visible on any publicly accessible page. It must be served only behind a login wall.

5.3. API responses must not be served to unauthenticated visitors.

6. Data Usage Restrictions

6.1. Behind a login. Data returned by the API must be displayed only to authenticated users within your application. It cannot appear on public pages that are visible to search engines or to AI crawlers. This is the restriction that matters most to us.

6.2. No redistribution or resale. You may not resell the Data, pipe or stream it to a third party, or otherwise make it available to anyone outside your own authenticated users.

6.3. No competing use. You may not use the Data to build a product that competes with Microburbs or its data services.

6.4. Right to review your use. Where the Data is made available to your users behind a login, Microburbs may ask you to describe or demonstrate how it is being used and displayed, and you agree to respond within a reasonable time.

6.5. Microburbs reserves the right to implement and enforce rate limits, and daily and monthly call caps. Violation of usage limits may result in immediate suspension of API access.

7. Data Updates and Accuracy

7.1. Microburbs updates property data and CMA comparables daily, and core suburb metrics weekly. However, no specific update frequency is guaranteed.

7.2. Microburbs does not warrant that the Data is error-free or complete. The Data is provided "as is" and the Client should verify critical information from authoritative sources before making decisions based on the Data.

7.3. If the Client identifies any data inaccuracies, they may submit a Data Correction Request with supporting evidence for review.

8. Fees and Payment

8.1. The Client shall pay the Fees as specified in their subscription plan. All prices are in AUD and exclude GST unless otherwise stated.

8.2. Fees are billed monthly or annually in advance and are non-refundable except as required by Australian Consumer Law.

8.3. Microburbs reserves the right to modify the Fees upon 30 days' written notice. The Client may terminate the Agreement if they do not accept the new Fees.

8.4. If payment fails, Microburbs may suspend API access until payment is resolved. Access is typically suspended within one hour of payment failure.

9. Test Data Access

9.1. Microburbs provides free Test Data (limited to one suburb and one property) via the sandbox token to allow prospective Clients to evaluate the API before subscribing.

9.2. Test Data is subject to all restrictions in this Agreement. It may not be used in production environments or displayed to end users.

10. Intellectual Property Rights

10.1. All Intellectual Property Rights in the API, the Data, and any documentation remain the exclusive property of Microburbs.

10.2. Nothing in this Agreement transfers ownership of any Intellectual Property Rights to the Client.

10.3. The Client shall not use Microburbs' Brand Features without prior written consent.

11. Monitoring and Audit

11.1. Microburbs reserves the right to monitor all API usage, including request volumes, endpoints accessed, IP addresses, and usage patterns.

11.2. The Client agrees to provide Microburbs with reasonable access to audit the Client's use of the API and the Data upon request.

12. Confidentiality

12.1. Each party agrees to keep the other party's Confidential Information strictly confidential and not to disclose it to any third party without prior written consent.

12.2. Confidential Information includes but is not limited to API Keys, pricing terms, technical specifications, and business strategies.

13. Term and Termination

13.1. This Agreement commences on the Effective Date and continues for the subscription period selected by the Client (the "Initial Term"), automatically renewing for successive periods unless terminated.

13.2. Either party may terminate this Agreement by providing 30 days' written notice.

13.3. Microburbs may terminate this Agreement immediately if the Client breaches any term, particularly any Data Usage Restriction.

13.4. Upon termination, the Client must immediately cease all use of the API and the Data, and delete or destroy all copies of the Data in its possession.

14. Limitation of Liability

14.1. To the maximum extent permitted by law, Microburbs' total liability under this Agreement shall not exceed the total Fees paid by the Client in the 12 months preceding the claim.

14.2. Microburbs shall not be liable for any indirect, consequential, exemplary, incidental, or punitive damages arising from or in connection with this Agreement.

15. General

15.1. This Agreement is governed by and construed in accordance with the laws of New South Wales, Australia.

15.2. Microburbs reserves the right to amend these terms at any time. Changes become effective immediately upon posting. Continued use of the API after changes are posted constitutes acceptance of the new terms.

15.3. If any provision of this Agreement is found to be invalid or unenforceable, the remaining provisions shall remain in full force and effect.

16. Contact Us

If you have questions about these API Terms, please contact us at:

Microburbs Pty Ltd
ACN: 660 243 354
ABN: 11 660 243 354
2/11 York Street, Sydney NSW 2000, Australia
Email: [email protected]

Please also refer to our General Terms of Use, Disclaimer, and Privacy Policy.