---
title: "Rapid Response Integration: Configuration"
url: "https://help.psarev.io/en/article/rapid-response-integration-configuration"
language: "en"
last_updated: "2026-07-01T13:23:54.896Z"
---

# Rapid Response Integration: Configuration

| **NOTE:** An authorized user account is required to run this integration. To support better security and audit visibility, we recommend creating a dedicated "service account" user. When configuring this integration, sign in using the service account rather than your personal user account to ensure that audit logs reflect the service account running the integration instead of the user who originally installed it. |
| --- |

Complete the steps below to configure the Rapid Response integration.

| **NOTE:** Before starting the configuration steps below, be sure you have completed the required prerequisite steps. See the [Rapid Response RMM Integration: Prerequisites](https://help.psarev.io/en/article/connectwise-rmm-integration-prerequisites) article for more information. |
| --- |

1.  Click *Admin* on the sidebar menu and select **Integrations Library**.
2.  Click the *Marketplace* tab.
3.  Locate and select the **Rapid Response & Rev.io Data Sync Integration** in the *Alarm Monitoring* section.
4.  Click the **Configure** button.
5.  In the *Rev.io Connection* section, the connection is pre-populated for your environment. Click **Next**.
6.  In the *Rapid Response Connection* section, enter the following credentials you gathered during the prerequisites and click **Connect**:
    -   **Base URL:** the Rapid Response API base URL for your environment:
        -   Production: `https://eastapi.rrms.com/RestAPI/api`
        -   East Dev: `https://eastdevapi.rrms.com/RestAPIDev/api`
        -   West Dev: `https://westdevapi.rrms.com/RestAPIDev/api`
    -   **Username:** the external login username provisioned by your Rapid Response Dealer Support Representative.
    -   **Password:** the password for the Rapid Response external login.
7.  Once connected, click **Next**. In the *Settings* section, enter the following sync values and click **Finish**:
    -   **Dealer Number:** your Rapid Response dealer group number (SiteGroupNum). All synced accounts are linked to this dealer group in Rapid Response.
    -   **Default Device Type:** the panel/device type code applied to new accounts, taken from your Rapid Response account, for example *2GIGCP21*.
    -   **Default Timezone:** the Rapid Response time zone number applied to new accounts, taken from your Rapid Response account, for example *13*.
    -   **Bill Profile:** the Rev.io bill profile assigned to new customers created from Rapid Response sites during the inbound sync. Select from your active Rev.io bill profiles.
8.  The integration will prepare to sync your accounts. Do not leave this page while the initial sync is running. If you need to work elsewhere in the system while the integration syncs, open Rev.io in another browser tab.
9.  Complete the process to match your Rev.io accounts to Rapid Response sites. See the [Integrations Library: Data Sync & Mapping](https://help.psarev.io/en/article/integrations-library-data-sync-mapping) article for more information about reviewing and confirming matches.
10.  After the initial sync, the two-way sync runs automatically on an hourly schedule. Rev.io accounts are pushed to Rapid Response sites at the top of each hour, and Rapid Response sites are synced back to Rev.io at half past the hour.

* * *

## How Records Are Mapped

**Outbound (Rev.io to Rapid Response):** Each Rev.io customer account becomes a Rapid Response site under your dealer group. The customer name, address, and region/state are carried across. The site type is set to residential or commercial based on the customer identity type in Rev.io. The account number is sent as the transmitter code, and your configured default device type and default time zone are applied to new sites.

**Inbound (Rapid Response to Rev.io):** Each Rapid Response site maps to a Rev.io customer. Commercial sites become Business customers and residential sites become Residential customers, with the site name split into first and last name. Addresses are carried across. A site marked cancelled in Rapid Response sets the corresponding customer to a closed status in Rev.io. Sites that are neither commercial nor residential are skipped on the inbound sync.
