BuildingTransparency APIs Terms of Service

Last modified: April 6, 2026

Thank you for using BuildingTransparency’s APIs, other developer services, and associated software (collectively, “APIs”). By accessing or using our APIs, you are agreeing to the terms below. If there is a conflict between these terms and additional terms applicable to a given API, the additional terms will control for that conflict. Collectively, we refer to the terms below, any additional terms, terms within the accompanying API documentation, and any applicable policies and guidelines as the “Terms.” You agree to comply with the Terms and that the Terms control your relationship with us. So please read all the Terms carefully. If you use the APIs as an interface to, or in conjunction with other BuildingTransparency products or services, then the terms for those other products or services also apply.

For paid API access, these Terms are incorporated into and form part of the EC3 API Order Form executed between BuildingTransparency and Customer. The Order Form constitutes the EC3 API Data Usage Agreement referenced in BuildingTransparency’s API Access & Pricing schedule (the ‘Order Form’ and together with these Terms, the ‘Agreement’). In the event of a conflict between these Terms and an executed Order Form, the Order Form will control. Capitalized terms used but not defined in the Order Form have the meaning given in these Terms.

Under the Terms, “BuildingTransparency” means Building Transparency, a Washington State nonprofit corporation, with offices at 3213 W Wheeler Street #1014, Seattle, WA 98199-3245, unless set forth otherwise in additional terms applicable for a given API. We may refer to “BuildingTransparency” as “we”, “our”, or “us” in the Terms.

Building Transparency is a 501(c)(3) nonprofit organization whose mission is to provide open-access data and tools that accelerate embodied carbon reduction across the built environment. Building Transparency operates EC3 as a neutral, nonprofit steward of the world’s largest digital repository of Environmental Product Declarations (EPDs)

Section 1: Account and Registration

a. Accepting the Terms

You may not use the APIs and may not accept the Terms if (a) you are not of legal age to form a binding contract with BuildingTransparency, or (b) you are a person barred from using or receiving the APIs under the applicable laws of the United States or other countries including the country in which you are resident or from which you use the APIs.

b. Entity Level Acceptance

If you are using the APIs on behalf of an entity, you represent and warrant that you have authority to bind that entity to the Terms and by accepting the Terms, you are doing so on behalf of that entity (and all references to “you” in the Terms refer to that entity).

c. Registration

In order to access certain APIs you may be required to provide certain information (such as identification or contact details) as part of the registration process for the APIs, or as part of your continued use of the APIs. Any registration information you give to BuildingTransparency will always be accurate and up to date and you’ll inform us promptly of any updates. Paid API access requires execution of an Order Form. By signing an Order Form, Customer represents that all registration information provided is accurate and current, and agrees to notify BuildingTransparency promptly of any changes.

d. Suppliers and Affiliates

BuildingTransparency has suppliers and affiliated legal entities around the world. These companies may provide the APIs to you on behalf of BuildingTransparency and the Terms will also govern your relationship with these companies.

Section 2: Using Our APIs

a. Your End Users

You will require your end users to comply with (and not knowingly enable them to violate) applicable law, regulation, and the Terms.

b. Compliance with Law, Third Party Rights, and Other BuildingTransparency Terms of Service

You will comply with all applicable law, regulation, and third party rights (including without limitation laws regarding the import or export of data or software, privacy, and local laws). You will not use the APIs to encourage or promote illegal activity, anticompetitive behaviour, or violation of third party rights. You will not violate any other terms of service with BuildingTransparency (or its affiliates).

c. Permitted Access

You will only access (or attempt to access) an API by the means described in the documentation of that API. If BuildingTransparency assigns you developer credentials (e.g. client IDs), you must use them with the applicable APIs. You will not misrepresent or mask either your identity or your API Client’s identity when using the APIs or developer accounts.

d. API Limitations

BuildingTransparency sets and enforces rate limits on your use of the APIs based on the access tier associated with your account, as set forth in the applicable Order Form or API Access & Pricing schedule. If usage reaches or exceeds approved thresholds, BuildingTransparency may, in its reasonable discretion and in lieu of termination, rate-limit (slow) requests rather than terminate access, in order to protect platform reliability and service integrity for all users. Current rate limit information is available in BuildingTransparency’s user guide at docs.buildingtransparency.org and may be adjusted from time to time. If you would like to use any API beyond your tier’s limits, you must obtain BuildingTransparency’s express written consent. Contact support@buildingtransparency.org or submit a request through the EC3 UserSnap system.

e. Open Source Software

Some of the software required by or included in our APIs may be offered under an open source license. Open source software licenses constitute separate written agreements. For certain APIs, open source software is listed in the documentation. To the limited extent the open source software license expressly supersedes the Terms, the open source license instead sets forth your agreement with BuildingTransparency for the applicable open source software.

f. Communication with BuildingTransparency

We may send you certain communications in connection with your use of the APIs. Please review the applicable API documentation for information about opting out of certain types of communication.

g. Feedback

If you provide feedback or suggestions about our APIs, then we (and those we allow) may use such information without obligation to you.

h. Non-Exclusivity

The Terms are non-exclusive. You acknowledge that BuildingTransparency may develop products or services that may compete with the API Clients or any other products or services.

i. Data Protection and Privacy

You are solely responsible for ensuring that you have the authority to transfer any data you transfer to BuildingTransparency, and that the BuildingTransparency privacy policy and confidentiality policies are a sufficient protection for such data.

Section 3: Commercial Use and Data Resale Restriction Clause

The resale, sublicense, or redistribution of the copyrighted database of the EC3 API has not been licensed or otherwise authorized, and is a violation of law. To clarify this legal circumstance, the following terms apply.

a. Permitted Use

Free-tier API access is permitted for research, learning, and pilot integrations, and does not include the right to store, cache for reuse, or deploy EC3 data in commercial or production applications. Paid-tier API access, as set forth in an executed Order Form, grants a non-exclusive, non-transferable, revocable license to access, store, cache, and reuse EC3 API Data solely during the Term, and to use EC3 API Data in commercial and production applications. Resale, sublicensing, or redistribution of EC3 data as a standalone data product remains prohibited for all tiers without express written consent from BuildingTransparency.

b. Prohibited Activities

Additionally, regardless of access tier, users shall not: (i) represent EC3 data as their own proprietary data; (ii) use API access to circumvent applicable attribution requirements; or (iii) claim any governance, advisory, or decision-making rights based on API access or fee payment.

c. Notification Requirement

Whether or not User plans to resell, sublicense, or redistribute data obtained from the EC3 API, users must notify BuildingTransparency of their intent to integrate the data into their platforms or databases prior to commencing such integration. Notification is also required for any on-going provision of EC3 API data pursuant to an existing agreement relating to the resale, sublicense, or redistribution of such data. Notifications should be sent to support@buildingtransparency.org

d. Binding Terms

These terms apply to all users of the EC3 API, including those currently using the API. There is no grandfathering of previous terms, and all users are bound by these updated terms effective immediately.

e. Consequences for Non-Compliance

Failure to notify BuildingTransparency prior to use or to obtain necessary approvals for prohibited activities will result in immediate suspension of access to the EC3 API.

Users will have 14 days from the date of suspension to rectify the violation by providing the required notification or obtaining the necessary approval. If the violation is not rectified within this period, access will be permanently terminated.

Additional legal actions may be taken, including but not limited to claims for damages and injunctive relief.

f. Fees and Payment

API access fees are based on the tier selected by the Customer, as set forth in the current API Access & Pricing schedule published at buildingtransparency.org/api-access-pricing and in any applicable Order Form. Tier selection is self-reported based on the organization’s most recent 12-month revenue or valuation, whichever is higher.

Fees are invoiced upon execution of an Order Form. Available payment structures include: (i) annual payment; (ii) two-year prepayment (subject to a 10% discount); or (iii) monthly payments (subject to a 10% premium).

API fees apply solely to EC3 API Data access and usage volume and do not include customization, consulting services, enterprise instances, implementation support, or preferential assistance.

BuildingTransparency’s fees are exclusive of all taxes, levies, or duties imposed by taxing authorities. Customer is responsible for any sales, duty, or other governmental taxes or fees due with respect to the Services. BuildingTransparency will collect, and the Customer will pay, applicable sales tax where BuildingTransparency determines it has a duty to collect.

BuildingTransparency reserves the right to adjust pricing tiers upon 30 days’ written notice. Prepaid fees are non-refundable except as required by applicable law or as expressly provided in an Order Form.

g. Fee Waivers

BuildingTransparency may, in its sole discretion, grant time-limited fee waivers to organizations engaged in research, education, or mission-aligned work that advances embodied-carbon reduction and public benefit. Fee waivers: (i) are granted for a defined duration not to exceed 12 months per grant period and may be renewed subject to review; (ii) do not modify API governance, attribution, or other access terms; and (iii) do not confer preferential access, influence over EC3 roadmap or policies, or governance rights. Organizations receiving fee waivers remain subject to all other provisions of these Terms.

h.Charitable Contributions

API access fees are separate from and independent of any charitable contributions to BuildingTransparency. Organizations may independently choose to make unrestricted charitable contributions to support Building Transparency’s mission and the continued operation of EC3 as public infrastructure. Such contributions: (i) are entirely voluntary; (ii) do not affect API pricing, access tier, rate limits, or any other access terms; and (iii) will be acknowledged in accordance with applicable IRS regulations. No quid pro quo arrangement between charitable contributions and API access terms is intended or should be inferred.

Section 4: Your API Clients

a. API Clients and Monitoring

The APIs are designed to help you enhance your environmental declaration system and applications (“API Client(s)”). YOU AGREE THAT BuildingTransparency MAY MONITOR USE OF THE APIS TO ENSURE QUALITY, IMPROVE BuildingTransparency PRODUCTS AND SERVICES, AND VERIFY YOUR COMPLIANCE WITH THE TERMS. This monitoring may include BuildingTransparency accessing and using your API Client, for example to identify security issues that could affect BuildingTransparency or its users. You will not interfere with this monitoring. BuildingTransparency may use any technical means to overcome such interference. BuildingTransparency may suspend access to the APIs by you or your API Client without notice if we reasonably believe that you are in violation of the Terms.

b. Security

You will use commercially reasonable efforts to protect user information collected by your API Client, including personally identifiable information (“PII”), from unauthorized access or use and will promptly report to your users any unauthorized access or use of such information to the extent required by applicable law.

c. Ownership

BuildingTransparency does not acquire ownership in your API Clients, and by using our APIs, you do not acquire ownership of any rights in our APIs or the content that is accessed through our APIs.

d. User Privacy and API Clients

You will comply with all applicable privacy laws and regulations including those applying to PII. You will provide and adhere to a privacy policy for your API Client that clearly and accurately describes to users of your API Client what user information you collect and how you use and share such information (including for advertising) with BuildingTransparency and third parties.

e. No Governance Rights, Neutrality

API access does not confer governance, advisory, or decision-making rights; influence over EC3 roadmap, standards, or policies; or preferential data treatment, visibility, or priority support. BuildingTransparency operates EC3 as a neutral nonprofit steward and applies these Terms consistently across all users regardless of fee tier, contribution history, or organizational affiliation.

Section 5: Prohibitions and Confidentiality

a. API Prohibitions

When using the APIs, you may not (or allow those acting on your behalf to):

1. Perform an action with the intent of introducing to BuildingTransparency products and services any viruses, worms, defects, Trojan horses, malware, or any items of a destructive nature.
2. Defame, abuse, harass, stalk, or threaten others.
3. Interfere with or disrupt the APIs or the servers or networks providing the APIs.
4. Use the APIs for any activities where the use or failure of the APIs could lead to death, personal injury, or environmental damage (such as the operation of nuclear facilities, air traffic control, or life support systems).
5. Use the APIs to process or store any data that is subject to the International Traffic in Arms Regulations maintained by the U.S. Department of State.
6. Remove, obscure, or alter any BuildingTransparency terms of service or any links to or notices of those terms.

Unless otherwise specified in writing by BuildingTransparency, BuildingTransparency does not intend use of the APIs to create obligations under the Health Insurance Portability and Accountability Act, as amended (“HIPAA”), and makes no representations that the APIs satisfy HIPAA requirements. If you are (or become) a “covered entity” or “business associate” as defined in HIPAA, you will not use the APIs for any purpose or in any manner involving transmitting protected health information to BuildingTransparency.

b. Confidential Matters

1. Developer credentials (such as passwords, keys, and client IDs) are intended to be used by you and identify your API Client. You will keep your credentials confidential and make reasonable efforts to prevent and discourage other API Clients from using your credentials. Developer credentials may not be embedded in open source projects.
2. Our communications to you and our APIs may contain BuildingTransparency confidential information. BuildingTransparency confidential information includes any materials, communications, and information that are marked confidential or that would normally be considered confidential under the circumstances. If you receive any such information, then you will not disclose it to any third party without BuildingTransparency’s prior written consent. BuildingTransparency confidential information does not include information that you independently developed, that was rightfully given to you by a third party without confidentiality obligation, or that becomes public through no fault of your own. You may disclose BuildingTransparency confidential information when compelled to do so by law if you provide us reasonable prior notice, unless a court orders that we not receive notice.

Section 6: Content

a. Content Accessible Through our APIs

Our APIs contain some third party content (such as text, images, videos, and EPDs). This content is the sole responsibility of the person that makes it available. We may sometimes review content to determine whether it is illegal or violates our policies or the Terms, and we may remove or refuse to display content. Finally, content accessible through our APIs may be subject to intellectual property rights, and, if so, you may not use it unless you are licensed to do so by the owner of that content or are otherwise permitted by law. Your access to the content provided by the API may be restricted, limited, or filtered in accordance with applicable law, regulation, and policy.

b. Submission of Content

Some of our APIs allow the submission of content, such as EPDs. BuildingTransparency does not acquire any ownership of any intellectual property rights in the content that you submit to our APIs through your API Client, except as expressly provided in the Terms. For the sole purpose of enabling BuildingTransparency to provide, secure, and improve the APIs and the related service(s), and only in accordance with the applicable BuildingTransparency privacy policies, you give BuildingTransparency a perpetual, irrevocable, worldwide, sublicensable, royalty-free, and non-exclusive license to Use content submitted, posted, or displayed to or from the APIs through your API Client. “Use” means use, host, store, modify, communicate, and publish. Before you submit content to our APIs through your API Client, you will ensure that you have the necessary rights (including the necessary rights from your end users) to grant us the license.

c. Retrieval of content

When a user’s non-public content is obtained through the APIs, you may not expose that content to other users or to third parties without explicit opt-in consent from that user.

e. Prohibitions on Content

Unless expressly permitted by the content owner or by applicable law, you will not, and will not permit your end users or others acting on your behalf to, do the following with content returned from the APIs:

1. Misrepresent the environmental impact of material(s);
2. Misrepresent the source or ownership; or
3. Remove, obscure, or alter any copyright, trademark, or other proprietary rights notices; or falsify or delete any author attributions, legal notices, or other labels of the origin or source of material.

Section 7: Brand Features; Attribution

a. Brand Features

“Brand Features” is defined as the trade names, trademarks, service marks, logos, domain names, and other distinctive brand features of each party. Except where expressly stated, the Terms do not grant either party any right, title, or interest in or to the other party’s Brand Features. All use by you of BuildingTransparency’s Brand Features (including any goodwill associated therewith) will inure to the benefit of BuildingTransparency.

b. Attribution

You agree to display any attribution(s) required by BuildingTransparency as described in the documentation for the API. BuildingTransparency hereby grants to you a nontransferable, nonsublicenseable, nonexclusive license while the Terms are in effect to display BuildingTransparency’s Brand Features for the purpose of promoting or advertising that you use the APIs. You must only use the BuildingTransparency Brand Features in accordance with the Terms and for the purpose of fulfilling your obligations under this Section. You understand and agree that BuildingTransparency has the sole discretion to determine whether your attribution(s) and use of BuildingTransparency’s Brand Features are in accordance with the above requirements and guidelines.

c. Publicity

You will not make any statement regarding your use of an API which suggests partnership with, sponsorship by, or endorsement by BuildingTransparency without BuildingTransparency’s prior written approval.

d. Promotional and Marketing Use

In the course of promoting, marketing, or demonstrating the APIs you are using and the associated BuildingTransparency products, BuildingTransparency may produce and distribute incidental depictions, including screenshots, video, or other content from your API Client, and may use your company or product name. You grant us all necessary rights for the above purposes.

Section 8: Privacy and Copyright Protection

a. Privacy Policies

By using our APIs, BuildingTransparency may use submitted information in accordance with our privacy policy or confidentiality policy.

b. DMCA Policy

We provide information to help copyright holders manage their intellectual property online, but we can’t determine whether something is being used legally or not without their input. We respond to notices of alleged copyright infringement and terminate accounts of repeat infringers according to the process set out in the U.S. Digital Millennium Copyright Act. If you think somebody is violating your copyrights and wants to notify us, please submit a notice to support@buildingtransparency.org.

Section 9: Termination

a. Termination

You may stop using our APIs at any time with or without notice. Further, if you want to terminate the Terms, you must provide us with prior written notice and, upon termination, cease your use of the applicable APIs. BuildingTransparency reserves the right to terminate the Terms with you or discontinue the APIs or any portion or feature or your access thereto for any reason and at any time without liability or other obligation to you. Unless otherwise specified in an applicable Order Form, paid API access is granted on an annual basis commencing on the date of Order Form execution. BuildingTransparency may suspend or terminate access immediately, without prior notice, in cases of misuse, abuse, security concerns, or material breach of these Terms.

b. Your Obligations Post-Termination

Upon any termination of the Terms or discontinuation of your access to an API, you will immediately stop using the API, cease all use of the BuildingTransparency Brand Features, and delete any cached or stored content that was permitted by the cache header under Section 5. Building Transparency may independently communicate with any account owner whose account(s) are associated with your API Client and developer credentials to provide notice of the termination of your right to use an API. Users with paid API access who have stored or cached EC3 API Data must, upon termination or expiration of the Agreement, immediately cease all use of such data and, upon BuildingTransparency’s written request, certify in writing that all stored EC3 API Data has been deleted or returned.

c. Surviving Provisions

When the Terms come to an end, those terms that by their nature are intended to continue indefinitely will continue to apply, including but not limited to: Sections 4b, 5, 8, 9, and 10.

Section 10: Liability for our APIs

a. WARRANTIES

EXCEPT AS EXPRESSLY SET OUT IN THE TERMS, NEITHER BuildingTransparency NOR ITS SUPPLIERS OR DISTRIBUTORS MAKE ANY SPECIFIC PROMISES ABOUT THE APIS. FOR EXAMPLE, WE DON’T MAKE ANY COMMITMENTS ABOUT THE CONTENT ACCESSED THROUGH THE APIS, THE SPECIFIC FUNCTIONS OF THE APIS, OR THEIR RELIABILITY, AVAILABILITY, OR ABILITY TO MEET YOUR NEEDS. WE PROVIDE THE APIS “AS IS”.

SOME JURISDICTIONS PROVIDE FOR CERTAIN WARRANTIES, LIKE THE IMPLIED WARRANTY OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, AND NON-INFRINGEMENT. EXCEPT AS EXPRESSLY PROVIDED FOR IN THE TERMS, TO THE EXTENT PERMITTED BY LAW, WE EXCLUDE ALL WARRANTIES, GUARANTEES, CONDITIONS, REPRESENTATIONS, AND UNDERTAKINGS.

b. LIMITATION OF LIABILITY

WHEN PERMITTED BY LAW, BuildingTransparency, AND BuildingTransparency ‘s SUPPLIERS AND DISTRIBUTORS, WILL NOT BE RESPONSIBLE FOR LOST PROFITS, REVENUES, OR DATA; FINANCIAL LOSSES; OR INDIRECT, SPECIAL, CONSEQUENTIAL, EXEMPLARY, OR PUNITIVE DAMAGES.

TO THE EXTENT PERMITTED BY LAW, THE TOTAL LIABILITY OF BuildingTransparency, AND ITS SUPPLIERS AND DISTRIBUTORS, FOR ANY CLAIM UNDER THE TERMS, INCLUDING FOR ANY IMPLIED WARRANTIES, IS LIMITED TO THE AMOUNT YOU PAID US TO USE THE APPLICABLE APIS (OR, IF WE CHOOSE, TO SUPPLYING YOU THE APIS AGAIN) DURING THE SIX MONTHS PRIOR TO THE EVENT GIVING RISE TO THE LIABILITY.

IN ALL CASES, BuildingTransparency, AND ITS SUPPLIERS AND DISTRIBUTORS, WILL NOT BE LIABLE FOR ANY EXPENSE, LOSS, OR DAMAGE THAT IS NOT REASONABLY FORESEEABLE.

c. Indemnification

Unless prohibited by applicable law, if you are a business, you will defend and indemnify BuildingTransparency, and its affiliates, directors, officers, employees, and users, against all liabilities, damages, losses, costs, fees (including legal fees), and expenses relating to any allegation or third-party legal proceeding to the extent arising from:

1. your misuse or your end user’s misuse of the APIs;
2. your violation or your end user’s violation of the Terms; or
3. any content or data routed into or used with the APIs by you, those acting on your behalf, or your end users.

Section 11: General Provisions

a. Modification

We may modify the Terms or any portion to, for example, reflect changes to the law or changes to our APIs. You should look at the Terms regularly. We’ll post notice of modifications to the Terms within the documentation of each applicable API, to this website, and/or in the GitHub documentation. Changes will not apply retroactively and will become effective no sooner than 30 days after they are posted. But changes addressing new functions for an API or changes made for legal reasons will be effective immediately. If you do not agree to the modified Terms for an API, you should discontinue your use of that API. Your continued use of the API constitutes your acceptance of the modified Terms.

b. U.S. Federal Agency Entities

The APIs were developed solely at private expense and are commercial computer software and related documentation within the meaning of the applicable U.S. Federal Acquisition Regulation and agency supplements thereto.

c. General Legal Terms

We each agree to contract in the English language. If we provide a translation of the Terms, we do so for your convenience only and the English Terms will solely govern our relationship. The Terms do not create any third party beneficiary rights or any agency, partnership, or joint venture. Nothing in the Terms will limit either party’s ability to seek injunctive relief. We are not liable for failure or delay in performance to the extent caused by circumstances beyond our reasonable control. If you do not comply with the Terms, and BuildingTransparency does not take action right away, this does not mean that BuildingTransparency is giving up any rights that it may have (such as taking action in the future). If it turns out that a particular term is not enforceable, this will not affect any other terms. The Terms are the entire agreement between you and BuildingTransparency relating to its subject and supersede any prior or contemporaneous agreements on that subject. For information about how to contact BuildingTransparency, please visit buildingtransparency.org.

Except as set forth below: (i) the laws of the State of Washington, U.S.A., excluding Washington’s conflict of laws rules, will apply to any disputes arising out of or related to the Terms or the APIs; and (ii) ALL CLAIMS ARISING OUT OF OR RELATING TO THE TERMS OR THE APIS WILL BE LITIGATED EXCLUSIVELY IN THE FEDERAL OR STATE COURTS OF KING COUNTY, WASHINGTON, USA, AND YOU AND BUILDINGTRANSPARENCY CONSENT TO PERSONAL JURISDICTION IN THOSE COURTS.

If you are accepting the Terms on behalf of a United States federal government entity, then the following applies instead of the paragraph above: the laws of the United States of America, excluding its conflict of laws rules, will apply to any disputes arising out of or related to the Terms or the APIs. Solely to the extent permitted by United States Federal law: (i) the laws of the State of Washington (excluding Washington’s conflict of laws rules) will apply in the absence of applicable federal law; and (ii) FOR ALL CLAIMS ARISING OUT OF OR RELATING TO THE TERMS OR THE APIS, THE PARTIES CONSENT TO PERSONAL JURISDICTION IN, AND THE EXCLUSIVE VENUE OF, THE COURTS IN KING COUNTY, WASHINGTON.

If you are accepting the Terms on behalf of a United States city, county, or state government entity, then the following applies instead of the paragraph above: the parties agree to remain silent regarding governing law and venue.