How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Need help?

Contact us
Vergesense

VergeSense API

REST and webhook API for the VergeSense Cloud occupancy intelligence platform. Read buildings, floors, spaces, space types, neighborhoods, space groups, detections and threshold crossings; pull hourly and aggregate occupancy, utilization and headcount metrics at portfolio, building, floor, neighborhood, space-type, space-group and space level; inventory sensors and gateways; call the Predict API (space usage, space shortage, normalized space type distribution) built on the VergeSense Large Spatial Model; and create, patch, enable, disable, delete and inspect the delivery logs of webhooks that push space_report, space_availability and motion_detected events.

Documentation Provider Profile APIs.io OpenAPI GitHub

This API exposes 36 operations across 34 paths. It is described by OpenAPI 3.1.0, at version 2021-03-29.

Requests are made against a single base URL, https://api.vergesense.com.

36 operations 34 paths 0 schemas 1 DELETE28 GET1 PATCH6 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.1.0
API Version
2021-03-29
Base URL
https://api.vergesense.com
Authentication
API Key
Resource Areas
1

Authentication & Security 1

VergeSense API declares 1 security scheme for authenticating requests. An API key is passed in the header as vs-api-key (sec0). By default, every request must be authenticated.

Paths & Operations 36

Across 34 paths, the API surfaces 36 operations — 1 DELETE, 28 GET, 1 PATCH, 6 POST. Each is listed below with its method, path, parameters, and response codes.

Operations 36
GET
/metrics/hourly/spaces
/metrics/hourly/spaces
metrics_hourly_spaces 13 params → 200400
GET
/metrics/hourly/floors
/metrics/hourly/floors
metrics_hourly_floors 10 params → 200400
GET
/metrics/hourly/buildings
/metrics/hourly/buildings
metrics_hourly_buildings 9 params → 200400
GET
/metrics/hourly/neighborhoods
/metrics/hourly/neighborhoods
metrics-hourly-neighborhoods 9 params → 200400
GET
/buildings
/buildings
buildings-1 → 200400
GET
/buildings/{building_ref_id}
/buildings/:buildingrefid
buildings-2 2 params → 200400
GET
/buildings/{building_ref_id}/history
/buildings/:buildingrefid/history
buildingsbuilding_ref_idhistory 6 params → 200400
GET
/spaces
/spaces
spaces-1 4 params → 200400
GET
/spaces/detections
/spaces/detections
spaces_detections 10 params → 200400
GET
/spaces/thresholds/crossings
/spaces/thresholds/crossings
spaces_thresholds_crossings 7 params → 200400
GET
/spaces/types
/spaces/types
space_types 1 param → 200400
POST
/webhooks
/webhooks
webhooks-1 body → 200400
GET
/webhooks
/webhooks
webhooks → 200400
POST
/webhooks/{id}/enable
/webhooks/:id/enable
webhooksidenable 1 param → 200400
POST
/webhooks/{id}/disable
/webhooks/:id/disable
webhooksiddisable 1 param → 200400
GET
/webhooks/setup
/webhooks/setup
webhookssetup → 200400
PATCH
/webhooks/{id}
/webhooks/:id
webhooksid 1 param → 200400
DELETE
/webhooks/{id}
/webhooks/:id
webhooksid-1 1 param → 200400
GET
/webhooks/{id}/logs
/webhooks/:id/logs
webhooksidlogs 5 params → 200400
GET
/hardware/sensors
/hardware/sensors
hardware_sensors 4 params → 200400
GET
/hardware/gateways
/hardware/gateways
hardware_gateways 4 params → 200400
GET
/sensors
/sensors
sensors-1 1 param → 200400
GET
/sensors/state
/sensors/state
sensorsstate 1 param → 200400
GET
/sensors/history
/sensors/history
sensorshistory 3 params → 200400
GET
/metrics/aggregate/buildings/{building_id}
/metrics/aggregate/buildings
get_metricsaggregatebuildings{building_id} 7 params → 200400
POST
/predict/space_usage
Predict Space Usage
post_predict-space-usage 1 param body → 200
POST
/predict/space_shortage
Predict Space Shortage
post_predict-space-shortage 1 param body → 200
POST
/predict/normalized_space_type_distribution
Predict Normalized Space Type Distribution
post_predict-normalized-space-type-distribution body → 200
GET
/metrics/aggregate/floors/{floor_id}
/metrics/aggregate/floors
get_metricsaggregatefloors 7 params → 200400404
GET
/metrics/aggregate/spaces/{space_id}
/metrics/aggregate/spaces/:spaceid
get_metricsaggregatespace 7 params → 200400404
GET
/metrics/aggregate/neighborhoods/{neighborhood_id}
/metrics/aggregate/neighborhoods
get_metricsaggregateneighborhoods 7 params → 200400404
GET
/metrics/aggregate/space_groups
/metrics/aggregate/spacegroups
get_metricsaggregatespacegroups 7 params → 200400404
GET
/metrics/aggregate/space_types
/metrics/aggregate/spacetypes
get_metricsaggregatespacetypes 7 params → 200400404
GET
/metrics/aggregate/portfolio
/metrics/aggregate/portfolio
get_metricsaggregateportfolio 6 params → 200400
GET
/metrics/aggregate/spaces
/metrics/aggregate/spaces
metrics 8 params → 200400
GET
/metrics/spaces
/metrics/spaces
metrics_spaces 7 params → 200400

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

vergesense-api-openapi.json Raw ↑
#Occupancy Intelligence#Workplace Analytics#Building Data#Space Utilization#IoT Sensors#Webhooks
← Back to V APIs
API Details
ID
vergesense:vergesense-api
Base URL
https://api.vergesense.com
Docs
https://vergesense.readme.io/reference/reference-getting-started
Provider
Vergesense
APIs.io →  GitHub →
Explore more
All APIs Providers APIs.io Network
Work with this as data

Every API here is available over the API and to AI agents over MCP. APIs is not yet its own endpoint on the v1 API. Reach this content through network search and the tag graph, or the MCP server below.

Installs https://mcp.apievangelist.com/mcp in Claude, Cursor, VS Code and the rest — one button, every client.

MCP tools for apis
4 tools reach this content
  • search_api_evangelistSearch every content type across the network at once.
  • find_relatedThe shared-tag relevance graph — what else covers this.
  • get_tagEverything one tag labels, across all content types.
  • guide_topicPRO — a curated bundle for a topic: area, guidance, rules, papers, stories, services.
All tools & prompts
Call it yourself
curl for this page
Search the network for this 
curl "https://api.apievangelist.com/v1/search?q=vergesense-vergesense-api&limit=10"
Everything under a tag 
curl "https://api.apievangelist.com/v1/tags/vergesense-vergesense-api"

Discovery needs no key. Full bodies and the synthesis endpoints are Pro.

Get an API key

Free tier, no email required. Sign in with whichever identity you already have.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have. Your account

Where this information came from

This is an independent, third-party profile of VergeSense API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.