Open Presence Listener Info & Documentation

Automated Check-in via Network Login Workflow

Automated Check-in via Physical Access Control (Security/Turnstile) Workflow

Customer responsibility: 

• A client developer resource who has experience working with RESTful API calls
• Capture and process the presence events.
• Create or provide portal ID's to Tango.
• Push the presence events to the Reserve Open Presence Listener. (see documentation attached) 
  • Data Elements:
    • Email Address
    • Portal ID (location/door ID)
    • Timestamp in UTC
    • Event Type
• Initial development will be done against a Tango Reserve Development environment.
• Restrictions on presence events:
  • Only send valid Reserve users
  • Exclude Service Accounts
  • Exclude devices (like copiers)
  • Only send new events per person
    • For Network Logon, only send "new events" and not users who are "still logged in". If a user logs out and logs back on, then this would be a considered a new event.
  • Only send events for locations that are live in Reserve.

Tango will provide:

• Access to the Open Presence Listener Portal
• Service account to access the listener.
• A development environment for testing

A Tango-Reserve technical resource will review the test data in the development environment prior to granting approval and access for the customer to move their solution to Reserve production.

Download the attached documentation on the Open Presence Listener here. 

Attachments (3)

pdf

Tango_Reserve_Open_Presence_Listener_2026-0203.pdf
282 KB

69a689e472e58.27605970078611.png
412 KB

69a689e472e5a.27605965718035.png
412 KB