## Introduction *** :one: Before diving into the Notification service, ensure you understand the [High-level architecture concept](doc:high-level-architecture-concept), particularly the section about the multi-instance platform. In this context, an instance is the foundational unit for Notification services. Rules and settings are set at the instance level, affecting all users within that instance. This approach offers tremendous flexibility to your product. Specifically, you can categorize users into distinct groups and establish unique rules for export, including destination, even for users from a single mobile app. :two: Familiarize yourself with [Data management](doc:data-processing-workflow) options and the provided [datasets.](doc:data-workflow-and-categories-of-data) ## Setting up *** There are 3 steps to complete configuration: 1. Select and configure notification provider: 2. Configure Damoov platform 3. Process received notifications ### Select and configure notification provider: **Integration of Notification Services for Backend:** ➡️ [Setup Guide](https://docs.damoov.com/docs/data-export#setting-up-1)
If you're looking to extract data from the Damoov platform and manage it on your own server, this part is essential. Currently, we support the following notification services: - [AWS SNS](https://aws.amazon.com/sns/) - [Azure service bus](https://docs.microsoft.com/en-us/azure/service-bus-messaging/) - [Azure event grid](https://docs.microsoft.com/en-us/azure/event-grid/) Every dataset accessible through the data export service is associated with a unique event type. You can find a comprehensive list of these types and sample data [Here](doc:data-workflow-and-categories-of-data) ### Configure Damoov platform 1. Ensure you possess the essential details before beginning the configuration: | Notification service provider | Required details | | :---------------------------- | :--------------------------------------------- | | AWS | Access Key, Secret Key, TopicArn | | Azure event grid | TopicKey, Endpoint | | Azure service bus | Endpoint, SharedAccessKeyName, SharedAccessKey | 2. Visit Damoov Portal to complete the configuration: [https://app.damoov.com/control-panel/callbacks/](https://app.damoov.com/control-panel/callbacks/ "https://app.damoov.com/control-panel/callbacks/") Damoov Portal callback settings screen

### Process received notifications There are two types of notifications: 1. Notifications with URL inside the message body (Trips, Claims) 2. Notifications with message body only (Heartbeats) **Notifications with URL inside the message body (Trips, Claims)** To retrieve data from the URL, you need to use **Get Request** and provide UserId (UserId=DeviceToken) as a Header: ```curl curl --location --request GET 'https://mobilesdk.telematicssdk.com/mobilesdk/stage/track/get_track/v1?TrackToken=' \ --header 'DeviceToken: ' ``` ## Type of notifications **TRIPS:** - IncomingTrackRemoved (the track was deemed invalid or excluded) - it may include walking, cycling, and walking activities prior to driving and after driving. - IncomingTrackReceived (the track was valid and has been stored as Raw Trips Data) **(Recommended)** - TrackEnrichmentFinished (a track has been converted from raw to processed) **(Recommended)** **Notification sample** ```json 1 - IncomingTrackRemoved { "Event": "IncomingTrackRemoved", "Sender": "Data Motion", "UserId": "e5f2d616-896d-4610-9bef-9ff823af1275", "Object": { "Id": "9347f5eb-7aca-48c3-b698-f2c7b35add29", "Type": "IncomingTrackSummary", "Url": "https://mobilesdk.telematicssdk.com/mobilesdk/incoming/incoming/tracks/removed/9347f5eb-7aca-48c3-b698-f2c7b35add29/v1/" }, "Timestamp": "2020-07-20T14:44:54.9074056Z", "Details": { "TrackStartDate": "2020-04-29T09:20:48.0000000-06:00", "TrackFinishDate": "2020-04-29T09:57:02.0000000-06:00", "Reason": "Insufficient Track length" } } ``` ```json 2 - IncomingTrackReceived { "Event": "IncomingTrackReceived", "Sender": "Data Motion", "UserId": "e5f2d616-896d-4610-9bef-9ff823af1275", "Object": { "Id": "9347f5eb-7aca-48c3-b698-f2c7b35add29", "Type": "IncomingTrack", "Url": "https://mobilesdk.telematicssdk.com/mobilesdk/incoming/incoming/tracks/received/9347f5eb-7aca-48c3-b698-f2c7b35add29/v1/" }, "Timestamp": "2020-07-20T14:44:54.9074056Z", "Details": { "TrackStartDate": "2020-04-29T09:20:48.0000000-06:00", "TrackFinishDate": "2020-04-29T09:57:02.0000000-06:00" } } ``` ```json 3 - TrackEnrichmentFinished { "Event": "TrackEnrichmentFinished", "Sender": "Data Motion", "UserId": "e5f2d616-896d-4610-9bef-9ff823af1275", "Object": { "Id": "9347f5eb-7aca-48c3-b698-f2c7b35add29", "Type": "RichTrack", "Url": "https://mobilesdk.telematicssdk.com/mobilesdk/stage/track/get_track/v1?trackToken=" }, "Timestamp": "2020-07-20T14:44:54.9074056Z", "Details": { "ObjectReplaced": true, "TracksRemoved": [ { "Id": "3337f5eb-7aca-48c3-b698-f2c7b35add29", "Type": "RichTrack" }, { "Id": "4447f5eb-7aca-48c3-b698-f2c7b35add29", "Type": "RichTrack" } ] } } ``` **CRASH:** - Crash notification - 4 - AccidentEventReceived - Crash Data Buffer Received - 5 - AccidentEventExtraReceived - The full set of crash data received - 6 - AccidentEventCompletePackageReceived - Crash data - 7 - AccidentEventFiltered **(recommended)** **High-level scheme for crash data** 3086

**Notification sample** ```json 4 - AccidentEventReceived { "Event": "AccidentEventReceived", "Sender": "Data Motion", "UserId": "e5f2d616-896d-4610-9bef-9ff823af1275", "ClientId": "User 1234", "Object": { "Id": "9347f5eb-7aca-48c3-b698-f2c7b35add29", "Type": "Accident", "Url": "https://api.telematicssdk.com/api/drivingevents/get/v1/Accidents/received/9347f5eb-7aca-48c3-b698-f2c7b35add29" }, "Timestamp": "2021-07-20T14:44:54.9074056Z", "Details": { "DateReceived": "2021-07-20T14:42:54.8884056Z" } } ``` ```json 5 - AccidentEventExtraReceived { "Event": "AccidentEventExtraReceived", "Sender": "Data Motion", "UserId": "e5f2d616-896d-4610-9bef-9ff823af1275", "ClientId": "User 1234", "Object": { "Id": "9347f5eb-7aca-48c3-b698-f2c7b35add29", "Type": "AccidentExtra", "Url": "https://api.telematicssdk.com/api/drivingevents/get/v1/Accidents/extras/received/9347f5eb-7aca-48c3-b698-f2c7b35add29" }, "Timestamp": "2021-07-20T14:44:54.9074056Z", "Details": { "DateReceived": "2021-07-20T14:42:54.8884056Z" } } ``` ```json 6 - AccidentEventCompletePackageReceived { "Event": "AccidentEventCompletePackageReceived", "Sender": "Data Motion", "UserId": "e5f2d616-896d-4610-9bef-9ff823af1275", "ClientId": "User 1234", "Object": { "Id": "9347f5eb-7aca-48c3-b698-f2c7b35add29", "Type": "Accident", "Url": "https://api.telematicssdk.com/api/drivingevents/get/v1/Accidents/received/9347f5eb-7aca-48c3-b698-f2c7b35add29" }, "Timestamp": "2021-07-20T14:44:54.9074056Z", "Details": { "PackageDateReceived": "2021-07-20T14:42:54.8884056Z", "AccidentPassedFilters": true } } ``` ```json 7 - AccidentEventFiltered { "Event": "AccidentEventFiltered", "Sender": "Data Motion", "UserId": "e5f2d616-896d-4610-9bef-9ff823af1275", "ClientId": "User 1234", "Object": { "Id": "9347f5eb-7aca-48c3-b698-f2c7b35add29", "Type": "Accident", "Url": "https://api.telematicssdk.com/api/drivingevents/get/v1/Accidents/received/9347f5eb-7aca-48c3-b698-f2c7b35add29" }, "Timestamp": "2021-07-20T14:44:54.9074056Z", "Details": { "DateFiltered": "2021-07-20T14:42:54.8884056Z" } } ``` **PHONE STATUS** - Status update (Heartbeat **Notification sample** ```json Phone status { "Event": "HeartbeatReceived", "Sender": "Damoov", "UserId": "4dbf7a0f-d4ed-4a38-867c-1a4bbd84d089", "ClientId": "Gocha", "Timestamp": "2023-09-18T22:38:02.4974696Z", "Object": { "Id": "4dbf7a0f-d4ed-4a38-867c-1a4bbd84d089", "Type": "RawHeartbeat", "Uri": null }, "Details": { "ChargeLevel": 89.4, "WifiEnabled": true, "GPSEnabled": true, "RealTimeLocationEnabled": false, "MobileDataEnabled": true, "NotUploadedTripsCount": 6, "InstanceId": "3c1c8fd7-4133-404a-82e9-93a015d85362", "TimeReceived": "2023-09-18T22:37:53.7273284Z" } } ``` ## Data samples For your convenience, we've attached the data from a sample trip (recorded in March 2021 outside Cambridge, UK) - Raw Telematics data (notification IncomingTrackReceived) [Download JSON file, 1.2 MB](https://datamotion.docsend.com/view/48wdg5jrzkj5eeys)
_note that an IncomingTrackRemoved notification technically also links to an object similar to this one, but it will contain little or no useful information, but may be used for troubleshooting if you get many invalid tracks._ - Processed Trip Data (notification TrackEnrichementFinished) [Download JSON file, 341 kB](https://datamotion.docsend.com/view/8jeyednw4j62sf8r) ## Data Format Reference :point_right: [Raw telematics data](doc:raw-telematics-data-format)
:point_right: [Processed telematics data](doc:processed-telematics-data-format)
:point_right: [Crash data](doc:crash-data) ## Data processing workflow for vehicle data _Item 5 in the schematic at the top_ _Note that this is an advanced and rare use case. For most driver behavior and fleet management use cases, you will not need to use this._ Vehicle data collection is an advanced feature that is available as an add-on, and it works as follows: The SDK connects through Bluetooth to a so-called OBD (On-Board Diagnostics) device that talks directly to the car's onboard computer to get data like engine failure codes, maintenance status, etc. One example would be to generate a notification when the "Check Engine" light is on.
This feature requires additional hardware :point_right: [Bluetooth OBD](doc:bluetooth-obd) and communication via Bluetooth, and requires specific knowledge of the make and model of the car. It is most commonly used by fleet apps that actively manage the vehicles and their maintenance.
:point_right: [In-vehicle data](doc:in-vehicle-data) In general, vehicle data is handled in a similar fashion to GPS and Sensor data; data is filtered and enriched, and notifications are sent when a new dataset is available. ## Accessing these datasets Now that we've discussed the main categories of data and how they are processed, let's see how you can access that data. This consists in principle of two steps:
Option API: - Get a notification that a new dataset has been processed - Access the API to download the data referenced in the notification
Option Third-party storage - Data gets copied by us to your preferred storage provider - Get a notification that a new dataset has been copied ## Notifications When a dataset moves from one stage to the next on the Damoov platform, it creates an event. You can subscribe to those events to then access the relevant data > 📘 Note > > Notification message doesn't contain any track’s data, such as events or waypoints. To get these details, you have to query the track’s data using the Web API service, using credentials received from SNS Message. We support several well-known notification services, including Amazon and Azure. Each notification contains URLs, identifiers, and credentials for the respective dataset. > 🚧 Important > > Your back-end or application had to be prepared to receive several notifications related to a single trip. It means the previous version of the track has been updated, and you need to retrieve an updated version from our API again. An Example where this happens would be that the track was merged with another trip segment. the updated trip will have new trip details (time, distance, etc) ### Setting up notifications To set up Notifications, please go Callback settings
### Setting up notifications through AWS SNS The following AWS information is required to complete the setup: - AccessKey - Secret - AWS Region - TopicArn of the SNS queue ### Setting up notifications through Azure Service Bus The following Azure information has to be entered to complete the setup: - Endpoint, for example: `sb://.servicebus.windows.net/` - SharedAccessKeyName, for example: `` - SharedAccessKey, for example: `` ### Setting up notifications through Azure Event grid The following Azure information has to be entered to complete the setup: - Endpoint, for example: `https://..eventgrid.azure.net/api/events` - TopicKey, for example: ``