🇺🇸
Skedway documentation
English (en-us)
English (en-us)
  • Welcome
  • Reference
    • Custom Domain Authentication
  • Automation (API)
    • Check-in through control access
      • Settings
      • Authentication
      • Scheduling
      • Utilities
  • Integrations
    • Integrations - General Specifications
      • Google Workplace Integration - Calendar + Directory
      • Microsoft Integration - Calendar + Directory
    • Importing user`s profile photo
  • SSO - Single Sign On (SAML 2.0)
    • General Specifications
      • SSO for Google Workspace (G-Suite)
      • SSO for Azure portal (Microsoft)
  • Hardwares
    • Network & Infrastructure
    • Access links: URLs allowed to pass through the firewall
Powered by GitBook
On this page
  1. Automation (API)
  2. Check-in through control access

Scheduling

Endpoint responsible for performing position and parking check-in with user-informed data.

PreviousAuthenticationNextUtilities

Last updated 2 years ago

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...

Behavior

Requires authentication: Bearer Token (Authorization)

  1. For the route to work, you must inform at least one identification of the user who will be checked in:

    1. ID

    2. UID (Unique identifier of the company, can be considered the work register, etc)

    3. Email

  2. If the date is not informed, the current date and time will be considered.

  • Description
  • POSTPerform automatic check-in (Desk and Parking only) with user data
  • Behavior

Perform automatic check-in (Desk and Parking only) with user data

post
Authorizations
Path parameters
langanyOptional

Translation (pt_br, en_en, en_gb, es_es)

Example: pt_br
Body
idnumberRequired

Skedway ID

Example: 458
uidstringRequired

Custom UID

Example: u45832
emailstringRequired

Email

Example: example@domain.com
datestring · date-timeOptional

Checkin Date (RFC3339)

Example: 2022-11-10T19:30:30-03:00
notifybooleanOptional

Notify user via push if check-in has been performed

Default: trueExample: false
Responses
200
No scheduling found to check-in
application/json
201
Check-in successful
application/json
401
Unauthorized
403
Invalid Date
application/json
404
User not found
application/json
post
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
}