Data Sources

NOTE: Most data sources behave the same way in the RAD-e API response. For that reason, you may not see examples of all of our data sources

  • In general, most B2B Tech Partners will provide data in a format similar to what's documented here

911 Inform

911 Inform Data can be queried by phone number and will always be associated with a live 911 call.

Use Case

When a query for 911 Inform data is made by phone number (tel://{phone_number}), the call taker should be presented with information enabling them to link out to the 911 Inform command center, allowing them to control the 911 Inform connected building.

911 Inform can be used in tandem with RapidSOS' /spatial-layers endpoint to enable visualization of the connected 911 Inform buildings. However all other functionality is available via the RAD Enhanced endpoint.

Test Numbers

  • Phone number: 12222222221

API Response

911 Inform data returned under the 911_inform key.

If no data is returned by the request, there will be no data returned in the payload.

911Secure

911Secure Data can be queried by phone number and will always be associated with a live 911 call.

Use Case

This solution connects user-specific location information from an Avaya Enterprise device (commercial network) routed through Sentry VPC (automatic dynamic 911 call routing) with 911 through the RapidSOS platform. When a query for 911Secure data is made by phone number (tel://{phone_number}), the call taker should be presented with the list of returned 911Secure records, which can then be shown to the call taker.

Test Numbers

  • Phone number: 15555555551

API Response

911Secure data is returned under the 911secure key.

If no data is returned by the request, there will be no data returned in the payload.

Cove

Cove Home Security provides home security systems for the DIY space. Cove Data can be queried by phone number and will always be associated with a live 911 call.

Use Case

Call routing is established from the alarm panel to the monitoring center, which provides emergency contacts for alarm validation.

Additionally, this allows the Monitoring Center the ability to route to the correct PSAP for the home in an emergency, and provides a location and Data to the PSAP.

Test Numbers

  • Phone number: 15555555556

API Response

Cove data is returned under the cove key.

If no data is returned by the request, there will be no data returned in the payload.

Emergency Health Profile

Emergency Health Profile Association medical Data can be queried by phone number and will always be associated with a live 911 call.

Use Case

Emergency Health Profile Association can provide device user's profile, medical information, COVID-19-related information, and emergency contacts. This profile data has been filled out by the user on emergencyprofile.org.

Test Numbers

  • Phone number: 15555555552

API Response

Emergency Health Profile Association data returned under the emergency_health_association key.

If no data is returned by the request, there will be no data returned in the payload.

IMPORTANT: All requests should be placed at least twice to ensure that there is no data available.

MedicAlert

MedicAlert Data can be queried by phone number or by the member's MedicAlert ID (referred to in API calls as 'maf-id'). More than one profile may be returned when querying by phone number, so to protect the privacy of MedicAlert members, queries by phone number will return a list containing MedicAlert Candidate records. These contain just enough information for a call-taker to uniquely identify the caller - name, gender, and MedicAlert ID. Queries by a valid MedicAlert ID will always return a single MedicAlert Profile record containing a complete profile.

Use Case

When a query for MedicAlert data is made by phone number, the call taker should be presented with the list of returned MedicAlert Candidate records and select the one matching the caller. The MedicAlert ID of the selected candidate should then be used to query for the complete profile, which can then be shown to the call taker.

Test Numbers

  • Phone number: 14085555557
  • MedicAlert account number: 50673864608

API Request

Request body for request by MedicAlert ID:

API Response

MedicAlert data returned under the medicalert key.

IMPORTANT: All requests should be placed at least twice to ensure that there is no data available.

The full response structure is:

  • medicalert
    • data
      • candidates
        • list of candidates
      • profile
        • profile_data

*If no data is returned by the request, the value of *
data is set to null i.e.:

  • medicalert
    • data
      • null

Exceptions

  • MedicAlert currently uses phone numbers +10000000000 through +19999999999 (e.g., 000-000-0000, 111-111-1111, etc.)as placeholders for customers who do not have an active phone number.
    • We recommend when leveraging this API, including exceptions for these "phone numbers" to avoid querying against them and receiving erroneous data.
    • This functionality should be built into the code developed for a customer using MedicAlert data on production.
  • If a production number is needed with non-live data please use 15555555557 or maf_id 50673864608 or 79950438355.

Examples

MedicAlert Candidates

MedicAlert Profile

MedicAlert Profile

MedicAlert - No Data Returned

SiriusXM

SiriusXM Data can be queried by phone number and will always be associated with a live 911 call.

Use Case

SiriusXM is an API for receiving location information for consumption by 911 call takers in handling vehicle crash related emergencies. SiriusXM includes additional data in location payloads, where available. This information is sent from both the SiriusXM vehicle, and SiriusXM equipped devices.

Information sent can include vehicle details such as vin, make, model, year, color, speed, as well as additional values. When a query for SiriusXM data is made by phone number, the call taker should be presented with the list of returned SiriusXM records, which can then be shown to the call taker.

Test Numbers

  • Phone number: 12222222213

API Response

SiriusXM data is returned under the sxm key.

If no data is returned by the request, there will be no data returned in the payload.

Uber

Uber Data can be queried by phone number and will always be associated with a live 911 call.

Uber provides information to ECCs through the RapidSOS emergency response data platform from 9-1-1 calls made through the Safety Toolkit (Blue Shield) inside the Uber App.

Use Case

When a query for Uber data is made by phone number (tel://{phone_number}), the call taker should be presented with information relating to the incident occurring for the caller's Uber enabled location.

Test Numbers

  • Phone number: 15555555515

API Response

Uber data is returned under the uber key.

If no data is returned by the request, there will be no data returned in the payload.

Other Data Sources

  • Default test number
    • Phone number: 15555555555
  • Location-only test number
    • Phone number: 14444444444
  • Chick-fil-A App Test Number
    • Phone number: 15555555559
  • ZeroEyes App Test Number
    • Phone number: 15555555554
  • Amazon GSOC Test Number
    • Phone number: 15555555511
  • Brave Test Number
    • Phone number: 15555555549
  • Farmers Insurance (TrueMotion)Test Number
    • Phone number: 15555555547
  • Lemonade Car Insurance Test Number
    • Phone number: 15555555546
  • Google Additional Data
    • ​​​​​​​Phone number: 13035550149