GalaxyMobile Client API

<back to all web services

ProtectMeUpdateLocationRequest

The following routes are available for this service:
POST/protectme/locationUpdate the location of an in-progress panic request.
ProtectMeUpdateLocationRequest Parameters:
NameParameterData TypeRequiredDescription
PanicIdbodyintYesThe ID of the panic log. This is the ID returned by the panic provider when the service was activated.
LatitudebodydoubleYesLatitude of the panic location.
LongitudebodydoubleYesLongitude of the panic location.
ApiServiceRequest Parameters:
NameParameterData TypeRequiredDescription
ApiKeyformstringYesThe API Key required for authentication
ProtectMeActivationResponse Parameters:
NameParameterData TypeRequiredDescription
ProductAvailableformboolNoIs the requested product set up and enabled on Galaxy.
UserHasAccessformboolNoDoes the user have access to this product, based on their Galaxy profile.
PanicIdformlongNoThe ID of the panic log. This is the ID returned by the panic provider. Used to get panic detail later.
ApiServiceResponse Parameters:
NameParameterData TypeRequiredDescription
DescriptionformstringNo
HeadingformstringNo
WasSuccessfulformboolNo
ModelStateformObjectNo

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 /protectme/location HTTP/1.1 
Host: galaxymobile.api.client.prod.86degrees.com 
Accept: application/json
Content-Type: application/json
Content-Length: length

{"PanicId":0,"Latitude":0,"Longitude":0,"ApiKey":"String"}
HTTP/1.1 200 OK
Content-Type: application/json
Content-Length: length

{"ProductAvailable":false,"UserHasAccess":false,"PanicId":0,"Description":"String","Heading":"String","WasSuccessful":false,"ModelState":{}}