Omnicomm Online-Integration Api-En
Omnicomm Online-Integration Api-En
Integration Manual
02.04.2020
Contents
6 General Information
6 Main Features
6 REST
API
7 SOAP
8 Connection
9 SOAP
10 REST API
10 Obtaining the rights to use REST
API
10 Authorization
10 User
Management
10 Vehicle
Management
11 Geofence
Management
11 Notification
Handling
11 Reports
11 Omnicomm Video
Service
12 Obtaining a video fragment
12 Restrictions
12 Unsuccessful authorization attempts
12 Authorized calls
13 Unauthorized calls
13 SOAP
13 SOAP Methods
List
13 signIn – authorization
41 getTrack – track
48 Errors
48 Work Client
Example
49 Types of
Events
General Information
Omnicomm Online
Omnicomm Online allows the user to control the operation of vehicles and
drivers by means of reports being part of it. To access Omnicomm Online
only a personal computer is required, connected to the Internet.
Omnicomm Online has built-in special-purpose tools to collect the
processed data and use them in the accounting documents and in the
fleet monitoring systems.
This manual describes the built-in tools operation and the integration with
third-party systems.
General Information
The integration with Omnicomm Online is used to expand the
functionality of third-party systems and to automate the input of data
obtained from Omnicomm Online into the accounting systems.
The following integration methods are available:
REST API
Main Features
REST API
REST API facilitates the automation of:
user management
6
General Information
geofence management
receiving reports
receiving notifications
SOAP
Data, downloaded from the Omnicomm Online system, allows, at the
initiation of appropriate functionality of third-party systems, the following
tasks to be performed automatically:
Accounting for mileage and usage time for calculating the amount of
work, driver’s salary, etc.
Use of the current location to select suitable vehicle to fulfill the order
7
Connection
SOAP protocol does not support the use of OVMS (video service)
subsystem. Use REST API for quick integration with the OVMS subsystem.
Mileage
Fuel consumption
Movement duration*
Track*
Actual location*
Connection
To obtain the connection address for web services, the client should
contact Omnicomm’s Technological Support Team.
Connection to the web-service is performed by the Technical Support
8
Demo access to the web-services
SOAP
If necessary, to test the connection to web-services (to verify the
application without using a real Omnicomm Online account, or if there is
doubt about the network settings), one can use the web-services demo
server of Omnicomm.
Web services connection address:
http://demo.omnicomm.ru:8000/AnalyticalServer/v2/ws?wsdl
Login: rudemoru Password: rudemo123456
9
REST API
REST API
You can find the API method specification at
https://developers.omnicomm-world.com
Authorization
A JWT token must be indicated in the Authorization header when
accessing the REST API methods (except for authorization methods). This
JWT token grants the right to use REST API.
JWT format: JWT<space><the JWT received from the authorization
method>
Example:
Authorization: JWT
eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpZCI6MTU3MDM1OTEsImxvZ2luIjoiYWR
4ifQ.0I0CXcwWWxZWARE0eUEPOAvKd0prW_Uf0jbOMLnd5SI
The JWT expiry day is indicated in the payload-attribute exp in the Unix
Time Stamp format in UTC. After the expiry, when accessing the method
the Error 401 Unauthorized will appear.
The JWT can be obtained using the method POST /auth/login?jwt=1 or,
upon expiry, post /auth/refresh by indicating in the Authorization refresh
header the JWT obtained during the authorization from post /auth/login?
jwt=1.
User Management
User management covers adding, deleting, and blocking users in
Omnicomm Online, as well as getting a list of all Omnicomm Online users.
An authorized user may access the vehicle data.
An external system can carry out tasks on a user's behalf after logging in
under their account (after obtaining the JWT with the user's right).
Description of user management methods: https://developers.omnicomm-
world.com/#/Users/
Vehicle Management
10
REST API
Geofence Management
Geofences are virtual areas on the map created by users in Оmnicomm
Оnline. When creating a geofence, specify its shape (a polygon, a circle,
or a line) and its geographic coordinates.
Geofences are used to monitor vehicle location (entering/exiting a
geofence) and other operation parameters, such as the vehicle's speed.
Description of geofence management methods:
https://developers.omnicomm-world.com/#/Geozones/
Notification Handling
Notifications are used to promptly notify users about recorded events.
Description of methods for handling notifications:
https://developers.omnicomm-world.com/#/Notifications/
Reports
Reports are used to obtain various information about vehicle operation.
Description of methods for obtaining reports:
https://developers.omnicomm-world.com/#/Reports/
11
REST API
Create a task to obtain the video fragment based on the received video
profile: POST /service/ovms/api/tasks
After receiving the “done” status for the task, request the video file:
GET /service/ovms/api/tasks/file/{task_id}
Restrictions
There are restrictions on the intensity of requests that may be sent to the
Onmicomm Online REST API to protect it against DoS-attacks and errors
of third-party systems.
When these restrictions are exceeded, any requests from the
corresponding IP address or user to the REST API will be blocked.
Authorized calls
12
SOAP
Unauthorized calls
Not more than 60 in one minute from the same IP-address.
SOAP
SOAP Methods List
For date and time data transmitting the UNIXTIME (in seconds) format is
used. Units of other parameters are listed below.
signIn – authorization
Input Values
Returned Values
13
SOAP
Input Values
Returned Values
Input Values
14
SOAP
Returned Values
15
SOAP
Input Values
Returned Values
Input Values
16
SOAP
Returned Values
17
SOAP
Input Values
Returned Values
Input Values
18
SOAP
Returned Values
Input Values
Returned Values
19
SOAP
Input Values
Returned Values
Input Values
20
SOAP
Returned Values
Input Values
Returned Values
21
SOAP
Input Values
Returned Values
22
SOAP
Input Values
Returned Values
Input Values
23
SOAP
Returned Values
Input Values
Returned Values
24
SOAP
Input Values
Returned Values
Input Values
25
SOAP
Returned Values
26
SOAP
Input Values
Returned Values
27
SOAP
Input Values
Returned Values
Input Values
28
SOAP
Returned Values
29
SOAP
Input Values
Returned Values
Input Values
Returned Values
30
SOAP
Input Values
Returned Values
31
SOAP
Input Values
Returned Values
32
SOAP
Input Values
Returned Values
33
SOAP
Input Values
Returned Values
34
SOAP
Input Values
Returned Values
35
SOAP
Input Values
Returned Values
Input Values
36
SOAP
Returned Values
Input Values
37
SOAP
Returned Values
Input Values
Returned Values
38
SOAP
Input Values
39
SOAP
Returned Values
40
SOAP
Input Values
Returned Values
getTrack – track
41
SOAP
Input Values
Returned Values
Input values
42
SOAP
Returned Values
43
SOAP
Input values
44
SOAP
Returned Values
45
SOAP
Input values
46
SOAP
Returned Values
47
SOAP
Errors
List of returned errors:
0: No errors – there are no errors
1: Signing in failed – incorrect Login / Password entered
2: Authorization required – authorization is required to access the data
3: Dead session number – session has expired, re-authorization is
required
4: Bad interval – incorrect time interval entered
5: Bad object – there is no object with this identifier
6: Admin login – someone is trying to log in as Admin User
7: Unusable object – the value cannot be calculated for the object with
this identifier
8: Bad event type – there is no event type with this identifier
9: Access denied – no authorization to access the object
10: Data not found – no data for the corresponding input values
11: Blocked interval – the requested interval contains data blocking
periods
12: Bad object type – the specified object type does not exist
13: Invalid format – the format is incorrect
14: Undefined error – the error is unspecified
15: 404 – page not found
package ru.omnicomm.test.client;
import ru.omnicomm.analyticalserver.*;
import java.net.MalformedURLException;
48
SOAP
import java.net.URL;
import java.util.List;
}
}
Types of Events
49
SOAP
6 Ignition OFF
8 Battery power ON
10 Transition to roaming
13 Idle time
14 Beginning of speeding
50
SOAP
21 Connection established
51
SOAP
32 Overload of auxiliary
equipment
33 Power ON
38 Power OFF
42 Beginning of stop
43 End of stop
44 Beginning of acceleration
45 End of acceleration
46 Digital input ON
52
SOAP
48 Instant acceleration
49 Unknown driver
52 Device tampering
54 iButton applied
53
info@omnicomm-
world.com
www.omnicomm-
world.com