Trigger Geofence Downloads - 0x0016
Written by Iman Kareem
Updated at March 26th, 2025
Table of Contents
Before you start
Ensure you have reviewed:
A full list of API calls can be found at: https://api.oemserver.com/swagger/index.html.
Description
Many devices support Geofence Downloads to Device.
Geofence downloads enable functionality such as:
- Setting custom speed limits on private property, such as a mine site, and triggering a buzzer when the driver exceeds the limit.
- Turning on a vehicle's emergency lights in a specific area.
- Disabling cellular communication (and GPS fixes for a period of time) in a sensitive area, such as at an airport, or on an oil rig.
- Using alternate logging parameters to increase battery life
It is possible for a 3rd party server to act as the ‘Geofence Server’.
If a new Geofence is added on the Geofence server, it then needs to be ‘synced’ down to the device.
This message can be used to trigger a connection to the Geofence server.
It is not the only mechanism to trigger this connection - in fact, the server can trigger this in the “Hello Response” to the device (as part of usual data transfer). This is the preferred method to handle Geofence syncing vs this API call.
Payload
Payload is empty.
cURL Example:
curl -X 'POST' \
'https://api.oemserver.com/v1/AsyncMessaging/Send?serial=439705' \
-H 'accept: text/plain' \
-H 'Authorization: Basic XXXXXXXXXXXXXXXXX' \
-H 'Content-Type: application/json' \
-d '{
"MessageType": 22,
"CANAddress": 4294967295,
"ExpiryDateUTC": "2025-04-26T23:52:12.126Z",
"SendAfterDateUTC": "2025-03-26T23:52:12.126Z",
"Flags": 0,
"Data": []
}'