Scheduling
Endpoint responsible for performing position and parking check-in with user-informed data.
Description
Check-in will only be done for bookings that are within the allowed check-in period. Period that star with Check-in advance until No show.
All user bookings will be considered, without filters such as site, building, floor, etc...
Translation (pt_br, en_en, en_gb, es_es)
pt_br
Skedway ID
458
Custom UID
u45832
example@domain.com
Checkin Date (RFC3339)
2022-11-10T19:30:30-03:00
Notify user via push if check-in has been performed
true
Example: false
POST /scheduling/checkin HTTP/1.1
Host:
Authorization: Bearer Bearer
Content-Type: application/json
Accept: */*
Content-Length: 104
{
"id": 458,
"uid": "u45832",
"email": "example@domain.com",
"date": "2022-11-10T19:30:30-03:00",
"notify": false
}
{
"statusCode": 1,
"message": "text",
"checkinCount": 0
}
Behavior
Requires authentication: Bearer Token (Authorization)
For the route to work, you must inform at least one identification of the user who will be checked in:
ID
UID (Unique identifier of the company, can be considered the work register, etc)
Email
If the date is not informed, the current date and time will be considered.
Last updated