# Ruuster API Terms of Use

Source: https://help.ruuster.com/api/terms

> The Ruuster API Terms of Use, which govern all use of the API.

**Effective October 5, 2026. Last updated October 27, 2026** (storage in your own systems, sharing a home's data with your clients and leads, and public records: Sections 4.1, 4.3 and 6.4)

These Ruuster API Terms of Use (the "API Terms") govern access to and use of the Ruuster application
programming interface. They are entered into between Ruuster Inc., a Delaware corporation
("Ruuster", "we"), and the brokerage or real estate team that is enabled to use the API ("Customer",
"you").

## 1. Scope and acceptance

**1.1 Supplement to your agreement.** These API Terms supplement your existing subscription agreement
with Ruuster (the "Agreement"). If they conflict, these API Terms control for the API only; the
Agreement controls for everything else, including fees, governing law and limitation of liability,
except where Section 9 says otherwise.

**1.2 Incorporation.** These API Terms are incorporated into the Agreement by reference and apply to
any use of the API. No separate acceptance is required. An Authorized User who uses the API confirms
that they are authorized to act for Customer.

**1.3 Responsibility for use.** You are responsible for all use of the API made with your Authorized
Users' credentials, and for your service providers' compliance with these API Terms.

## 2. Definitions

| Term | Meaning |
|---|---|
| **API** | The Ruuster application programming interface at api.ruuster.com, its webhooks and event feed, and the Documentation. |
| **Documentation** | The guides and reference published at help.ruuster.com/api, as updated from time to time. |
| **Authorized User** | An owner or administrator of Customer's Ruuster account. Agent accounts cannot use the API. |
| **Credentials** | An Authorized User's API key and login email, and any webhook signing secret. |
| **API Data** | All data returned by the API or sent by its webhooks, including Lead Data, Listing Data, Public Record Data and Analytics Data. |
| **Lead Data** | Information about Customer's leads and clients, including names, CRM identifiers, activity on Ruuster sites, email engagement and, when enabled, email addresses and phone numbers. |
| **Listing Data** | Listing information that originates from a multiple listing service (MLS) or similar source. |
| **Public Record Data** | Property information that originates from county and other public records, including parcel, assessment, tax, deed, mortgage, valuation and owner information. |
| **Analytics Data** | Aggregated traffic and engagement measurements, including figures derived from Google Analytics. |
| **Integration** | Customer's software, workflows or services that call the API or receive its webhooks. |

## 3. Access

**3.1 Enablement.** API access is available only to brokerages that Ruuster has enabled. Ruuster may
decline or delay enablement at its discretion, including until listing attribution for your agents is
configured.

**3.2 Who may call.** Only Authorized Users may use the API, each with their own Credentials.
Credentials may not be shared between people or used by agents.

**3.3 Lead contact details.** Lead email addresses and phone numbers are returned when Ruuster turns
them on for your brokerage under the Agreement. You may ask Ruuster to turn them off at any time.

## 4. License and restrictions

**4.1 License.** Subject to these API Terms, Ruuster grants you a limited, non-exclusive,
non-transferable, non-sublicensable, revocable license to use the API and API Data for your own
internal business purposes in operating your real estate brokerage, such as seller reporting,
marketing analysis and following up with your own leads. This includes storing API Data in your own
CRM and other internal systems to enhance your own contact records, and using it to serve and market
to your own clients and leads. API Data may be used only by you, your agents and your staff, inside
your own systems, and by a service provider under 4.2. You may also share API Data about a particular
home with your own clients and leads, for example in a home value estimate (AVM), CMA, seller report or
listing presentation, each person receiving information about the homes that concern them, and never
as a bulk list or export.

**4.2 Service providers.** You may let a service provider (for example a reporting or data warehouse
vendor, or an automation tool) process API Data on your behalf, provided it is bound by written
obligations at least as protective as these API Terms and uses the data only for you.

**4.3 Restrictions.** You will not, and will not let anyone else:

- (a) sell, resell, rent, license or otherwise make API Data available to a third party, except to a
  service provider under 4.2, to your own clients and leads about a particular home under 4.1, or as
  required by law;
- (b) use the API or API Data to build or improve a product that competes with Ruuster, or to train a
  machine-learning model that is offered to anyone other than you;
- (c) access data of any brokerage other than your own, or try to;
- (d) exceed or circumvent rate limits, quotas or access controls, including by using several
  Credentials to multiply limits;
- (e) call the API from a web browser, mobile app or other client-side code, or embed Credentials
  where others can read them;
- (f) probe, scan or test the API's security, or reverse engineer it, except with Ruuster's written
  permission;
- (g) use API Data to send messages or make calls that do not comply with applicable law, including
  the laws listed in Section 5.3;
- (h) use the API in a way that harms Ruuster, its other customers or the people whose data it holds;
- (i) re-aggregate, compile or combine API Data into a dataset, database or list for anyone other than
  your own brokerage;
- (j) use API Data in, or to build or improve, any product or service that is sold, licensed,
  subscribed to or otherwise monetized, other than the real estate brokerage services you provide to
  your own clients;
- (k) give API Data to, or make it available through, any other user, brokerage or end user, except
  sharing data about a particular home with your own clients and leads under 4.1;
- (l) pull, export or compile API Data in bulk. Public Record Data is provided one property at a time,
  for looking up your own clients' and leads' homes.

**4.4 Ownership.** Ruuster owns the API, the Documentation and all related intellectual property. As
between the parties, you own your Lead Data, including your leads' engagement data, and you grant
Ruuster the rights it needs to provide the API. Ruuster may use feedback about the API without
obligation.

## 5. Lead data and privacy

**5.1 Roles.** For Lead Data you receive through the API, you decide how it is used. You are
responsible for having a lawful basis and any notices or consents required to receive and use it.

**5.2 Protection.** You will protect API Data with administrative, technical and physical safeguards
at least as strong as those you use for your CRM data, and limit access to people who need it.

**5.3 Compliance.** You will comply with all laws that apply to your use of Lead Data, which may
include the CAN-SPAM Act, the Telephone Consumer Protection Act, U.S. state privacy laws, Canada's
Anti-Spam Legislation, PIPEDA and provincial privacy laws.

**5.4 Incidents.** If you learn that API Data or Credentials have been accessed without
authorization, you will tell Ruuster at support@ruuster.com promptly and cooperate with Ruuster's
response.

**5.5 Deletion.** When the law requires it, you will delete Lead Data obtained through the API,
including when a person exercises a deletion right.

**5.6 Where data is processed.** Ruuster and its service providers store and process API Data,
including data about Canadian brokerages and their leads, in the United States. While there, it is
subject to U.S. law and may be accessible to courts, law enforcement and national security
authorities of the United States. You are responsible for any notice your own customers need about
the transfer of their information to your systems and service providers.

## 6. Listing data

**6.1 MLS rules.** Listing Data is subject to the rules and licenses of the MLS that supplied it. You
must use Listing Data obtained through the API in full compliance with the rules of that MLS,
including its rules on display, distribution and storage. You are solely responsible for that
compliance.

**6.2 Changes for MLS compliance.** Ruuster may remove or limit Listing Data fields, or stop returning
listings that are not attributed to your brokerage, if an MLS requires it or Ruuster believes it is
needed to comply with an MLS rule.

**6.3 Attribution.** Listings are attributed to your brokerage from the MLS identifiers on your
agents' Ruuster profiles and any offices Ruuster has confirmed as yours. You are responsible for
keeping your agents' MLS identifiers accurate.

**6.4 Public Record Data.** Public Record Data is subject to the licenses of the providers that supply
it to Ruuster, and to Sections 4.1 and 4.3. It is available only for homes in the states your
brokerage's MLSs cover. In addition, you will not:

- (a) use owner names, mailing addresses or other owner details to contact anyone who has asked not to
  be solicited;
- (b) use Public Record Data as, or in a way that makes it, a consumer report under the Fair Credit
  Reporting Act or a similar law, including to decide anyone's eligibility for credit, insurance,
  employment or housing;
- (c) use Public Record Data as a substitute for a title, vesting, ownership or encumbrance report.

Public records arrive in periodic loads and may lag recording by about two months. Loan balances and
the status of recorded mortgages are estimates.

## 7. Credentials and security

**7.1 Keep them secret.** You will keep Credentials confidential, store them in a secrets manager or
equivalent, send them only over HTTPS, and use them only from servers you or your service providers
control.

**7.2 Compromise.** If Credentials may have been exposed, contact Ruuster at support@ruuster.com
straight away. Ruuster will block the exposed key and regenerate a new one for you.

**7.3 Departing users.** When an Authorized User leaves your brokerage or no longer needs access,
remove them in Ruuster; their Credentials stop working shortly after.

**7.4 Webhook endpoints.** You are responsible for the security of the URLs you register for
webhooks, including verifying Ruuster's signature on every delivery as described in the
Documentation.

## 8. Limits, webhooks and changes

**8.1 Limits.** Use of the API is subject to the rate limits, payload limits and daily quotas in the
Documentation. Ruuster may change them, apply lower limits to a particular Integration that is
degrading the service, or raise them at your request.

**8.2 Webhooks.** Webhook deliveries are made at least once, without ordering guarantees, typically
within minutes. Ruuster may pause or disable a subscription whose endpoint fails repeatedly or
answers in a way that burdens the service. Events are kept for 30 days for replay and the event feed.

**8.3 Changes.** Ruuster may add features, fields and endpoints at any time. Ruuster will give at
least 90 days' notice, in the changelog in the Documentation and by email to Authorized Users, before
removing a field or endpoint or changing it in a way that breaks existing Integrations, except where
a shorter period is required for security, legal or MLS compliance reasons.

**8.4 Discontinuation.** Ruuster may modify, suspend or discontinue the API, in whole or in part, at
any time and without notice. Section 8.3 does not limit this right.

## 9. Accuracy, availability and liability

**9.1 Nature of the data.** API Data reflects what Ruuster records and what third-party analytics
services measure, each with its own methods and limits described in the Documentation. Figures may be
estimates, may change as late data arrives, and exclude visitors who block analytics. API Data is not
an audited record. You are responsible for how you present API Data to sellers or others, and you
will not describe it as guaranteed or complete.

**9.2 Availability.** The API is provided without a service level commitment. Ruuster may pause it
for maintenance or to protect the service, and will try to give advance notice of planned pauses.

**9.3 As is.** The API and API Data are provided entirely "as is" and "as available", without
warranties of any kind, express or implied, including merchantability, fitness for a particular
purpose, accuracy, availability and non-infringement. You use the API at your own risk.

**9.4 No liability.** To the maximum extent permitted by law, Ruuster, its affiliates and their
officers, employees and agents will have no liability of any kind arising out of or relating to the
API, API Data or these API Terms, whether in contract, tort, negligence or otherwise, including for
lost profits, lost data, business interruption or indirect, incidental, special or consequential
damages, even if advised of their possibility.

**9.5 Your indemnity.** You will defend and indemnify Ruuster against third-party claims arising from
your or your service providers' use of API Data in breach of these API Terms or applicable law,
including claims by leads, MLSs or regulators.

## 10. Suspension, termination and general

**10.1 Suspension.** Ruuster may suspend or limit API access, block Credentials or pause webhooks
immediately if it reasonably believes there is a security risk, a breach of these API Terms, a risk
to the service or other customers, or a legal or MLS requirement. Ruuster will tell you the reason
when it lawfully can and restore access once the issue is resolved.

**10.2 Termination.** Either party may end API access at any time. API access ends automatically when
the Agreement ends. Sections 4.3, 4.4, 5, 6.1, 6.4, 9 and 10 survive.

**10.3 Changes to these API Terms.** Ruuster may update these API Terms at any time. Updates take
effect when they are published in the Documentation, and Ruuster will tell Authorized Users by email.
Continued use after an update is acceptance.

**10.4 General.** Governing law, venue, notices and assignment follow the Agreement. Questions:
support@ruuster.com.