Getting Started

Smart911Connect can deliver text or image data to an 9-1-1 center or first responder automatically in the event an emergency call for service is received at a Smart911-enabled PSAP. The platform provides two categories of APIs. The first category is for third parties who wish to provide data along with a 9-1-1 call (content providers). The second category is for third parties to consume the aggregated Smart911Connect data (e.g. call taking or CAD system providers). The platform provides APIs for the pre-registration of key look-up data, for the real-time retrieval and delivery of additional data during a 9-1-1 call or event, and for delivering the data in either HTML or JSON/XML formats. Smart911Connect is optimized for a fast response to the 9-1-1 event. The architecture is designed for high availability, scalability, performance and security.

Technical Overview

Smart911Connect allows disparate sources to provide data to 9-1-1 concurrent with an event (emergency call for service processed by a PSAP). As such, a content provider will need expose an API to Smart911Connect in order for the platform to “pull” data when a triggering event is identified at a PSAP. Once approved, content providers supply an API key to Smart911Connect along with a URI and the required parameter types. Smart911Connect technical support will assist you in setting up a connector to point to your service.

There are a couple of things you need to know before you start developing your integration with Smart911Connect.

1. Determine data to expose and query parameters

You should determine which bits of data you wish to expose to 9-1-1. Also, you should determine the what type of input parameter you need from Smart911Connect to lookup your data (e.g. address, phone number, special field contained in the ALI, combination parameters, etc).

2. Setup your connector with Smart911Connect

Below is a list of items that will be needed to setup a connector in Smart911Connect. After you register, technical support will contact and need the following:

  • Your application key
  • A URI that points to your service
  • The type of data you will need as input to your service
  • The content type of the response (JSON/XML)

Here’s an example of an API request to your service:


Content Provider APIs


In order for the platform to respond quickly to a 9-1-1 event, a registry may be used to store key data points for lookup purposes. This registry will be populated via a secure REST request with data points such as an ANI (unique phone number), or address and a URI mapping. The URI will be used to retrieve details related to the call if a match in the registry exists. The Registry may also be populated via an offline, batch interface.

There may be some providers who may need to a custom input parameter to be used for a lookup. In that case, a premium level will be made available to the provider. The provider will work with the Smart911Connect engineering team to determine the best approach for capturing that data point and making it available.

Retrieval of additional data

Smart911Connect will fetch details from content providers via the exposed URI. Depending on the integration this may occur after a match is made in the registry, or directly with all calls meeting defined criteria. A secure REST request will made via the URI to the provider. The provider will respond with data formatted in JSON. Smart911Connect will format the data and deliver to the answering operator.

The premium level allows for other parameters to be used besides the ANI.

Emergency System Provider APIs

A third party may choose to consume the data aggregated by Smart911Connect. There are two ways a third party may consume this service. The third party may choose to be served up an HTML formatted response to be intergrated into a browser. Or, a third party may want a “raw” JSON response that can be consumed in any way.

On both of the above types, a secure REST request will be sent to Smart911Connect with a parameter(s) such as an ANI. Based on the preference of the third party, the response will be either HTML or JSON.