API Terms and Conditions of Use

These Terms and Conditions of Use (Terms) govern access to and use of the Suburb Data application programming interface (API) provided by Suburb Data Pty Limited (ABN 96 665 109 017) of Suite 24B, Level 2, 1 Maitland Place, Norwest NSW 2153 (Suburb Data, we, us).

By generating an API Key, calling any endpoint, or crediting an account for API use, you (you, the Client) accept these Terms and agree to be bound by them. If you are accepting on behalf of an organisation, you warrant that you are authorised to bind that organisation, and "you" means that organisation.

These Terms apply in addition to the Suburb Data Platform Terms of Service (https://suburbdata.com.au/terms-and-conditions) and Privacy Policy (https://suburbdata.com.au/privacy-policy). Where there is an inconsistency in relation to API use, these Terms prevail.

API means the Suburb Data application programming interface, including all endpoints, and any successor or replacement interface.

API Key means the credential issued to you through the Suburb Data platform for authenticating API requests.

Client Application means the website, application, product, service or internal system operated by you through which the Data is used or presented.

Credit means the prepaid balance held against your account and applied to Data Charges and Fees.

Data means all information returned by the API, including Metric Values, Reference Data, search results, scores, rankings, forecasts and derived indicators.

Data Charge means the per-request amount debited from your Credit for a request for Live Data, as quoted by the Suburb Data platform.

Data Month means the monthly data release period, which commences when a new data release is published (usually on or about the 6th day of each calendar month).

Delivered Document has the meaning given in clause 4.4.

End User means a natural person who accesses Output through your Client Application.

Fees means the Account Enablement Fee, the Compliance Check Fee and any other fee described in Schedule 1.

Live Data means real Data returned in live mode, for which Data Charges apply.

Metric Values means the values returned for a metric, market and month combination, including values returned in search results and historical series.

Output means the reports, screens, charts, files or other materials you present to End Users that contain or are derived from the Data.

Reference Data means the lists of available months, markets, market types, property types and metrics (including metric names and codes) returned by the API's lookup endpoints.

Scoring IP means Suburb Data's proprietary scoring, ranking, forecasting and demand/supply methodologies, including the DSR family of scores, together with the models, weightings, formulae and source-data selection underlying them.

Trial Data means mock, non-genuine sample data returned in trial mode at no Data Charge.

2.1 API access requires an active Suburb Data platform account in good standing. You must generate your API Key through the platform and must tell us, accurately, what you intend to use the API for.

2.2 We may decline, defer or revoke API access at our discretion, including where the intended use is inconsistent with these Terms.

2.3 You must maintain a monitored email address on the account. Notices we send to that address are taken to be received.

2.4 You must:

(a) keep the API Key confidential and not disclose it to any third party;

(b) not embed the API Key in client-side code, mobile applications, public repositories or anything else accessible to an End User or the public;

(c) call the API only from server-side systems under your control;

(d) rotate the API Key promptly on our request; and

(e) notify us within 24 hours of becoming aware of any actual or suspected compromise or unauthorised use of the API Key.

2.5 You are responsible for all activity conducted using your API Key and for all Data Charges and Fees incurred through it, whether or not you authorised the activity.

3.1 Subject to your compliance with these Terms and payment of all Data Charges and Fees, we grant you a non-exclusive, non-transferable, non-sublicensable, revocable licence for the term of these Terms to:

(a) call the API in accordance with the technical documentation;

(b) process and analyse the Data within your Client Application; and

(c) present Output incorporating the Data to End Users of your Client Application.

3.2 The licence is limited to your own Client Application and your own business. It does not extend to related bodies corporate, resellers, agencies acting for you, or any other party, unless we agree in writing.

3.3 All rights not expressly granted are reserved. Nothing in these Terms transfers ownership of the API, the Data, the Reference Data or the Scoring IP.

4.1 You may present Output to End Users, including in reports, dashboards, charts and documents generated by your Client Application.

4.2 Authenticated access, and approved public display. Output must only be made available to End Users who have created an account with you and authenticated before accessing it, unless we have expressly approved that category of Output for public display. Any publicly displayed Output must comply with any conditions we specify, including attribution, linking and limits on the Data shown.

4.3 Any Output not expressly approved for public display must not be made available on a publicly accessible page, and must be excluded from search engine indexing.

4.4 Delivered Documents. Despite clauses 4.2 and 4.3, you may provide a static, point-in-time document (such as a PDF suburb report) containing Output to a named client of your business (a Delivered Document), provided that the Delivered Document:

(a) is generated by your Client Application from a request you have paid for;

(b) carries the attribution required by clause 4.7 and the disclaimer required by clause 10.4;

(c) states the Data Month to which the Data relates;

(d) is provided to an identified individual client, and not published, posted openly, or distributed to a list, mailing group or the public; and

(e) is not provided in a machine-readable, tabular or bulk format (including CSV, JSON, XLSX or an equivalent), and is not accompanied by any export of the underlying values.

4.5 Except to the extent we have approved public display under clause 4.2, you must not present Output in a way that:

(a) is designed principally to attract search engine traffic, or that competes with Suburb Data in search engine results;

(b) makes the Data freely available to the public without authentication;

(c) allows the Data to be extracted, exported or downloaded in bulk or in a machine-readable form by an End User; or

(d) is the substantive equivalent of the Suburb Data platform itself — that is, a general-purpose suburb research or suburb search tool offered to the market.

Paragraphs (c) and (d) apply whether or not we have approved public display.

4.6 You must not alter Metric Values, or present Data in a way that misrepresents what it measures, how current it is, or its source.

4.7 Attribution. You must display the attribution "Powered by Suburb Data" (or such other attribution as we specify from time to time) on every screen and in every document containing Output. The attribution must be:

(a) legible, and no less prominent than any other data-source attribution you display;

(b) positioned so that it is visible together with the Output it relates to, and not confined to a footer, a separate page, an "about" page or a collapsed element; and

(c) hyperlinked to www.suburbdata.com.au wherever the format permits.

You must not remove, obscure, minimise or alter the attribution, and you must not present the Data in a way that suggests it originates from you or from any third party.

4.8 You must not state or imply that Suburb Data endorses, sponsors, certifies or is a partner of you or your Client Application without our prior written consent.

5.1 Reference Data may be cached. You may store and cache Reference Data — the lists of available months, markets, market types, property types and metrics, including metric names and codes — for as long as you hold an active API Key. You must keep your cached Reference Data reasonably current, and in any event should:

(a) check for an updated months list from around the 4th day of each month until a new release is published;

(b) check for an updated metrics list at least once a month, as new metrics may be added at any time; and

(c) check for an updated markets list at least every three months.

5.2 Reference Data is cached for your own integration only. You must not publish it, redistribute it, or make it available to any person as a standalone list or dataset.

5.3 No storage of Metric Data. Other than Reference Data, you must not store, cache, save, persist, copy, archive or otherwise retain any Data, in any form, on any medium, for any period. Each presentation of such Data to an End User must be served from a request made to the API for that purpose.

5.4 Clause 5.3 applies regardless of:

(a) how the Data is held, including in a database, file, spreadsheet, memory store, message queue, log, backup, analytics pipeline, content delivery network, browser storage or intermediate cache;

(b) whether the Data is held in its original form, in aggregate, in summary, or transformed; and

(c) whether the storage is intended to be permanent or temporary.

5.5 The following are permitted, and are not "storage" for the purposes of clause 5.3:

(a) transient processing of a response in memory for the time reasonably necessary to render the Output for the request that produced it;

(b) retention of a Delivered Document under clause 4.4, in the form in which it was delivered; and

(c) retention of request metadata that contains no Metric Values — for example, a record of which endpoint was called, when, at what cost, and for which market and month.

5.6 You must not:

(a) accumulate Data across requests, months or markets into any persistent store, warehouse, data lake or archive;

(b) construct any dataset that reproduces or substitutes for the Data, whether by accumulation over time, by inference, or by combination with other sources;

(c) use a Delivered Document, or any Output, as a data source for any further request, calculation, comparison or Output; or

(d) use cached Reference Data to infer, reconstruct or approximate any Metric Value or any part of the Scoring IP.

5.7 Historical series returned by the historical chart endpoint are Metric Values for the purposes of this clause. Requesting a long historical series does not create a right to retain it.

5.8 You acknowledge that clause 5.3 means repeat presentations of the same Metric Values require repeat requests, each of which incurs a Data Charge under clause 8.3.

6.1 You must not, and must not permit any person to:

(a) resell, sublicense, redistribute, syndicate, stream, pipe or otherwise make the Data available to any third party, other than as Output permitted by clause 4;

(b) use the Data to build, train, fine-tune, evaluate or ground any machine learning model, language model, embedding, index or retrieval system, whether for your own use or any other person's;

(c) use the API or the Data to develop, improve or operate any product or service that competes with the Suburb Data platform or the API;

(d) systematically enumerate markets, metrics or months — including by iterating the suburb search endpoint across geographies or filter ranges — for the purpose of extracting the Data at scale or reconstructing any part of the Suburb Data database;

(e) reverse engineer, decompile, or attempt to derive, replicate, approximate or infer the Scoring IP, including by statistical analysis of Data returned by the API;

(f) share, pool, proxy or on-sell API access, or operate the API on behalf of another business;

(g) circumvent, disable or interfere with any rate limit, throttle, quota, authentication or monitoring mechanism;

(h) use automated tools to access the API other than your own server-side integration operating within the usage limitations; or

(i) use the API or Data for any unlawful purpose, or in connection with any activity that would breach the Privacy Act 1988 (Cth), the Competition and Consumer Act 2010 (Cth) or applicable anti-discrimination law.

6.2 You must not use the Data as the basis of any representation to a person that a property or location is a good or bad investment, is safe or unsafe, or is desirable or undesirable by reference to the characteristics of the people who live there.

7.1 Trial Data is mock data provided for integration testing only. It does not reflect real market conditions and must never be presented to an End User, published, or used for any decision.

7.2 Access to live mode requires a credited account, payment of the Account Enablement Fee, and our approval of your intended use.

7.3 We may require you to demonstrate a compliant integration before enabling live mode, and may re-verify at any time.

8.1 The API operates on a prepaid, pay-per-request basis. You credit your account through the Suburb Data platform, and each request for Live Data debits your Credit by the applicable Data Charge.

8.2 Data Charges vary by endpoint, metric, volume of data requested and age of data requested. Indicative costs can be obtained through the platform's cost estimate function before a request is made. The charge applied at the time of a request is the charge payable.

8.3 Duplicate requests are charged. Unlike the platform user interface, the API charges each request separately, including repeat requests for identical data. You are responsible for managing your own request volume.

8.4 You are not charged for a metric, market and month combination for which no data exists.

8.5 The Fees in Schedule 1 apply in addition to Data Charges and are debited from your Credit. You must maintain sufficient Credit to cover both the Fees and the Data Charges for any request; requests will fail if your balance is insufficient.

8.6 All amounts are in Australian dollars and are stated inclusive of GST unless otherwise indicated. Credit is not a deposit, does not bear interest, and is not redeemable for cash.

8.7 Credit does not expire.

8.8 We may change Data Charges and Fees on 28 days' notice to the email address on your account. Changes apply to requests made after the notice period ends. Continued use after that date constitutes acceptance.

8.9 Except where required by law, Fees and Data Charges are non-refundable. Nothing in this clause limits your rights under the Australian Consumer Law.

9.1 Your requests are subject to frequency and volume limitations. These limitations are not published, may vary, and may be applied at our discretion.

9.2 We may throttle, queue, reject or suspend requests that exceed those limitations, that impose an unreasonable load on our systems, or that are inconsistent with the use case you told us about.

9.3 If your use case requires higher limits, contact us before building against the API.

10.1 We use reasonable efforts to publish a new data release monthly, on or about the 6th, and to validate the Data before release.

10.2 You acknowledge that:

(a) the Data is compiled and derived from multiple sources, including third-party and government sources, and may contain errors, omissions, gaps or inaccuracies;

(b) not all metrics are available for all markets and all months;

(c) scores, rankings and forecasts — including the DSR family of scores — are estimates produced by statistical models, not predictions or guarantees, and past performance of any methodology does not indicate future performance;

(d) the Data is general information only and is not financial product advice, investment advice, a valuation, or a recommendation in relation to any property or location; and

(e) any reliance on the Data by you or your End Users is at your own risk.

10.3 If you identify a specific inaccuracy, you may report it to us, with supporting evidence, using the Help button on the Suburb Data website. We will acknowledge within 2 business days and investigate within a reasonable time. We are not obliged to make any correction.

10.4 You must include in your own terms of service, and display in your Output, a disclaimer to the effect that the Data is general information only, may be inaccurate or out of date, is not financial or investment advice, and should be independently verified before any decision is made.

11.1 You must have terms of service and a privacy policy that bind your End Users and that are consistent with these Terms, including restrictions on copying, redistributing and extracting the Data at least as protective as clauses 4, 5 and 6.

11.2 You must maintain accurate records of your End Users and be able to identify, on our reasonable request, which End Users have accessed Output.

11.3 You must promptly terminate the access of any End User who breaches those restrictions.

11.4 You are responsible to us for the acts and omissions of your End Users and personnel as if they were your own.

12.1 We may monitor API usage, including request patterns, volumes and parameters, to verify compliance, protect the service and improve our products.

12.2 We may, on reasonable notice and no more than twice in any 12-month period (or at any time where we reasonably suspect a breach):

(a) request a demonstration or test account for your Client Application;

(b) request a written description of how the Data is stored, cached, secured and presented; and

(c) request written confirmation, signed by an officer of your business, that you are complying with clauses 5 and 6.

12.3 You must not obstruct monitoring or audit, and must not deploy measures designed to conceal how the Data is used.

12.4 The Compliance Check Fee in Schedule 1 covers our compliance activity during your initial period of API use.

13.1 The API, the Data, the Reference Data, the Scoring IP, the technical documentation and all associated intellectual property rights are owned by or licensed to Suburb Data.

13.2 You own your Client Application and any material you independently create, but not any part of it that consists of or embodies the Data or the Scoring IP.

13.3 Any goodwill arising from your use of our brand accrues to us. Clause 4.7 governs your obligation to attribute the Data to us; it does not permit any other use of our brand.

13.4 Neither party may use the other's name, logo, brand or any description of the relationship between the parties in any marketing material, case study, press release, website, pitch or public statement without the other party's prior written consent. Consent is specific to the use for which it is given, is not implied by these Terms or by the existence of the relationship, and may be withdrawn on reasonable notice.

13.5 If you notify us of, or we adopt, any feedback or suggestion about the API, we may use it without restriction or obligation to you.

14.1 These Terms commence when you first accept them and continue until terminated.

14.2 You may stop using the API at any time. Unused Credit is dealt with under clause 8.

14.3 We may suspend or disable your API access immediately, without notice, where:

(a) we reasonably suspect a breach of these Terms;

(b) your Credit balance is insufficient;

(c) your usage threatens the availability, security or integrity of the API;

(d) we are required to do so by law or by an upstream data supplier; or

(e) we cease providing the API.

14.4 Where we suspend access for a suspected breach, we will tell you the reason and give you a reasonable opportunity to respond, unless doing so would prejudice an investigation or a third party.

14.5 Re-enabling an account disabled for breach requires payment of a further Account Enablement Fee and any other condition we reasonably impose.

14.6 Either party may terminate on 28 days' written notice. Either party may terminate immediately for material breach that is not remedied within 14 days of notice, or on the other party's insolvency.

14.7 If we terminate under clause 14.3(e) — because we cease providing the API — we will refund your unused Credit. In all other cases unused Credit is forfeited on termination for your breach, and otherwise remains available under clause 8.

15.1 On termination, all licences end and you must immediately stop calling the API.

15.2 You must immediately stop presenting Output to End Users, and must delete all Data held in your possession or control, including cached Reference Data. If we ask, you must confirm in writing within 7 days that you have done so.

15.3 You may retain Delivered Documents already provided to named clients, and records required by law, provided they are not used as a data source and continue to carry the attribution and disclaimer.

15.4 Clauses 5, 6, 13, 15, 16, 17, 18 and 20 survive termination.

16.1 You indemnify us against all loss, damage, cost and expense (including reasonable legal costs) arising from:

(a) your breach of these Terms;

(b) any claim by an End User or third party arising from your Client Application or your Output; and

(c) any claim that your use of the Data infringes a third party's rights.

16.2 Your liability under clause 16.1 is reduced to the extent the loss was caused by our breach or negligence.

17.1 Certain rights under the Australian Consumer Law cannot be excluded, restricted or modified. Nothing in these Terms does so.

17.2 To the extent permitted by law, our liability for breach of a non-excludable consumer guarantee is limited, at our option, to resupplying the relevant service or paying the cost of resupply.

17.3 To the extent permitted by law, we are not liable for loss of profit, revenue, opportunity, goodwill, anticipated savings, data, or any indirect or consequential loss, however arising.

17.4 To the extent permitted by law, our aggregate liability arising out of or in connection with these Terms is limited to the total Data Charges and Fees paid by you in the 3 months before the event giving rise to the claim.

17.5 The API and the Data are provided "as is" and "as available". We do not warrant that the API will be uninterrupted, error-free or secure, and we do not offer service credits or availability guarantees.

18.1 Each party must keep the other's confidential information confidential and use it only for the purposes of these Terms. Our confidential information includes the API Key, the technical documentation, non-public aspects of the Scoring IP, and any non-public pricing.

18.2 Disclosure is permitted to personnel and advisers who need to know and who are bound to equivalent obligations and where required by law.

18.3 These obligations continue for 3 years after termination, and indefinitely for the Scoring IP.

19.1 We may amend these Terms by publishing an updated version and notifying the email address on your account at least 28 days before the change takes effect.

19.2 If you do not accept a change, you may terminate before it takes effect and we will refund unused Credit. Continued use after the effective date constitutes acceptance.

20.1 Governing law. These Terms are governed by the laws of New South Wales, Australia. Each party submits to the exclusive jurisdiction of the courts of that State.

20.2 Notices. Notices to you are sent to the email address on your account. Notices to us go to support@suburbdata.zendesk.com.

20.3 Assignment. You may not assign or novate these Terms, including on a change of control of your business, without our prior written consent, not to be unreasonably withheld. We may assign on notice to you.

20.4 Force majeure. Neither party is liable for delay or failure caused by events beyond its reasonable control. If the event continues for more than 30 days, either party may terminate on notice.

20.5 Entire agreement. These Terms, together with the documents they reference, are the entire agreement between the parties in relation to the API.

20.6 No waiver. A failure to exercise a right is not a waiver of it.

20.7 Severance. If a provision is unenforceable, it is read down or severed to the minimum extent necessary, and the rest continues.

20.8 Relationship. Nothing creates a partnership, joint venture, agency or employment relationship.

20.9 Non-exclusive. These Terms are non-exclusive. We may supply the API to any person, including your competitors.

Fees apply to API users in addition to Data Charges. They are debited from your Credit and are subject to change under clause 8.8.

Fee

Amount (inc. GST)

When charged

Account Enablement Fee

$800

Immediately before your first Live Data request, and again to re-enable an account disabled for breach

Compliance Check Fee

$150 per month

Immediately before your first Live Data request in each new Data Month

Rebate of the Account Enablement Fee. The Account Enablement Fee is credited back to your account once all of the following are satisfied:

(a) at least 6 months have passed since your first Live Data request, or since your most recent breach of these Terms (whichever is later);

(b) you have incurred at least $1,200 in Data Charges (excluding Fees) since your first Live Data request, or since your most recent breach (whichever is later); and

(c) no breach of these Terms is outstanding.

Cessation of the Compliance Check Fee. The Compliance Check Fee ceases to apply once the conditions in (a), (b) and (c) above are satisfied. It recommences on any subsequent breach.

The rebate is provided as account Credit and is not payable in cash.

Version 1.0, effective 26th August 2026.