API and Webhooks Overview

VergeSense provides a suite of integration capabilities to our customers and partners. Open REST APIs are available to “pull” just the data you need, or VergeSense can automatically “push” relevant data to your platform using our pre-packaged webhooks.

VergeSense also partners with a number of technology companies to provide out-of-the-box integrations with platforms you may already have. Standard integration offerings include, but are not limited to:


Desk and Room Booking

Employee Experience


  • iOffice

  • SpaceIQ

  • SerraView

  • OfficeSpace

  • SpaceWell

  • Robin

  • TEEM

  • Cloudbooking

  • Comfy

  • JLL Oasis


  • CBRE Host

  • Rfiniti

  • Microsoft Outlook 365

  • Google Calendar

A full list of integrations and partners can be found here. 

Full details on how to utilize VergeSense APIs can be found here.

New Integrations: Process and Requirements

Method 1: VergeSense API Key - Customers and 3rd-party integrators can readily pull data from our API at your desired cadence (maximum 1 per minute) into your 3rd-party or homegrown platforms and applications.

  • Customers and 3rd-parties can access their API key via the VergeSense portal.

Method 2: VergeSense Webhook - VergeSense can enable webhooks on your behalf (self-service capabilities coming soon). Data events are sent automatically by VergeSense to your application or 3rd party suite. To make a request, submit the following information to your VergeSense point of contact:

  • Event Type: VergeSense supports subscribing to various events generated by the VergeSense Cloud platform. Options are described in the online API documentation. The “space_report v2” event is most commonly requested.

  • URL: This is the URL provided by the customer that data should be sent to.

  • Authentication Method: The authentication method (optional) for the endpoint that we will configure. Supported methods can be found in the online API documentation.

  • Building, Floor, and Space Reference IDs: Customers or 3rd-parties should provide a reference ID for all buildings, floors, and spaces in scope. Typically, this will match IDs already in use in IWMS and other systems. Space IDs must match in order to map data between systems.


Was this article helpful?

0 out of 0 found this helpful



Please sign in to leave a comment.