![traccar local server address for api traccar local server address for api](https://d585tldpucybw.cloudfront.net/sfimages/default-source/blogs/2020/2020-12/tcpip.png)
< Content-Type: application/json charset =UTF-8 > Accept: */ * > Cookie: JSESSIONID =xxxxxxxx Default admin username and password are admin and admin (or use any other admin credentials you have) Click settings >. > * upload completely sent off: 81 out of 81 bytes > * upload completely sent off: 109 out of 109 bytes Retrofit doesn't support anything like that, so you should use OkHttp directly: Request request new Request.Builder ().url (retrofit.baseUrl ().url ().toString () + 'api/socket').build () webSocket WebSocketCall.create (client, request) webSocket. > Accept: */ * > Cookie: JSESSIONID =xxxxxxx To get live updates you should be using WebSocket connection to Traccar server. POST /traccar/rest/getPositions HTTP/1.1
![traccar local server address for api traccar local server address for api](https://content.spiceworksstatic.com/service.community/p/post_images/0000184684/5783be13/attached_image/RedirectedFileGPO.png)
> Accept: */ * > Cookie: JSESSIONID =xxxxxxxxxx Both are open-source, thanks to which I was able to improve both and their cooperation. In this article I listed some common problems I encountered when I tried to use Freematics OBD-reader together with traccar device-tracking server. > * upload completely sent off: 25 out of 25 bytes Freematics + Traccar (integration and configuration) Raw. > Content-Type: application/x-www-form-urlencoded Below are examples of logging in an fetching data with curl (with demo site at ).
![traccar local server address for api traccar local server address for api](https://secureservercdn.net/198.71.233.64/373.938.myftpupload.com/wp-content/uploads/2019/06/image-63-1024x738.png)
Examples with cURLĪuthentication info is held in HTTP session, so you should have corresponding cookie in every request after logging in.
#TRACCAR LOCAL SERVER ADDRESS FOR API CODE#
Please refer to mobile web UI javascript code as an example of working with current RESTful API For now authentication data is stored in HTTP session, so prior to any method call the login method must be invoked. Status code 200 means that request completed successfully, any different code means that it failed.ĥ) Method call results are serialised in JSON.Ħ) Most of method calls require authentication. For example: /traccar/rest/login?payload=Ĥ) Errors are returned as HTTP status codes. For GET requests JSON array must be provided as payload parameter.