StationCommand Help Center
Integration Guide

Connect Active911 to StationCommand.

Generate Active911 OAuth credentials, configure API polling and webhook processing, verify end-to-end incident delivery, and understand the optional B.3 tracking/CAD/TTS controls.

Protect your credentials. Your Active911 refresh token and StationCommand webhook secret are credentials. Do not publish them or include them in screenshots.
01

Open the Active911 OAuth token generator

Sign in to Active911 and open:

console.active911.com/interface/dev/oauth_gen.php

Select Read Agency, Read Alerts, Read Responses, Read Devices, and Read Map Data. Leave Write Map Data unchecked.

Active911 OAuth scope selection
02

Select the agency

Choose the agency that belongs to this StationCommand installation and click Submit.

Active911 agency selection
03

Authorize read access

Confirm the agency and requested permissions, then select Yes.

Active911 authorization confirmation
04

Copy the Refresh Token

Active911 generates an Access Token and Refresh Token. StationCommand needs the Refresh Token.

Active911 token results with values hidden
05

Open Administration

Sign in to StationCommand, open Menu, and select Administration.

StationCommand menu
06

Open Integrations

From Administration, select Integrations.

StationCommand Administration workspace
07

Configure Active911 in StationCommand

  • Enable Active911 API.
  • Paste the Refresh Token.
  • Set polling interval and active alert window.
  • Enable Webhook.
  • Generate a new webhook secret.
  • Save Active911 settings.
StationCommand Active911 integration settings
08

Configure Active911 “Other” integration

Copy the complete “Other” Integration URL generated by StationCommand and configure it in Active911 as the third-party destination. Treat the URL as sensitive because it includes the webhook secret.

09

Test and verify

Use Test API / Webhook Processing. Verify Configured, Webhook Enabled, Received, Processed (Live), Errors, Last Received, and Last Processed.

Real webhook test: Active911's Other integration is triggered by dispatch/CAD-fed alerts. A manually created Active911 test alert does not prove third-party webhook delivery.
10

Configure optional B.3 features

Below the core API/webhook controls, B.3.2.0 also includes:

  • Private Incident & EOC Maps — Active911 Device Tracking for apparatus and opt-in responder location markers.
  • CAD Agency / Township Mapping for jurisdiction-aware mapping and Mutual Aid reporting.
  • Audible Incident Announcement (Text-to-Speech) for optional private station-display tone + speech.
  • Station Command Home Integrations for signed incident webhooks and Respond API access.

See Private Device Tracking, Mutual Aid, and the full Active911 section for details.