Skip to Content
IntegrationsRock RMS

Rock RMS

Connecting Rock RMS to Bellwether uses an API key. You’ll generate a key in Rock, paste it into Bellwether, and the connection is live.

Before You Start

You’ll need:

  • Administrator access to your Rock RMS instance
  • Your Rock RMS base URL — the URL you use to access Rock (e.g., https://rock.yourchurch.com)

Creating an API Key in Rock RMS

  1. Open Rock Admin. Sign in to your Rock RMS instance and go to Admin Tools → Security → REST Controllers.

  2. Create a new REST key. Click Add Key (or navigate to the REST Keys page, depending on your Rock version).

  3. Name the key. Something like “Bellwether” or “Bellwether Integration” so you can identify it later.

  4. Set permissions. The key needs read access to:

    • People
    • Groups
    • Group Members
    • Attendance
    • Schedules

    Bellwether only needs read access. Do not grant write permissions.

  5. Save and copy the key. Once created, copy the API key value. You’ll paste this into Bellwether in the next step.

Connecting in Bellwether

  1. Open Integrations. From your Bellwether dashboard, go to Settings → Integrations.

  2. Click Connect next to Rock RMS.

  3. Enter your details:

    • API Key — Paste the key you generated in Rock.
    • Base URL — Enter your Rock RMS URL, including the protocol (e.g., https://rock.yourchurch.com).

  4. Click Connect. Bellwether will verify the connection by making a test request to your Rock instance. If successful, you’ll see a green “Connected” badge.

What Data Is Accessed

Once connected, Bellwether can read:

  • People — Names, emails, phone numbers, connection status, and person attributes
  • Groups — Group rosters, group types, and membership details
  • Attendance — Attendance records for services, groups, and events
  • Schedules — Service schedules and volunteer assignments

This is read-only access. Bellwether cannot create, edit, or delete any records in your Rock RMS instance.

Disconnecting

Go to Settings → Integrations and click Disconnect next to Rock RMS. This deletes the stored API key from Bellwether’s servers. You can reconnect at any time with a new (or the same) key.

Troubleshooting

“API key rejected” — Double-check that the key is active in Rock and hasn’t been revoked. Also verify that your base URL includes https:// and doesn’t have a trailing slash.

“Connection failed” or timeout — Make sure your Rock RMS instance is accessible from the internet. On-premise installations behind a firewall may need a network configuration change to allow Bellwether’s servers to reach the Rock API.

Data seems incomplete — Verify the API key’s permissions in Rock. If the key doesn’t have access to a specific entity type (like Attendance), Bellwether won’t be able to read that data.

Last updated on
Planning CenterOverview