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 your encrypted Jentic One instance 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.

Can I limit what my agent is allowed to do with the ecobee API?

Yes. Because you run Jentic One yourself, your own rules decide which ecobee operations and credentials the agent may use, and the ecobee API takes the thermostat selection in the request body rather than a URL path, so you scope access by operation. You can allow the agent only the calls it needs, such as reading thermostat state with GET /thermostat and setting a temperature hold with POST /thermostat, while leaving demand-response (POST /demandResponse) and management-set (POST /managementSet) operations out unless you explicitly grant them. Your stored ecobee OAuth credentials are injected at execution time and never enter the agent's prompt or logs.