Skip to main content
POST
Wireless Positioning System Based Presence Events

Authorizations

Authorization
string
header
required

Bearer authentication header of the form Bearer <token>, where <token> is your auth token.

Body

application/json
eventID
string
required

The ID of the event generated by the originating system.

Maximum string length: 36
measuredAt
string<date-time>
required

When this event had occurred.

Example:

"2018-10-07T08:32:03Z"

clientDevice
object
required

Contains information about the location of a client device, represented by a single latitude and longitude pair along with information about the floor and building. The Locatee building IDs and floor IDs can be retrieved from public static data endpoint. For processing the event either floorID or buildingID need to be present in the request and need to exist in Locatee. Note that events with only buildingID present will be processed only for views in Portfolio Insights. A floorID is needed in order the events to be processed for views in Workplace Operations. Events where both floorID and buildingID are missing or otherwise invalid will not be processed and the request will not return an HTTP error status code so that other valid events in the same request can be processed.

presenceState
enum<string>
deprecated

Describes the presence of the client device.

Available options:
PRESENT,
ABSENT
Example:

"PRESENT"

presenceCount
integer<int32>

The total number of connected devices (network connectivity) or detected people (sensors). For wireless presence events, the presenceCount is expected to be 1 if the client device is connected to the network and 0 if the client device is disconnected. For sensor events, the presenceCount is expected to be 1 if the sensor detects a person's presence. For people-counting sensors, the presenceCount is expected to be the number of detected people by the sensor.

Example:

1

timeout
integer
default:900

Timeout in seconds until the presence count will reset to 0. The default value of timeout is 15min (900s). Ideal value is 2 times the readout frequency if 0 presenceCount events do not exist in the source system.

Example:

600

Response

Successful Operation