ecobee API

Name: ecobee API
Brand: ecobee API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentIOTHome Automationoauth216 EndpointsREST

For Agents

Control ecobee smart thermostats — adjust temperature, read sensor data, pull energy reports, manage thermostat groups, and participate in demand response programs.

Install Jentic One Beta

Connect the ecobee API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the ecobee API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with ecobee API.

Read current thermostat state including temperature, humidity, HVAC mode, and occupancy sensor data

Set thermostat hold temperatures, climate programs, and vacation schedules remotely

Pull runtime and meter reports for energy consumption analysis over configurable date ranges

GET STARTED

Start building with ecobee API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use ecobee API for, with concrete tasks.

★ AI Agent Smart Home Climate Control

AI agents control ecobee thermostats through Jentic's intent search, adjusting temperature and HVAC programs based on occupancy patterns, weather forecasts, or energy pricing signals. An agent searches for 'set thermostat temperature', discovers the POST /thermostat endpoint, and sends a setHold function call with the desired temperature and duration. Jentic handles OAuth 2.0 token refresh and thermostat selection automatically.

Set a temperature hold of 70°F heating and 76°F cooling on thermostat ID 'abc123' for the next 4 hours using the setHold function

Energy Usage Monitoring and Optimization

Track HVAC energy consumption by pulling meter reports (GET /meterReport) and runtime reports (GET /runtimeReport) that break down daily heating hours, cooling hours, fan runtime, and auxiliary heat usage. These reports enable energy optimization algorithms to identify inefficient patterns — such as excessive auxiliary heat activation — and recommend schedule adjustments that reduce utility costs without sacrificing comfort.

Pull the runtime report for thermostat 'abc123' covering the last 30 days, then calculate total heating hours vs cooling hours and identify days with auxiliary heat usage exceeding 4 hours

Utility Demand Response Integration

Participate in utility demand response programs by creating and managing demand response events through the POST /demandResponse endpoint. When grid load peaks, utilities signal connected thermostats to temporarily reduce energy consumption. The API enables enrollment, event scheduling, and opt-out management for residential and commercial properties participating in load-shedding programs.

Create a demand response event that raises the cooling setpoint by 3°F for all thermostats in management set 'commercial-01' between 2PM and 6PM today

Multi-Property Thermostat Management

Administer thermostats across multiple properties using management sets (GET/POST /managementSet) with user and thermostat assignments. Property managers control HVAC settings for apartment buildings, hotel rooms, or office suites from a single API integration. The /managementSet/thermostat endpoint handles bulk thermostat assignment, while /managementSet/users manages access permissions per property.

List all management sets, add thermostat 'xyz789' to management set 'building-a', then assign user 'manager@example.com' with read-write access to that set

Key Endpoints

16 endpoints — jentic publishes the only available openapi specification for ecobee api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

GET

/thermostat

Retrieve thermostat state, sensors, and settings

POST

/thermostat

Update thermostat settings and execute functions

GET

/thermostatSummary

Get summary status of all thermostats

GET

/runtimeReport

Pull HVAC runtime analytics by date range

GET

/meterReport

Get energy meter consumption data

POST

/demandResponse

Create a demand response event

POST

/group

Create or update a thermostat group

POST

/managementSet

Create a management set for multi-property admin

GET

/thermostat

Retrieve thermostat state, sensors, and settings

POST

/thermostat

Update thermostat settings and execute functions

GET

/thermostatSummary

Get summary status of all thermostats

GET

/runtimeReport

Pull HVAC runtime analytics by date range

GET

/meterReport

Get energy meter consumption data

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

ecobee OAuth 2.0 tokens (access and refresh) are stored encrypted in the Jentic vault (MAXsystem). Agents receive pre-authorized access — OAuth flow complexity and token refresh are handled automatically without exposing client secrets.

Intent-based discovery

Agents search by intent (e.g., 'set thermostat temperature') and Jentic returns the matching ecobee operation with the function call schema (setHold, resumeProgram, etc.), so the agent can control thermostats without understanding ecobee's function-based API pattern.

Time to first call

Direct ecobee integration: 2-3 days for OAuth 2.0 flow, function call API patterns, and selection object construction. Through Jentic: under 1 hour — search, load schema, execute.

FAQs

Specific to using ecobee API through Jentic.

Why is there no official OpenAPI spec for ecobee API?

ecobee does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call ecobee API via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.

What authentication does the ecobee API use?

The ecobee API uses OAuth 2.0 authorization code flow. Users authorize applications at https://api.ecobee.com/authorize and tokens are exchanged at https://api.ecobee.com/token. The smartWrite scope grants full read-write access to thermostat data. Through Jentic, OAuth tokens are stored in the encrypted MAXsystem vault with automatic refresh handling.

Can I set a specific temperature on my thermostat through this API?

Yes. Send a POST request to /thermostat with a setHold function specifying the desired heat and cool setpoints, hold type (nextTransition, indefinite, or holdHours), and the thermostat identifier in the selection object. For example, set holdType to 'holdHours' with holdHours of 4 to maintain 72°F for 4 hours before resuming the normal schedule.

How do I get energy usage data through Jentic?

Search Jentic for 'get thermostat energy usage report' to discover the GET /runtimeReport and GET /meterReport endpoints. The runtime report breaks down daily HVAC operation by heating, cooling, fan, and auxiliary heat hours. The meter report provides actual energy consumption data. Both accept startDate and endDate parameters for custom date ranges.

What sensor data is available from ecobee thermostats?

The GET /thermostat endpoint returns data from all connected sensors including the built-in thermostat sensor and any remote room sensors. Available readings include temperature, humidity, and occupancy (motion detection). Specify 'includeSensors' in the selection to receive the full remoteSensors array with per-sensor capability readings.

Can I manage thermostats across multiple properties?

Yes. The management set endpoints (GET/POST /managementSet) enable multi-property administration. Create management sets to group thermostats by building or zone, assign users with specific access levels via POST /managementSet/user, and add or remove thermostats via POST /managementSet/thermostat. This supports commercial property management at scale.

ecobee API

Connect the ecobee API to your agent

Capabilities

Start building with ecobee API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs