# Testing Beestat API: Where do I get thermostat\_id
**URL:** https://community.beestat.io/t/testing-beestat-api-where-do-i-get-thermostat-id/1756
**Category:** Uncategorized
**Created:** [May 22, 2026, 5:19pm UTC](https://community.beestat.io/t/testing-beestat-api-where-do-i-get-thermostat-id/1756 "2026-05-22T17:19:14Z")
**Posts on this page:** 6
**Page:** 1
### Author:  [@rakeshg](https://community.beestat.io/u/rakeshg)
#### Post date: [May 22, 2026, 5:19pm UTC](https://community.beestat.io/t/testing-beestat-api-where-do-i-get-thermostat-id/1756/1 "2026-05-22T17:19:14Z")
Hello - just discovered Beestat and I’m trying to use the API to get data on my thermostats. I have the API key and I can call `ecobee_thermostat.read_id` and get results. However, when I try and add the thermostat\_id to get data for only one thermostat using the thermostat\_id in the arguements, I get and “invalid thermostat\_id” response. From the API documentation, I can’t figure out what to use for “thermostat\_id”
I have tried “ecobee\_thermostat\_id”, “identifier” (both as integer and string), the value in sensors.id but nothing seems to work.
To test, I am constructing the url/query string and pasting into Safari. Any help would be appreciated.
---
### Author:  [@rakeshg](https://community.beestat.io/u/rakeshg)
#### Post date: [May 22, 2026, 7:15pm UTC](https://community.beestat.io/t/testing-beestat-api-where-do-i-get-thermostat-id/1756/2 "2026-05-22T19:15:10Z")
Figured it out - the thermostat\_id to use is the one that is returned by _ **thermostat.read\_id** _ and not _ecobee\_thermostat.read\_id_. Phew
---
### Author:  [@ziebelje](https://community.beestat.io/u/ziebelje)
#### Post date: [May 23, 2026, 12:18pm UTC](https://community.beestat.io/t/testing-beestat-api-where-do-i-get-thermostat-id/1756/3 "2026-05-23T12:18:40Z")
The original intent was that this would also work with other thermostats like Nest, but that quickly became not a thing. The legacy of the idea lives on in multiple thermostat tables. 🙂
---
### Author:  [@rakeshg](https://community.beestat.io/u/rakeshg)
#### Post date: [May 23, 2026, 1:13pm UTC](https://community.beestat.io/t/testing-beestat-api-where-do-i-get-thermostat-id/1756/4 "2026-05-23T13:13:06Z")
@ziebelje - a couple of related (sort of) question. Is the timestamp in “attributes” query in UTC or local time? In looking at the data that is returned, it appears to be UTC (`timestamp":{"value":["2026-05-21T00:00:00","2026-05-22T00:00:00"],"operator":"between"`) returns data offset by 5 hours from US central, but I wanted to confirm. Also, the number records returned for a single day (using the query above) is 289, so I was wondering if the 5 minute data bucket start at 00:00:00 and should end at 23:55:00 or it should being at 00:00:05 and end at 00:00:00? Thanks for your help. 🙏🏼
---
### Author:  [@ziebelje](https://community.beestat.io/u/ziebelje)
#### Post date: [May 25, 2026, 12:23pm UTC](https://community.beestat.io/t/testing-beestat-api-where-do-i-get-thermostat-id/1756/5 "2026-05-25T12:23:23Z")
Answered questions in dedicated thread: [Beestat API Questions/Clarifications](https://community.beestat.io/t/beestat-api-questions-clarifications/1759)
For a full day you’ll want 00:00 through 23:55 which is 288 records. Between is inclusive, so in your example above you’re getting one extra row which the first row for 5/22.
---
### Author:  [@rakeshg](https://community.beestat.io/u/rakeshg)
#### Post date: [May 25, 2026, 2:58pm UTC](https://community.beestat.io/t/testing-beestat-api-where-do-i-get-thermostat-id/1756/6 "2026-05-25T14:58:24Z")
> [@ziebelje](#):
>
> For a full day you’ll want 00:00 through 23:55
Thanks so much - I tried it both ways figured that 288 was the right number!