# Mobile log controller (/mobilelog)
This controller contains one endpoint to write log files from a mobile app to the server.
# /{app}
/mobilelog/{app} POST
Description
Writes (part of) a log file from a mobile app to the server. On the server it
will store the log file in a path user/app/device or user/app (if you don’t set
a device). Log files are separated by date. You should specify at what position
the data should be written in the log file. This call will delete all data after
that position and then write the specified data.
The log files are written on the server in files with a date like
20220923.log or 20220923.zip. The extension depends on the zip
parameter.
Authorization
Any authenticated user
URL parameters
{app}
App code. This depends on the apps that are known in your instance of SenSeeAct.
See this method in the source code of SenSeeActService:
nl.rrd.senseeact.service.ApplicationInit.createMobileAppRepository()
device
(optional) Device ID. If specified, this must be a string of at most 64 characters using only alphanumeric characters and dashes (-). For example you can pass a UUID or an Android device ID.
date
The date identifying the log file.
position
The position in the log file where the data should be written.
zip
(optional) true if it should write to a file like 20220923.log, false if it
should write to 20220923.zip. The default is false.
Content (application/octet-stream)
The data to write to the log file.
Response (application/json)
–
Example
Request
POST https://www.example.com/servlets/senseeact/v6.1.0/mobilelog/myapp ?device=3aa96976b8938f04 &date=2016-01-27 &position=0 &zip=false X-Auth-Token: ... Content-Type: application/octet-stream ...
Response
–