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

Sense Devices API

Device-level energy data and device information

Sense Devices API is one of 6 APIs that Sense publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Devices. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, an engineering blog, and rate-limit docs.

This API exposes 5 operations across 5 paths, and defines 4 schemas. It is described by OpenAPI 3.2.0, at version 1.0.0.

Requests are made against a single base URL, https://api.sense.com/apiservice/api/v1.

5 operations 5 paths 4 schemas 5 GET

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0.0
Base URL
https://api.sense.com/apiservice/api/v1
Authentication
HTTP Bearer
Resource Areas
1

Authentication & Security 1

Sense Devices API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (BearerAuth). By default, every request must be authenticated.

  • BearerAuth — Bearer token obtained from the /authenticate or /renew endpoints. Include as "Authorization: bearer " header.

Paths & Operations 5

Across 5 paths, the API surfaces 5 operations — 5 GET. Each is listed below with its method, path, parameters, and response codes.

Devices 5

Device-level energy data and device information

GET
/app/monitors/{monitor_id}/devices
List discovered devices
getDiscoveredDevices 1 param → 200401
GET
/app/monitors/{monitor_id}/devices/overview
Get devices overview
getDevicesOverview 1 param → 200401
GET
/app/monitors/{monitor_id}/devices/always_on
Get always-on device info
getAlwaysOnInfo 1 param → 200401
GET
/app/monitors/{monitor_id}/devices/{device_id}
Get specific device information
getDeviceInfo 2 params → 200401404
GET
/monitors/{monitor_id}/devices
Get raw device data
getRawDeviceData 1 param → 200401

Schemas 4

The contract defines 4 schemas that model the data the API accepts and returns. The most detailed are Device (6 properties), AlwaysOnResponse (2 properties), DevicesOverviewResponse (2 properties). Each schema is shown below with its type and property counts.

Device
object
A machine-learning detected electrical device
6 properties
DevicesOverviewResponse
object
Overview of all detected devices
2 properties
AlwaysOnResponse
object
Always-on load information
2 properties
DeviceDetail
object
Detailed information for a specific device

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

sense-devices-api-openapi.yml Raw ↑

Other APIs Sense publishes across the network.

Sense Realtime API
Sense Authentication API
Sense History API
Sense Monitors API
Sense Users API
Where this information came from

This is an independent, third-party profile of Sense Devices 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.