Using POST

Update:6/29/2019 - So it turns out that I was wrong. Whether you are using POST or GET to access your API, if your API server is using valid SSL the data is encrypted, including the URL which contains the GET parameters. Thanks to a colleague at work for this update. POST If you are using a secure SSL connection (i.e. then this data is encrypted during transmission on both GET and POST calls. Four parameters will be passed in the connection. 1. lat=yourlatitude 2. lon=yourlongitude 3 *key1=yourkey1 4 *key2=yourkey2 * key1 and key2 parameter names and values are what you put in the key1, key2 configuration entries. This could be something like mysecretkey=123098456 to pass to your web api or status=Stopped for lunch. There are currently no restrictions on the api keys or values but on your api side you should check and restrict incoming values to avoid invalid characters being sent. Locidoke allows you to rename the keys to match your API requirements.