AlertSense Map Service

RecipientRequest

The following routes are available for this service:
POST	/api/data/Geometry
POST	/api/recipients

**RecipientRequest** Parameters:
Name	Parameter	Data Type	Required	Description
CountsOnly	body	bool	No
GeoJson	body	GeoJson	No

**GeoJson** Parameters:
Name	Parameter	Data Type	Required	Description
Type	body	string	No
Shapes	body	List<Shape>	No

**Shape** Parameters:
Name	Parameter	Data Type	Required
Type	body	string	No
Geometry	body	HickoryGeometry	No
Properties	body	Object	No

**HickoryGeometry** Parameters:
Name	Parameter	Data Type	Required	Description
Type	body	string	No
Coordinates	body	List<List>	No

**RecipientResponse** Parameters:
Name	Parameter	Data Type	Required	Description
SourceRecords	body	List<SourceRecord>	No

**SourceRecord** Parameters:
Name	Parameter	Data Type	Required
SourceId	body	int	No
Label	body	string	No
Count	body	int	No
Status	body	string	No
Recipients	body	List<Recipient>	No

**Recipient** Parameters:
Name	Parameter	Data Type	Required	Description
Number	body	string	No
LatLng	body	LatLngDetails	No

**LatLngDetails** Parameters:
Name	Parameter	Data Type	Required	Description
Lat	body	double	No
Lng	body	double	No

To override the Content-type in your clients, use the HTTP Accept Header, append the .json suffix or ?format=json

To embed the response in a jsonp callback, append ?callback=myCallback

HTTP + JSON

The following are sample HTTP requests and responses. The placeholders shown need to be replaced with actual values.

POST /json/reply/RecipientRequest HTTP/1.1 
Host: elm.alertsense.com 
Content-Type: application/json
Content-Length: length

{"countsOnly":false,"geoJSON":{"type":"String","features":[{"type":"String","geometry":{"type":"String","coordinates":[[[0]]]},"properties":{}}]}}

HTTP/1.1 200 OK
Content-Type: application/json
Content-Length: length

{"SourceRecords":[{"SourceId":0,"Label":"String","Count":0,"Status":"String","Recipients":[{"Number":"String","LatLng":{"Lat":0,"Lng":0}}]}]}