API Terms
Last updated: 1 July 2026
These API Terms are a Module under the BuiltGrid Platform Terms of Service (Platform Terms) between BuiltGrid Australia Pty Ltd (ABN 63 667 799 813) (BuiltGrid, we, us, our) and (a) each Client that activates API access under its Account, and (b) each Integration Partner that accesses the API on a Client’s behalf (in each case, you, your). They apply in addition to the Platform Terms and to the Buyer Terms or Supplier Terms that apply to the relevant Client. Capitalised terms not defined here have the meanings given in the Platform Terms.
Summary (non-binding): Buyers and Suppliers at any tier of the supply chain (builders, trade contractors, subcontractors and materials suppliers) can use the BuiltGrid API to exchange profile, compliance, pricing and transaction data between BuiltGrid and their own systems, or to let a software vendor do so on their behalf. These API Terms cover credentials and security, what you may do with data you receive through the API (the same Network Rules as the rest of the Platform apply), technical limits, versioning and deprecation, and the responsibilities of Integration Partners.
1. Application and Acceptance
1.1 Clients. These API Terms apply to a Client from the time it activates API access or generates API Credentials, and continue while it holds API Credentials or API access under its Plan.
1.2 Integration Partners. If you access the API on behalf of a Client (for example, as the vendor of construction management, estimating, scheduling, enterprise resource planning software or accounting software the Client uses), you are an Integration Partner. You accept these API Terms by generating or using API Credentials, and you must comply with them in addition to any authorisation the Client gives you. If you are not also a Client, Platform Terms clauses 8, 10, 11, 12.1, 13, 16 and 17 apply to you as if you were a Client.
1.3 Relationship with other terms. These API Terms supplement the Platform Terms and the Client’s Buyer Terms or Supplier Terms, and override them only where they expressly deal with the same matter (Platform Terms clause 1.4).
1.4 Definitions. Additional defined terms are in clause 14 of these API Terms.
2. API Credentials and Access
2.1 Issue of credentials. We issue API Credentials to a Client through its Account. A Client may generate credentials for its own Applications and may authorise an Integration Partner to receive credentials or delegated access for that Client’s data.
2.2 Keep credentials secure. You must keep API Credentials confidential, store them securely, never embed them in client-side code or public repositories, use a separate credential for each Application, rotate credentials periodically and immediately if you suspect compromise, and notify us at builtgrid.com/contact-us without delay if a credential is lost or compromised.
2.3 Responsibility for use. You are responsible for all API calls made using your API Credentials, whether or not you authorised them, until you notify us of a compromise and we have had a reasonable opportunity to disable the credential.
2.4 Environments. We may provide a Sandbox for development and testing. The Sandbox may be reset at any time, must only contain test data, and is excluded from the Service Level Schedule and from the warranties in Platform Terms clause 12.2.
3. Licence
3.1 Clients. Subject to this agreement, we grant a Client a non-exclusive, non-transferable, revocable licence during the term to use the API and API Documentation to develop and operate Applications that access the Client’s own Client Data and the Shared Data the Client is permitted to access through the Platform, for the Client’s internal business purposes and to integrate the Services with systems and third-party products the Client uses.
3.2 Integration Partners. Subject to this agreement, we grant an Integration Partner a non-exclusive, non-transferable, revocable licence during the term to use the API and API Documentation solely to provide its software or services to the authorising Client, using that Client’s API Credentials or delegated access, and only within the scope of the Client’s authorisation.
3.3 Reservation. All rights not expressly granted are reserved. The API and API Documentation are BuiltGrid Materials.
4. Integration Partners
4.1 Client authorisation and responsibility. A Client that authorises an Integration Partner remains responsible to us for the Integration Partner’s use of the API and of the Client’s data, and must ensure the Integration Partner complies with these API Terms. A Client may revoke an Integration Partner’s access at any time through its Account.
4.2 Use of Client data. An Integration Partner may use data accessed through the API only to provide its software or services to the authorising Client and as that Client directs. It must not: (a) use the data for its own purposes, including analytics, benchmarking, marketing or product development, except as the Client expressly permits in writing and the law allows; (b) combine or aggregate data across multiple Clients without our prior written agreement; (c) retain data longer than needed to serve the Client; or (d) disclose the data to third parties other than its own sub-processors bound by equivalent obligations.
4.3 Shared Data of other Clients. Where an Integration Partner receives Shared Data of the authorising Client’s Connections through the API, Platform Terms clauses 6.4 to 6.8 apply to the Integration Partner as they apply to the authorising Client, and the Integration Partner may use that Shared Data only to provide its services to the authorising Client for the purposes permitted by Platform Terms clause 6.4.
4.4 Partner program. We may offer an integration partner program with additional terms, listing, certification or commercial arrangements. Access to the API under these API Terms does not make you a partner of BuiltGrid, and you must not describe yourself as endorsed, certified or partnered with BuiltGrid unless we have agreed that in writing.
4.5 Our discretion. We may decline, suspend or revoke an Integration Partner’s API access where reasonably necessary to protect the Services, Clients or their data, including where the Integration Partner competes with the Services or has breached these API Terms. We will notify the affected Clients where practicable.
5. Data Accessed Through the API
5.1 Nature of the data. Data returned by the API is either the Client’s own Client Data or Shared Data of other Clients, received through the Client’s Connections or through Upstream Sharing. The Network Rules in Platform Terms clause 6, including the permitted purposes (6.4), restrictions (6.5), confidentiality (6.6), retention after a Connection ends (6.8) and the multi-tier and Upstream Sharing rules (6.9 and 6.10), apply to Shared Data received through the API exactly as they apply in the Platform. In particular, you must not use the API to pass a Supplier’s pricing or Transaction Records to that Supplier’s competitors or to Upstream Clients.
5.2 Copies and caches. You may store copies of data received through the API in your Application or systems to the extent needed for the permitted purposes. You must keep those copies secure, keep them reasonably current, and delete or stop using Shared Data when the relevant Connection ends, subject to the record-keeping retention permitted by Platform Terms clause 6.8.
5.3 Personal Information. Data received through the API may include Personal Information (for example, contact details of a Connection’s personnel or details on licences and insurance certificates). You must handle it in accordance with the Privacy Act 1988 (Cth) and use it only for the permitted purposes.
5.4 Writing data to the Platform. You are responsible for the accuracy, format and legality of data your Application writes to the Platform, including data that will be shared with your Connections. Data written through the API is Client Data of the Client whose credentials were used.
5.5 No bulk extraction of other Clients’ data. You must not use the API to compile, extract or index data about Clients other than through Shared Data made available to you through Connections, and you must not use the API to build or populate a directory, database or marketplace of Buyers or Suppliers.
6. Technical Requirements and Fair Use
6.1 Documentation. You must use the API in accordance with the API Documentation, including authentication methods, request formats, pagination, error handling and retry behaviour.
6.2 Rate limits and technical controls. We may set and publish rate limits, concurrency limits, payload limits and other technical controls in the API Documentation, and may adjust them to protect the stability and security of the Services (Platform Terms clause 4.7). You must not circumvent them. If your Application exceeds a limit, requests may be throttled or rejected, and you must implement exponential back-off.
6.3 Efficient use. You must use webhooks or incremental endpoints where available rather than repeatedly polling for changes, avoid unnecessary or duplicate requests, and not use the API in a way that places an unreasonable load on the Services.
6.4 Usage-based Fees. Your Plan or Order Form specifies usage allotments and overage Fees. Any changes to allotments or overage Fees takes effect from your next Subscription Term with at least 30 days notice (Platform Terms clause 4.7).
7. Versioning, Changes and Deprecation
7.1 Versions. We version the API. We may make backward-compatible changes to a version at any time (for example, adding endpoints, optional parameters or response fields). Your Application must tolerate additions of this kind.
7.2 Breaking changes. Changes that are not backward-compatible will be released as a new version. We will give at least 6 months notice before retiring a version, published in the API Documentation and notified to the contact email for each Account with active credentials on that version, except where an earlier change is required for security or legal reasons.
7.3 Beta endpoints. Endpoints marked as beta or preview may change or be withdrawn without notice and are excluded from clause 7.2.
8. Security
8.1 Your obligations. You must: (a) connect to the API only over encrypted (TLS) connections; (b) store API Credentials and any tokens using industry-standard secrets management; (c) apply least-privilege access within your Application and systems; (d) keep your Application and dependencies patched; and (e) log API activity sufficiently to investigate incidents.
8.2 Incidents. You must notify us at builtgrid.com/contact-us without undue delay if you become aware of any security incident affecting API Credentials, your Application or data received through the API, and cooperate with us in responding to it. Our notification obligations to Clients are in Platform Terms clause 7.7.
8.3 Testing. You must not perform security or penetration testing against the API or the Services without our prior written consent. For testing, request a Sandbox. Report suspected vulnerabilities to builtgrid.com/contact-us.
9. Restrictions
In addition to Platform Terms clause 8 (Acceptable Use), you must not: (a) use the API to build a product or service that competes with the Services; (b) sell, sublicense or resell access to the API or to data obtained through it; (c) use the API to automate account creation, Connection requests or messaging in a manner that is unsolicited or misleading; (d) remove or obscure any notices or attributions returned by the API; (e) use the API for a Client that has not authorised you; (f) attempt to access data outside the scope of your credentials or a Client’s authorisation; or (g) misrepresent the source of data or the status of your Application’s relationship with BuiltGrid.
10. Your Applications
10.1 Responsibility. You are solely responsible for your Application, including its design, operation, security, legal compliance and support. We do not test, support or warrant your Application.
10.2 Privacy and transparency. If your Application handles Personal Information, you must maintain a privacy policy that accurately describes your collection, use and disclosure of that information and complies with the Privacy Act 1988 (Cth).
10.3 Describing the integration. You may state factually that your Application integrates with or works with BuiltGrid. You must not use our logos or trade marks without our prior written consent (Platform Terms clause 10.3). We may, with your consent, list your Application in an integrations directory.
11. Monitoring, Suspension and Termination
11.1 Monitoring. We monitor API usage for security, capacity planning, verification of usage allotments and compliance with these API Terms.
11.2 Suspension. We may suspend or disable API Credentials in accordance with Platform Terms clause 14.1, including where an Application threatens the security or stability of the Services or breaches these API Terms. We will give notice where practicable and restore access promptly once the cause is resolved.
11.3 Termination. API access ends when the Client deactivates it, when the relevant Plan or Subscription ends, or when the agreement terminates. On termination you must stop using the API, destroy API Credentials, and handle data received through the API in accordance with Platform Terms clauses 6.8 and 14.4.
12. Service Levels and Support
12.1 Availability. Where a Client’s paid Plan includes API access, the availability commitment and service credits in the Service Level Schedule apply to the production API as stated in that Schedule. The Sandbox, beta endpoints and Free Access are excluded.
12.2 Developer support. We provide reasonable support for the API through the API Documentation and the support channels in the Service Level Schedule. Support does not extend to developing, debugging or maintaining your Application.
13. Warranties and Liability
13.1 Platform Terms apply. Platform Terms clauses 12 (Warranties and Australian Consumer Law) and 13 (Liability and Indemnities) apply to these API Terms. Our warranty in Platform Terms clause 12.2 applies to the production API operating in accordance with the API Documentation; it does not extend to the Sandbox, beta endpoints or your Application.
13.2 Integration Partners. An Integration Partner indemnifies us and the authorising Client against loss arising from its use of the API or data in breach of these API Terms, on the same basis (including the contribution reduction) as Platform Terms clause 13.4. Our liability to an Integration Partner that is not a Client is limited to $0.
14. Definitions
“API Credentials” means API keys, client secrets, tokens and other credentials issued or generated through the Platform for access to the API.
“API Documentation” means the documentation for the API that we publish from time to time, including reference material, rate limits, versioning and deprecation notices.
“Application” means software (including scripts, connectors and integrations) that you develop or operate and that accesses the API.
“Integration Partner” means a person other than the Client that accesses the API on a Client’s behalf and with the Client’s authorisation, as described in clause 1.2 of these API Terms.
“Sandbox” means any non-production API environment we make available for development and testing.
Contact us
BuiltGrid at https://builtgrid.com/contact-us/
Reference: Platform Terms of Service
—-
Service Levels and Support Schedule
Last updated: 1 July 2026
This Schedule forms part of the agreement between BuiltGrid Australia Pty Ltd (ABN 63 667 799 813) (BuiltGrid, we, us, our) and each Client under the BuiltGrid Platform Terms of Service (Platform Terms). It sets out our availability commitment, service credits and support arrangements. Capitalised terms not defined here have the meanings given in the Platform Terms.
Summary (non-binding): Paid Plans in production come with a 99.0% monthly availability target, and support with defined severity levels and response targets. Free Access, beta features, staging and sandbox environments are excluded.
1. Application
1.1 Covered Services. This Schedule applies to the production Platform (web application and API) used under a paid Subscription (Covered Services). An Order Form may specify enhanced service levels or support, which prevail over this Schedule.
1.2 Exclusions. This Schedule does not apply to Free Access, beta or preview features, staging, test or Sandbox environments, third-party products or systems, Integrations that depend on third-party systems, or Implementation Services.
1.3 Changes. We may update this Schedule in accordance with Platform Terms clause 15. We will not reduce the availability commitment or service credit levels for a paid Subscription before the start of its next Subscription Term.
2. Availability Commitment
2.1 Target. We will use commercially reasonable efforts to make the Covered Services available with a Monthly Uptime Percentage of at least 99.0%.
2.2 Calculation. Monthly Uptime Percentage means, for a calendar month: (total minutes in the month minus Downtime minutes) divided by total minutes in the month, expressed as a percentage. Downtime means minutes during which the Covered Services are unavailable to substantially all Clients, as measured by our monitoring systems, excluding the Excluded Events in clause 2.3.
2.3 Excluded Events. Downtime does not include unavailability caused by: (a) Scheduled Maintenance; (b) Emergency Maintenance; (c) events beyond our reasonable control, including failures of the internet, telecommunications, power or hosting infrastructure not operated by us where we have taken reasonable steps to mitigate them; (d) your or your Users’ acts or omissions, equipment, software or network; (e) third-party products or systems; (f) suspension in accordance with the Platform Terms; or (g) denial-of-service or similar attacks, provided we act reasonably to mitigate them.
2.4 Scheduled Maintenance. Scheduled Maintenance means planned maintenance notified at least 48 hours in advance through the status page or in-product notice and conducted, wherever practicable, outside Australian business hours (Monday to Friday, 8am to 6pm Melbourne time). Scheduled Maintenance will not exceed 8 hours in any calendar month without additional notice.
2.5 Emergency Maintenance. Emergency Maintenance means unplanned maintenance reasonably required to address a security vulnerability or an imminent risk to the Services, which we will notify as soon as practicable, and which will not exceed 4 hours in any calendar month.
3. Service Credits
3.1 Credit levels. If the Monthly Uptime Percentage for a calendar month falls below the target, you are entitled to a service credit calculated as a percentage of the Monthly Fee for the affected Subscription:
3.2 Monthly Fee. Monthly Fee means the Fees for the affected Subscription attributable to the relevant month: the monthly installment, or one-twelfth of the annual Fee if paid up front. It excludes Implementation Services and overage Fees.
3.3 How to claim. To receive a service credit, you must request it at builtgrid.com/contact-us within 30 days after the end of the month concerned, identifying the dates and times of the unavailability. We will confirm the claim against our monitoring records within 14 business days.
3.4 Application of credits. Service credits are applied against your next installment or invoice (or, if none remains in the Subscription Term, refunded within 30 days). Credits for a single month will not exceed 10% of the Monthly Fee.
3.5 Exclusive remedy and chronic failure. Subject to your rights under the Australian Consumer Law, service credits are your sole and exclusive remedy for a failure to meet the availability target, except that if the Monthly Uptime Percentage is below 95.0% in any 3 months within a rolling 6-month period, or below 90.0% in 2 consecutive months, you may terminate the affected Subscription by written notice within 30 days after the end of the last such month, and Platform Terms clause 14.5 applies.
4. Support
4.1 Channels and hours. Support is available through in-product chat, by email at builtgrid.com/contact-us and by phone on 1300 547 757, Monday to Friday, 9am to 5pm Melbourne time, excluding Victorian public holidays (Business Hours). Requests received outside Business Hours are treated as received at the start of the next Business Hours period.
4.2 Support tiers. The support tier that applies depends on your Plan:
4.3 Severity levels and response targets. For the Standard tier, we classify support requests as follows and target the initial responses shown. Response means acknowledgement by a support engineer and commencement of work, not resolution.
4.4 Classification. You may propose a severity when raising a request. We will classify it reasonably in accordance with the definitions above and tell you if we change it.
4.5 Your responsibilities. To help us meet these targets you must: (a) provide a clear description of the issue, steps to reproduce, affected Users and any error messages; (b) nominate contacts authorised to raise and discuss support requests; and (c) respond to our reasonable requests for information. Response targets pause while we wait for information from you.
4.6 Out of scope. Support does not include: training beyond the onboarding included in your Plan; custom development, configuration or data entry; support for your own systems, third-party products or Integration Partners’ Applications; or recovery of data deleted by your Users beyond restoration from our standard backups where available.
5. Incident Communication
5.1 Status page. We publish the current status of the Covered Services, Scheduled Maintenance and incident updates at app.builtgrid.com.
5.2 Major incidents. For a P1 incident affecting many Clients, we will post updates to the status page at least every 8 Business Hours until mitigated and publish a summary of the cause and remediation within 10 business days after resolution.
5.3 Security incidents. Notification of security incidents affecting Client Data is governed by Platform Terms clause 7.7.
6. Backups and Recovery
6.1 Backups. We back up production Client Data at least daily and retain backups for at least 30 days. Backups are stored in Australia.
6.2 Recovery objectives. In the event of a disaster affecting our primary hosting environment, we target restoration of the Covered Services within 24 hours (recovery time objective) with data loss of no more than 24 hours (recovery point objective). These are targets, not guarantees, and do not give rise to service credits beyond those in clause 3.
Contact us
BuiltGrid at https://builtgrid.com/contact-us/
Reference: Platform Terms of Service
