> ## Documentation Index
> Fetch the complete documentation index at: https://rollout.mintlify.app/llms.txt
> Use this file to discover all available pages before exploring further.

# Introduction

> Universal API + embedded auth for real estate CRMs, TMS, LOS, and email.

<Info>
  **Build integrations in days, not months.** Rollout is the universal API layer for real estate software — connect to every major CRM, TMS, and LOS through a single integration.
</Info>

<div style={{ display: 'flex', justifyContent: 'center', gap: '3rem', flexWrap: 'wrap', padding: '2rem 0', textAlign: 'center' }}>
  <div>
    <div style={{ fontSize: '2.5rem', fontWeight: '700', color: 'var(--primary)' }}>1B+</div>
    <div style={{ fontSize: '0.875rem', opacity: 0.7 }}>API calls per month</div>
  </div>

  <div>
    <div style={{ fontSize: '2.5rem', fontWeight: '700', color: 'var(--primary)' }}>37+</div>
    <div style={{ fontSize: '0.875rem', opacity: 0.7 }}>Supported integrations</div>
  </div>

  <div>
    <div style={{ fontSize: '2.5rem', fontWeight: '700', color: 'var(--primary)' }}>10x</div>
    <div style={{ fontSize: '0.875rem', opacity: 0.7 }}>Target customer ROI</div>
  </div>
</div>

## The Integration Problem in Real Estate and Mortgage

Every real estate software company faces the same challenge: your customers use Follow Up Boss. Or Lofty. Or CINC. Or Sierra Interactive. Or one of dozens of other systems. Each one has a different API, different auth flows, and different data models.

**The traditional approach:**

* Build and maintain integrations one-by-one
* Handle OAuth flows, token refresh, and auth edge cases for each system
* Normalize data models across incompatible schemas while learning painful CRM/TMS/LOS-specific data nuances
* Secure sandbox/test accounts for each integration, which usually requires one-by-one partnerships with each provider
* Debug when upstream APIs change without warning
* Scale your integrations team as customer demands grow

**The Rollout approach:**

* One API, one auth flow, one data model
* We handle the upstream complexity
* You ship features, not integrations

## What is Rollout?

Rollout is a **universal API and embedded authentication layer** purpose-built for real estate software. It connects your product to your customers' CRMs, transaction management systems (TMS), loan origination systems (LOS), and email providers through:

* **A single, normalized REST API** — read and write contacts, transactions, and activities the same way across all systems
* **A drop-in authentication UI** — Rollout Link handles OAuth flows, API key collection, and credential management
* **Real-time sync options** — webhooks for event-driven architectures or Sync to DB for direct database access

<CardGroup cols={2}>
  <Card title="CRMs" icon="users">
    Follow Up Boss, Lofty, CINC, LionDesk, Sierra Interactive, Real Geeks, and more
  </Card>

  <Card title="Transaction Management" icon="file-contract">
    SkySlope, Dotloop, Open to Close, Sisu, ReZEN, and more
  </Card>

  <Card title="Loan Origination" icon="landmark">
    Encompass (ICE), and more
  </Card>

  <Card title="Email" icon="envelope">
    Gmail, Outlook, Constant Contact, and more
  </Card>

  <Card title="Calendar" icon="calendar">
    Google Calendar and more
  </Card>
</CardGroup>

<a href="/contact">Request an integration →</a>

## How it Works

```mermaid theme={null}
sequenceDiagram
    participant Your App
    participant Rollout
    participant CRM/TMS

    Your App->>Rollout: 1. Generate auth token (JWT)
    Rollout-->>Your App: Token returned
    Your App->>Rollout: 2. Render Rollout Link
    Note over Rollout: User connects their CRM
    Rollout-->>Your App: 3. Credential ID returned
    Your App->>Rollout: 4. API calls with credential ID
    Rollout->>CRM/TMS: Normalized request
    CRM/TMS-->>Rollout: Raw response
    Rollout-->>Your App: Normalized response
```

**Five steps to production:**

1. **Generate an auth token** on your server using your Client ID and Client Secret
2. **Embed Rollout Link** — users see a polished UI to connect their accounts
3. **Store the credential ID** returned when they authenticate
4. **Call the Universal API** — one consistent interface regardless of the underlying system
5. **React to changes** via webhooks or Sync to DB

## What You Build vs. What Rollout Handles

<Tabs>
  <Tab title="You Build (~1-2 days)">
    * A server endpoint that mints JWT tokens
    * A frontend page that renders Rollout Link
    * Storage for credential IDs (a single column in your users table)
    * API calls to Rollout's Universal API
    * (Optional) Webhook endpoint for real-time updates
  </Tab>

  <Tab title="Rollout Handles">
    * OAuth 2.0 / API key authentication for every supported system
    * Token refresh, session management, and auth edge cases
    * Access to partner/private endpoints that are not exposed in standard public APIs
    * Provider-by-provider partnership onboarding (legal, security, and commercial), so you avoid 12+ months of one-off integration effort
    * Data normalization across incompatible schemas
    * Webhook reliability controls (signatures, retries, and deduplication)
    * Upstream API changes and version migrations
    * Adding new integrations as your customers request them
  </Tab>
</Tabs>

## What It Looks Like

<Tabs>
  <Tab title="Light mode">
    <img src="https://mintcdn.com/rollout/J3SgtcePtApyhjtP/images/select-integration-dark.png?fit=max&auto=format&n=J3SgtcePtApyhjtP&q=85&s=5ee776a6c7afa43bcf1658698c29dcb5" alt="Select integration grid (light mode)" style={{ borderRadius: "12px" }} width="1262" height="1296" data-path="images/select-integration-dark.png" />
  </Tab>

  <Tab title="Dark mode">
    <img src="https://mintcdn.com/rollout/J3SgtcePtApyhjtP/images/select-integration-light.png?fit=max&auto=format&n=J3SgtcePtApyhjtP&q=85&s=5aa35ed1d8474443b890267baa266b26" alt="Select integration grid (dark mode)" style={{ borderRadius: "12px" }} width="1288" height="1320" data-path="images/select-integration-light.png" />
  </Tab>
</Tabs>

Rollout Link can be embedded as-is with full CSS customization, or you can build your own UI using the [`CredentialForm` component](/advanced-guides/use-your-own-integration-ui-with-the-credentialform-component).

## Security & Compliance

<CardGroup cols={2}>
  <Card title="SOC 2 Type II" icon="shield-check">
    Annual audits covering security, availability, and confidentiality
  </Card>

  <Card title="Data Encryption" icon="key">
    TLS 1.3 in transit, AES-256 at rest for all credentials
  </Card>

  <Card title="Signed Webhooks" icon="signature">
    HMAC SHA-256 signatures on every webhook for authenticity verification
  </Card>

  <Card title="No Browser Secrets" icon="browser">
    JWTs are generated server-side — client secrets never touch the frontend
  </Card>
</CardGroup>

Need enterprise requirements like SLA, DPA, BAA, or data residency? [Contact us](/contact).

## Why Teams Choose Rollout

<AccordionGroup>
  <Accordion title="Faster time-to-market">
    Ship integrations in days instead of weeks or months. Rollout has established partnerships and access to endpoints that are not typically exposed through public APIs, so one integration unlocks all supported systems.
  </Accordion>

  <Accordion title="Reduced engineering burden">
    Stop maintaining auth flows, debugging upstream API changes, and normalizing data. Avoid spending over a year on dedicated one-by-one partnership work with each provider — Rollout handles the complexity so your team can focus on core product.
  </Accordion>

  <Accordion title="Future-proof architecture">
    When a customer asks for a new integration, enable it in Rollout Link without changing your backend. Our Universal API design means zero code changes for new connectors.
  </Accordion>

  <Accordion title="Better user experience">
    Rollout Link provides a consistent, polished auth experience. Users connect accounts in seconds with clear error handling and status feedback.
  </Accordion>
</AccordionGroup>

## Get Started

<CardGroup cols={3}>
  <Card title="Get your API key" href="/getting-started/getting-your-api-key" icon="key">
    Obtain credentials to start building
  </Card>

  <Card title="Show Rollout Link" href="/getting-started/show-the-authentication-ui" icon="link">
    Embed the auth UI in your app
  </Card>

  <Card title="Make API requests" href="/getting-started/making-api-requests" icon="paper-plane">
    Read and write data via the Universal API
  </Card>

  <Card title="Use webhooks" href="/advanced-guides/how-to-use-webhooks" icon="plug">
    React to changes in real-time
  </Card>

  <Card title="Sync to DB" href="/sync-to-db-overview" icon="database">
    Stream data directly to your database
  </Card>

  <Card title="API Reference" href="/api-reference/crm/overview" icon="code">
    Explore endpoints and schemas
  </Card>
</CardGroup>

***

<Card title="Try the Demo" href="/demo-app" icon="play">
  See Rollout in action — connect a test CRM and make API calls in our interactive demo.
</Card>
