Skip to Content

Changes for page Grundlegendes

Last modified by YellowFox_RD on 2025/07/23 10:56
From version 2.1
edited by YellowFox_RD
on 2025/07/23 10:56
Change comment: There is no comment for this version
To version 1.1
edited by YellowFox_RD
on 2024/12/19 10:11
Change comment: Imported from XAR

Summary

Details

Page properties
Content
... ... @@ -1,17 +1,11 @@
1 1  (% class="box" %)
2 -(((
3 -Table of Contents
4 -)))
5 -
2 +(((Table of Contents)))
6 6  {{toc/}}
7 7  
8 8  Goal of this application is to provide the basic tracking functionality of YellowFox to third party software.
9 -
10 10  = Common =
11 -
12 12  Goal of this application is to provide the basic tracking functionality of YellowFox to third party software. Easy use and strong security were scopes during development. The user send commands via http to servers and receives the answers, positions, maps via the same way.
13 13  RTI can be used for example to:
14 -
15 15  (((
16 16  * Query of vehicle positions
17 17  * change of tracking settings
... ... @@ -19,22 +19,15 @@
19 19  * send orders and messages
20 20  * receive order states
21 21  )))
22 -
23 23  = Activation =
24 -
25 25  RTI must be activated from our support. Please feel free to contact them. You can then access the rti interface settings via extras → rti interface. There you are able to generate the needed keys for authentication.
26 -
27 27  = Base address =
28 -
29 -[[http://map.yellowfox.de/rti||rel="noopener noreferrer" target="_blank"]] or [[https://map.yellowfox.de/rti||rel="noopener noreferrer" target="_blank"]]
30 -
19 +[[http:~/~/map.yellowfox.de/rti/>>http://map.yellowfox.de/rti/]] or [[https:~/~/map.yellowfox.de/rti/>>https://map.yellowfox.de/rti/]]
31 31  = Description of functioning =
32 -
33 33  The authentication at rti interface is realized by rti keys. You can find these in the user portal via //extras → rti// //interface//. Your access owns two central keys: the company key and the import key. Furthermore you are able to generate an own key for each vehicle and vehicle group. Depending on the rti function, you will need a specific combination of keys. You can find information about that in the documentation of the respective function. The keys are distinct per company.
34 34  A rti key is a hexadecimal key. It will be generated at random and can be re-generated as often as you want. For vehicles you might also generate a custom rti ident, but these can only be used via 2-step authentication.
35 35  Rti keys have to be send with each request. They are not included in the responses.
36 36  Following keys are important to login via YellowFox:
37 -
38 38  (((
39 39  * company: This key is always mandatory. It identifies your company.
40 40  * import: This is kind of an universal key. It can be used to insert new data via the interface or access data of all vehicles.
... ... @@ -48,10 +48,7 @@
48 48  * group: Identifies a vehicle group and all vehicles assigned to it, as far as they own a rti key themselves. **If you use a group key make sure that all vehicles you want to access have a rti key!**
49 49  * Date, to prevent caching
50 50  )))
51 -
52 52  Execute as ?company=HEXKEY&vehicle=HEXKEY2
53 -
54 54  = Error codes =
55 -
56 56  If "ERROR:Text" is returned. "Text" contains the error description. You can find possible error codes  [[here>>doc:YellowFox Remote Tracking Interface.Fehlerwerte.WebHome]].
57 57