Configuration
Add MOVE features
The configuration of your MOVE project is split into 3 parts. Please make sure to select the right project in the drop-down menu of the navigation bar before you proceed. Also, please note that configuration changes may have an impact on your cost.
1. FEATURES
With these settings you can activate or deactivate MOVE features like Walking, Driving, or Public Transport. You will find a short syllabus of each feature in the MOVE Dashboard, and more detailed technical specifications in the chapter API Interface in these docs.
2. API KEYS & PROJECT CODES
Create an API key that allows secure access to the MOVE APIs.
Using the API key in the backend for:
Fetching data from the Timeline API or the Notifier API (see Timeline/authentication)
Using the API key in the frontend:
To authenticate your mobile MOVE SDK (see our code sample on Github). For security reasons, we recommend to use write-only keys for this scenario, or preferably the next option:
You can create, expire and delete as many API keys as you want on this page. The following parameters pertain to each API key:
key - copy the key from here
name - you can set this to whatever roles or rights segmentation you like to use in your systems; not relevant for MOVE
write-only - two different key types are available: write only (write-only=true; for all SDK functions that send and process data), and read-write (write-only=false; for all SDK functions / APIs you may use for reading data)
3. RECEIVER
The MOVE Generic Notifier pushes important events to your backend. This contains real-time events like POIs (Points of Interest), as well as more administrative data about user devices, that you may want to use to allow more targeted communication with your users.
Notifier events are pushed to your backend via a web hook: Set up a service, that is capable of receiving notifier events. Enter the URL of your service into this configuration page, as well as a token to be used for signing the event.
Timeline
The MOVE Timeline contains all the key results of MOVE compiled into a chronological timeline. Whenever a new timeline item is created for a user, MOVE pushes update notifications to your backend. Timeline items are not created in real-time; MOVE tries to clean up the timeline as much as possible from the raw data we receive from the devices, and is also enhancing the basic data with additional added value data - this may take some time. Note that we strictly avoid to change the timeline retrospectively, to simplify processing for your backend.
Timeline events are pushed to your backend via a web hook: Set up a service, that is capable of receiving timeline events. Enter the URL of your service into this configuration page, as well as a token to be used for signing the event.
Generic
Generic notifier sends all notification that are not related to timeline events. This contains multiple type of data:
Points-of-Interest: In case you activated the Points-of-Interest feature in your configuration, you will receive POI events here. These events can then be passed on to e.g. your CRM resp. Marketing Automation system for communicating with your user. This interface is almost real-time.
Device settings: User phones need to have a series of permissions granted. Permission profiles are forwarded through this interface, to enable communication with your users (e.g. please grant the Location Access "Always", otherwise we are unable to detect trips in the background).
may be extended in the future for new features
Assistance
Assistance notifier receives user alarms in emergency situations (both manual and automatic). At the specified URL you will receive the current GPS location and other details about the alarm, so you can adequately react to it. In order to react on user alarms, companies will usually set up a call service that is staffed 24/7 with human call operators.
manual - triggered in the mobile app whenever e.g. a user pushes an ALARM-button which calls the “initiate assistance call” service in the MOVE SDK
automatic - an Automatic Impact Detection can be configured as part of the MOVE features. Whenever a serious impact is detected during a car trip, the MOVE SDK sends an automatic alarm with some additional data to put the impact into context. The threshold helps to filter false positives. We recommend setting it to 1.0 in order to forward only serious impacts with an acceleration severity index>= 1.0.
Last updated