What is Raptor?
Raptor Technologies is a leading school safety platform used in K-12 environments for emergency management, visitor screening, and accountability. Integrating Raptor with Genea allows your campus to synchronize emergency actions across both systems. Eg: A lockdown triggered in Raptor can automatically lock doors via Genea, and a Genea Emergency Plan can instantly appear in Raptor for staff alerts and first responder notifications.
What this integration does?
Raptor → Genea: When an emergency is started in Raptor, Genea triggers the mapped Emergency Plan(s) for the matching building/location.
Genea → Raptor: When you trigger a Genea Emergency Plan, Genea creates the corresponding Raptor incident.
Setting Up Your Genea + Raptor Integration
1. Generating API Keys from Genea Portal
1. Generating API Keys from Genea Portal
Navigate to the 'API Keys' tab in your Genea admin Global Overview Page.
Scroll down and find the 'Raptor' in 'Integration Management' section, click the radio button corresponding to Raptor to give it full access.
Click 'Save', and a dialogue box showing the gnerated API Key will appear, copy this API Key and keep it handy.
Note: Once closed you cannot see the API and would need to re-generate the API Key.
2. Configuring Raptor (via Raptor Customer Success)
2. Configuring Raptor (via Raptor Customer Success)
Raptor setup is not customer facing currently, they handle this for you and provide you with all the details needed to login.
To complete the integration, you’ll need to reach out to Raptor Customer Success or your Raptor Implementation Manager.
Their team will handle all configuration on your behalf and provide you with the credentials and IDs needed to finish setup in Genea.
Hand them the API Key you generated in above step and they'll handle everything mentioned below.
Once you contact Raptor Support, they will:
Create Client Credentials : Generate your Client ID, Client Secret, and Client UID.
Configure Building UIDs : Identify each school or facility’s unique Raptor Building UID.
Configure Template UIDs : Map emergency types (e.g., Lockdown, Evacuation, Shelter in Place) to their internal template IDs.
Set Up Webhooks : Establish the secure webhook connection from Raptor Alert -> Genea for incident initiation and closure.
Validate Connectivity : Confirm communication between your Raptor account and Genea is successful.
Tip: When contacting Raptor, mention that you’re enabling the Genea Emergency Sync Integration so their team can locate the correct configuration faster.
Configuring Raptor (Can skip if Raptor Customer Success is helping with the setup)
Configuring Raptor (Can skip if Raptor Customer Success is helping with the setup)
Login to your Raptor Portal
Go to Raptor Connect -> Credentials Tab in Admin Nav Menu and Click on Add Credentials
Give a name to your credential, slect Credential Type as 'API Key', paste the API Key that you generated from Genea Portal in the API Key input box and re-enter it to confirm in the confirm API Key input box.
In API Key Header input box write 'Authorization'. And click on 'Save'.
Next go to 'Configurations' Tab in Raptor Connect, click on 'Add Configuration' and Enter the following details:
Event Information:
Configuration Type: Emergency
Preset Configuration Template: <Optional>
Name: Display name of the Configuration that you want to show.
Credential: Select the one we created in the above step while creating a new credential.
Method: POST
Destination URL: paste the exact following text.
https://api-safety-management.sequr.io/v1/integrations/raptor/emergencies
Rules:
Building Selection: Select 'All buildings' or select the buildings that you want to integrate.
Select Emergency Type: Select 'All Emergencies' or manually select the Emergencies that you want to integrate.
Select Optional Emergency Subtype: <Optional>
Select Optional Status: Can be left blank or select 'All statuses' if you want to communicate about all statuses or else you could go with only 'Initiated' or 'Resolved' status as well.
Payload: paste the exact following text (Make sure that letter case and marks are exactly matching the below text).
{
"client_uid": "{# CLIENT_ID #}",
"building_uid": "{# BUILDING_ID #}",
"incident_uid": "{# INCIDENT_ID #}",
"incident_status": "{# INCIDENT_STATUS #}",
"incident_type_name": "{# INCIDENT_TYPENAME #}",
"emergency_subtype": "{# INCIDENT_SUBTYPENAME #}",
"incident_source": "{# INCIDENT_SOURCE #}",
"first_name": "{# INCIDENT_PERSON_FIRSTNAME #}",
"last_name": "{# INCIDENT_PERSON_LAST_NAME #}",
"incident_initiated_timestamp": "{# INCIDENT_INITIATED_TIMESTAMP #}",
"incident_resolved_timestamp": "{# INCIDENT_RESOLVED_TIMESTAMP #}"
}Content Type: paste the exact following text
application/json
Status: Select Active
Leave the Custom Headers section
Click on 'Save'
The Raptor Setup for the Integration is now completed
3. Installing and Setting up Raptor in Genea Platform
3. Installing and Setting up Raptor in Genea Platform
Installing Raptor Integrations
Navigate to the 'Integrations' tab in your Genea Global Overview Portal.
Scroll down to Emergency Management section and Click on 'Install' under Raptor thumbnail.
You will get the following Information to Authenticate Genea <-> Raptor Integration.
Client Id
Client Secret
Client UIDNote: Reach out to Raptor team in case you haven't received these credentials. Copy/paste values exactly as provided by Raptor. Avoid leading/trailing spaces.
And click on 'Install' (If credentials are invalid, you’ll see an error).
Map buildings (Raptor → Genea locations)
In the 'Building Mapping' section of Raptor Emergency Integration Page, click on 'Fetch'.
Upon fetching, if there is any new building addition, deletion or update on Raptor's portal it'll appear in the dialogue box below. Click on 'Confirm and Sync Changes'.
Note: Once the building mapping Sync is updated it cannot be changed, and the buildings will be synced to current Raptor configurations while the old mapping will be updated.
Click on 'Add Building Mapping', and from the drop down select the 'Raptor Building Name' and corresponding 'Genea Location Name', and click save. You can also edit and delete the existing mappings.
Notes:You can add multiple mappings.
You can only map one Genea Location for every Raptor Buliding.
If a building isn’t mapped, inbound Raptor events for that building will be ignored.
Map Emergency Templates
In the 'Template Mapping' section of Raptor Emergency Integration Page, click on 'Fetch'.
Upon fetching, if there is any new Raptor Emergency Template addition, deletion or update on Raptor's portal it'll appear in the dialogue box below. Click on 'Confirm and Sync Changes'.
Note: Once the Template mapping Sync is updated it cannot be changed, and the Raptor Emergency Templates will be synced to current Raptor configurations, while the old mappings will be updated.
Click on 'Add Template Mapping', and from the drop down select the 'Raptor Template Name' (configured in Raptor portal eg: Lockdown, Evacuation etc) and corresponding 'Genea Emergency Plans', and click save. You can also edit and delete the existing mappings and enable/disable the mappings.
Notes:One Raptor Template → Many Genea Plans is supported (e.g., “Evacuate” can trigger Default Emergency Lockdown + Floor-specific plans).
Mapping is per account (your tenant). Reuse across buildings by pairing with Building Mapping.
If no template mapping exists, Genea won’t trigger any plan.
The Integration is completed from both Genea's and Raptor's end.
Setting Up Emergency Plans
Emergency Plans in Genea allow you to lock down or hold open doors across your property, trigger a physical device etc in response to critical events. Each plan defines:
Which doors and control points are included (e.g., all classroom doors).
What trigger states apply (Lockdown, Hold Open, etc.).
Optional physical triggers or schedules to automatically activate plans.
Exemptions for certain access groups (e.g., first responders, medical staff).
When paired with Raptor, these Emergency Plans can be invoked automatically when Raptor sends an incident trigger, or used to trigger alerts back into Raptor.
To learn how to create and configure Emergency Plans in Genea, see our full guide: How to Create Emergency Plans in Genea.
You can also access Emergency Plans in Interactive Floor Plans which is designed to facilitate swift and intuitive management of emergency plans. To learn more about this feature visit Managing Emergencies Through Interactive Floor Plans.
Testing the Integration
Test Raptor → Genea
In Raptor, start an incident (e.g: Evacuation) for a mapped Building.
In Genea, verify the mapped Emergency Plan(s) triggered for that Location.
You can check invocation logs of the Emergency plan and also see that the Emergency plan was triggered by Raptor in the View Notes.
Now you can revert the Emergency plan from the Raptor Portal.
You'll see the status of Emergency Plan going from Emergency to Normal state and also see the exact details in Invocation Logs.
Note: If a Raptor emergency is reverted, then all Genea emergencies mapped to the same template and building will also be reverted, regardless of which action originally triggered the emergency even if the emergency was not triggered from Raptor.
Test Genea → Raptor
In Genea, Trigger an Emergency Plan that you mapped to a Raptor Template.
In Raptor, verify the mapped Emergency Template triggered for that Location.
Note: You won't see the system triggering each other in case the building and template mapping is not correctly configured in Genea Integration page.
Viewing Logs & History
The Genea↔Raptor integration provides multiple log views so administrators can track and troubleshoot all emergency sync activity.
1. Event Logs (Location View)
All Raptor-initiated and Genea-triggered events appear in the Event Logs (Select Location -> 'Activity' Menu from Navbar -> 'Event Logs' Tab) section of Location Overview.
Here you can see:
Event Description (e.g., Evacuate, Lockdown, Shelter)
Raptor User Name and Source
Emergency Sub-Type (if provided by Raptor)
2. Audit Logs (Location View)
Audit Logs provide a detailed history of status changes for Emergency Plans. You can locate it in Audit Logs (Select Location > 'Activity' Menu from Navbar > 'Audit Logs' Tab) section of Location Overview. Each record includes:
Who triggered/reverted the plan (System or User)
Old vs. New snapshot of plan state
Event timestamps and Data ID for support/debugging
On clicking on view details you can also see changes in audit logs via a snap based comparison.
3. Raptor Integration Page → Event Logs (Global Overview)
The Raptor integration tile in Integrations > Emergency Management > Raptor includes its own Event Logs tab.
This shows the same events visible in Event Logs, but scoped specifically to Raptor integration activity.
Helpful if you only want to filter down to Raptor-related syncs.
4. Emergency Plan Invocation Logs (Global Overview)
Each Emergency Plan in Genea maintains its own Invocation Logs ('Global Overview' > 'Emergency Plans' Nav menu > Select the Emergency Plan > 'Details' Tab > 'Invocation Logs' Section)
This lets you track:
Which plan was triggered
Who triggered/reverted it
Execution status (Successful, Failed, In Progress)
Time of execution
Common Issues & Troubleshooting
“Unable to install Raptor Emergency Sync. Please verify your credentials.”
Client ID/Secret/Client UID don’t match Raptor records.
Confirm you’re using production credentials.
Try pasting into a plain text editor first to strip hidden characters and avoid including extra spaces in the input field.
Raptor event didn’t trigger a Genea plan
Building not mapped → add mapping under Building Mapping.
Template not mapped → map the Raptor Template to at least one Genea Emergency Plan.
Check Invocation Logs for Failed entries.
Genea plan triggered, but no incident appeared in Raptor
Ask your Raptor Admin to confirm the Template UID is valid for that client.
Ensure production auth is reachable and the token is valid.
Can I end/revert an emergency from Genea?
Only if Raptor exposes a corresponding “end incident” API (Currently not possible). If not, end it from Raptor; Genea will continue to show plan status per your plan configuration (Trigger/Revert).
We see intermittent failures
Re-try the action. If it persists, export Invocation Logs and Audit Log Data ID and contact support.
Expected Behavior & Assumptions
One active emergency per building
Raptor only allows one active incident per building at a time. Starting a new one may require ending the current incident first.Mappings required
Every event needs both a Building UID ↔ Location and a Template UID ↔ Emergency Plan mapping. Without both, the event will be ignored.Multi-template mapping supported
One Raptor Template can be mapped to multiple Genea Emergency Plans. All mapped plans will be triggered, but execution order is not guaranteed. If one plan is already active or invalid, others will still attempt to run.Revert behavior
If a Raptor emergency is ended, all linked Genea Emergency Plans (for that building/template) will also be reverted, regardless of what triggered those Genea Emergency plans in the first place.Permissions
Only Global Admins can install/manage the integration.
Only roles with Trigger/Revert access can operate plans in the Emergency Plans page.
Read access for Emergency Management automatically includes read access for Emergency Plans. However, if a user lacks access to Audit Logs, they will not see Raptor event logs in the integration page.
Error handling
If Raptor sends a trigger for an already-active plan, Genea returns a 204 (No Content) - not an error.
If multiple plans are mapped and some fail, the rest still execute. The event is logged once with overall status.
Raptor only receives an error if validation, authentication, authorization, or an internal server error occurs.
Time zones
Events in Genea are shown in your account’s configured time zone. Raptor may use UTC timestamps in payloads.
Need Help?
If you have any questions about this integration, or have any feature requests, please reach out to acsupport@getgenea.com.
Explore more at: help.getgenea.com