Skip to main content
RapidSOS integration gives your dispatchers real-time access to emergency location data, caller device positions, and phone lookup tools directly inside Dispatch CAD. Once you save valid credentials, the platform opens a persistent WebSocket connection for your organization, populates the RapidSOS Locations and RapidSOS Breadcrumbs map layers with live data, and unlocks the Track Phone Number and RapidSOS Lookup dialogs in the Dispatch CAD F4 menu. This page walks you through every step of credential setup, testing, and ongoing maintenance.

​
Who Can Access

Only org-level and platform-level administrators can view or edit RapidSOS credentials. Agency admins and dispatchers do not have access to this page. If RapidSOS Management does not appear in your sidebar, your role does not include access. Contact a Cadmus administrator to have your role reviewed.

​
Open RapidSOS Management

In the Web Admin sidebar, select RapidSOS Management. The direct URL is /rapidsos. The page opens to a credentials table listing every organization you have permission to manage.

​
Credentials Table

The table shows one row per organization and surfaces the following columns at a glance: Use the search or filter bar to locate a specific organization when your table contains many rows. Summary cards above the table may also show a count of configured versus unconfigured tenants.

​
Set Credentials

1

Select the organization

If you manage more than one organization, identify the correct row in the credentials table before proceeding.
2

Open the Set Credentials form

Select Set Credentials in the organization row, or open the row actions menu (⋮) and choose Set Credentials (or Edit if credentials already exist).
3

Complete the credential form

Fill in all required fields. Use the table below as a reference:Refer to the default endpoint values below if the form fields are blank:
Your Cadmus implementer may supply custom WebSocket URLs for special network routing. Use those values if provided, and contact IT if phone lookups succeed but live location tracks fail.
4

Test the credentials (recommended)

Before saving, select Test to validate connectivity. See Test Credentials for details.
5

Save credentials

Select Save. Cadmus stores the secret securely and initiates the WebSocket connection immediately.

​
Test Credentials

Run Test Credentials at any time — before the initial save, after a secret rotation, or when troubleshooting map data gaps. The test checks three services:
  • OAuth token generation — verifies the client ID, secret, and token endpoint are valid.
  • RAD-E API connection — confirms Cadmus can reach the RapidSOS data exchange API.
  • LEI API connection — confirms Cadmus can reach the location intelligence endpoint.
When prompted, enter a test caller ID in E.164 format (for example, +15555550100) to exercise phone-based lookups. The test dialog reports pass or fail for each check individually.
Fix all test failures before putting Production credentials into service. A misconfigured Production credential can prevent dispatchers from receiving emergency location data during live 911 calls.

​
Edit and Delete

Open the row actions menu (⋮) on any organization row to access:
  • Edit — update the client secret, base URL, or token endpoint.
  • Test — re-run the three-service connectivity check without changing any values.
  • Delete — remove the credential record for that environment. Dispatch CAD loses RapidSOS access for that organization immediately and until you add new credentials.

​
Runtime Settings

Each organization has a Runtime Settings panel on the RapidSOS Management page (below or beside the credentials table). These settings are stored in Cadmus and control what the backend and Dispatch CAD actually use — credentials alone are not enough.
1

Open Runtime Settings

On RapidSOS Management, expand Runtime Settings for the target organization and select Edit Settings.
2

Choose environment and dispatch agency

Environment must match saved credentials (Sandbox or Production). Dispatch agency sets the default agency when RapidSOS data creates or enriches incidents for that org.
3

Enable features

Turn on only what your deployment needs:Status badges (RAD-E On/Off, LEI On/Off, EDX On/Off) summarize the current state at a glance.
4

Configure polling (optional)

For demos and sandbox rehearsals:
  • Polling interval (seconds) — minimum 15, maximum 300 (default 30).
  • Configured polling phone numbers — E.164 numbers, one per line (example: +15555555556).
5

Configure EDX (optional)

When EDX is on, set EDX event types as a comma-separated list of RapidSOS event types your org subscribes to.
6

Save

Select Save. The backend refreshes runtime behavior immediately (WebSocket reconnect, polling start/stop).
If LEI is off, dispatchers may see LEI is disabled for this organization when using Track Phone Number. Enable LEI in Runtime Settings after credentials are saved.
Saving or deleting credentials also triggers a runtime refresh so feature toggles and the active environment stay in sync.

​
What Happens After Save

Once credentials are saved and Runtime Settings enable the features you need:
  1. EDX (when enabled) connects the RapidSOS WebSocket and streams real-time alerts to staged map pins.
  2. Configured polling (when enabled with RAD-E) periodically queries demo numbers and stages alerts on the map.
  3. The RapidSOS Locations and RapidSOS Breadcrumbs map layers in Dispatch CAD receive data.
  4. Track Phone Number, RapidSOS Lookup, and Create New CFS from map tooltips become available according to RAD-E/LEI/EDX toggles.
Dispatchers can click a staged pin and use Create New CFS — see Import RapidSOS CFS and Map & Location.

​
Sandbox vs. Production

Use Sandbox credentials for training sessions, demonstrations, go-live rehearsals, and any scenario where you need realistic-looking data without touching real 911 infrastructure. Sandbox returns synthetic test results and never generates real emergency responses.
Never point a Live dispatch organization at Sandbox credentials. Dispatchers will receive synthetic test data instead of real emergency location information, which poses a direct risk to caller safety.
If you maintain separate Sandbox and Live Cadmus organizations, configure credentials in both environments and match each Cadmus org to its correct RapidSOS environment.

​
API Reference

Cadmus exposes the following endpoints for managing RapidSOS credentials programmatically. All paths are scoped to an organization and require an authenticated session with OrgAdmin or CadmusAdmin privileges. Replace {orgId} with the numeric or UUID identifier for your organization, visible in the Web Admin URL when you navigate to your organization record.

​
Troubleshooting

Symptom: The RapidSOS Management link does not appear in the Web Admin sidebar.Checks:
  • Confirm your role is OrgAdmin or CadmusAdmin. AgencyAdmin and Dispatcher roles do not have access.
  • If your role appears correct, contact a CadmusAdmin to verify your role assignment in the system.
Symptom: The credential test reports a failure at the OAuth token step.Checks:
  • Re-enter the Client ID and Client Secret exactly as shown in the RapidSOS portal — leading and trailing spaces cause failures.
  • Verify the Token Endpoint URL matches the environment (Sandbox vs. Production) and has no typos.
  • Confirm the RapidSOS portal account has not expired or been suspended.
Symptom: All three test checks pass, but the RapidSOS Locations layer shows no pins.Checks:
  • Open Runtime Settings and confirm RAD-E, EDX, and/or Configured number polling are enabled for the correct environment.
  • For sandbox demos, add test numbers (e.g. +15555555556) under Configured polling phone numbers and enable Configured number polling.
  • Verify the saved Environment matches the Cadmus org type. Sandbox credentials on a Live org return no real-world location events.
  • Check WebSocket connectivity from the Cadmus server to the WebSocket endpoint. Firewalls or proxies that block wss:// connections will silently drop the stream.
  • Contact IT to confirm outbound WebSocket traffic is permitted on port 443.
Symptom: Dispatcher enters a phone number but tracking fails, or the map previously showed a black screen.Checks:
  • Enable LEI in Runtime Settings for the organization (LEI powers live device location).
  • Enable RAD-E if crash or partner data is also required.
  • Confirm credentials exist for the selected environment.
  • Dispatch CAD should show an on-map message instead of a blank screen when a feature is disabled — if not, update to the latest client build.
Symptom: The RapidSOS Lookup dialog returns data, but incoming location alerts do not automatically create or update incidents.Checks:
  • Auto-incident creation is governed by deployment-level incident rules, not credential configuration. Contact Cadmus support with your org ID to review your rule set.
Symptom: The F4 header menu in Dispatch CAD does not show Track Phone Number or RapidSOS Lookup.Checks:
  • Verify credentials are saved for the correct organization. A dispatcher logged into Org A will not see tools if credentials are only saved for Org B.
  • Confirm the dispatcher’s user account is assigned to the correct org in Web Admin.

​
Verification Checklist

After completing setup, run through these steps before notifying dispatchers that RapidSOS is live:
  1. Credentials saved for the correct organization and environment.
  2. Runtime Settings saved with appropriate RAD-E, LEI, and EDX toggles (and demo polling numbers if using sandbox).
  3. All three checks pass in the Test Credentials dialog (green indicators for token, RAD-E, and LEI).
  4. A dispatcher runs RapidSOS Lookup on a known Sandbox test number and receives data.
  5. The RapidSOS Locations map layer toggles on in Dispatch CAD and displays a staged pin (polling/EDX) or track pin (live LEI).
  6. Clicking a staged pin shows Create New CFS and opens the import form with pre-filled data.
  7. Document the credential rotation date and the name of the RapidSOS portal account owner for future reference.