All calls to the Rock 7 API must be authenticated. The API accepts two parameters -
These credentials should be different from those used to log in to other Rock Seven systems (e.g. Core). Contact Rock 7 Support (firstname.lastname@example.org) for assistance.
This command will create a new Geofence from the supplied coordinate pairs. The Geofence will be locked, and is not editable after it is created.
Polyfences can be configured and sent to a tracker, causing specific behaviour to occur exactly when the tracker crosses a geofence boundary.
A polyfence configuration consists of one or more geofences, each with an associated behaviour.
A typical workflow for creating and sending a geofence is shown below.
- Create one or more geofences
- Create a new (empty) polyfence configuration
- Attach one or more Geofences to the polyfence, specifying the desired tracker behaviour for each geofence.
- Send the polyfence configuration to the device
Tracker will transmit when it enters or leaves the Geofence
Tracker will only transmit when it enters the Geofence
Tracker will only transmit when it leaves the Geofence
Tracker will transmit when it enters the Geofence; and then disable Polyfence mode
Once a Polyfence has been defined; it can be sent to devices.
Sending a polyfence to a device will “lock” the Polyfence so no further Geofences may be attached. If you wish to include additional Geofences, a new Polyfence must be created.
Issuing this command will replace any other Polyfences associated to this device.
A device can be identified either by its device identifier or its serial.
Available devices can be queried along with usage, and line rental can be extended. Charging is carried out automatically using card details stored on file with our card provider (Stripe).