> ## Documentation Index > Fetch the complete documentation index at: https://docs.kodelabs.com/llms.txt > Use this file to discover all available pages before exploring further. # List device timeseries > Returns the recorded statuses of a device between `from` and `to`, oldest first. Each row is one recorded status: KODE OS records one per 1-minute window in which the device's points receive data, so consecutive rows can carry the same status. To find when a device went down or came back, compare each row with the one before it. > [!NOTE] > > The range between `from` and `to` has the same day limit as [List point timeseries](https://docs.kodelabs.com/products/kode-api/api-reference/timeseries/list-point-timeseries.md). Split longer ranges into multiple requests. Both bounds are inclusive. `from` and `to` need a UTC offset, for example `2026-11-01T00:00:00Z` or `2026-11-01T00:00:00+05:30`. A value without an offset is rejected. A page past the end returns an empty `data` array with the real `itemCount`. ## OpenAPI ````yaml /openapi/kode-api.yaml get /api/v1/buildings/{buildingId}/devices/{deviceId}/timeseries openapi: 3.1.0 info: title: KODE API version: 1.0.0 summary: Programmatic access to KODE OS resources and operations. description: > Use the KODE API to work with buildings, data sources, connectors, devices, points, virtual devices, timeseries data, schedules, the ontology, templating, mass writes, spaces, space assignments, tenants, meters, users, actions, and AssetOps work orders. license: name: Proprietary identifier: LicenseRef-Proprietary servers: - url: https://api.kodelabs.com/kodeos description: KODE API security: - bearerAuth: [] tags: - name: Authentication description: OAuth 2.0 discovery, token, and revocation endpoints. - name: Buildings description: Buildings and their areas. - name: Data sources description: Data sources connected to a building. - name: Devices description: Devices and their points. - name: Points description: Point queries and point writes. - name: Timeseries description: Current and historical point values. - name: Actions description: Actions exposed by building data sources. - name: Work orders description: AssetOps work orders, lookups, comments, and attachments. - name: Connectors description: KODE API connectors and the devices and points ingested through them. - name: Schedules description: Schedules discovered on building data sources. - name: Templating description: Apply ontology templates to groups of points. - name: Virtual devices description: Virtual devices that group points from other devices. - name: Ontology description: Canonical types, fields, units, and connections of the KODE ontology. - name: Users description: Users of the organization and their app access. - name: Mass write description: Write values to many points across buildings, and follow each run. - name: Spaces description: Levels and space units of a building, and the meters located in them. - name: Space assignments description: Assign tenants to leasable spaces of a building for a period. - name: Tenants description: Tenants of a building, the people or companies that lease its spaces. - name: Meters description: >- Meters of a building, their space assignments, parent and child links, and readings. paths: /api/v1/buildings/{buildingId}/devices/{deviceId}/timeseries: get: tags: - Devices summary: List device timeseries description: >- Returns the recorded statuses of a device between `from` and `to`, oldest first. operationId: listDeviceTimeseries parameters: - $ref: '#/components/parameters/BuildingId' - $ref: '#/components/parameters/DeviceId' - $ref: '#/components/parameters/Page' - $ref: '#/components/parameters/Limit' - name: from in: query required: true description: >- Start of the time range, inclusive. ISO 8601 date-time with an offset. schema: type: string format: date-time example: '2026-11-01T00:00:00Z' - name: to in: query required: true description: End of the time range, inclusive. ISO 8601 date-time with an offset. schema: type: string format: date-time example: '2026-11-02T00:00:00Z' responses: '200': description: A page of recorded statuses. content: application/json: schema: $ref: '#/components/schemas/PaginatedEntityDeviceStatusPublic' '400': description: >- `from` or `to` is missing, empty, or not a valid date with an offset (`Invalid date format`). `from` is after `to` (`From must not be after To`). The range is over the day limit (`From - To should be within N days period`). `limit` is above `200` or `0`. `page` is `0`. '401': $ref: '#/components/responses/Unauthorized' '403': $ref: '#/components/responses/Forbidden' '404': description: No device with this id exists in the building. '429': $ref: '#/components/responses/TooManyRequests' components: parameters: BuildingId: name: buildingId in: path required: true description: Building identifier from List buildings. schema: type: string example: 67c960faffaa42223163099e DeviceId: name: deviceId in: path required: true description: Device identifier. schema: type: string example: ahu-01 Page: name: page in: query description: Page number to return. The first page is `1`. schema: type: integer minimum: 1 default: 1 Limit: name: limit in: query description: Maximum number of items per page. schema: type: integer minimum: 1 maximum: 200 default: 50 schemas: PaginatedEntityDeviceStatusPublic: type: object properties: data: type: array items: $ref: '#/components/schemas/DeviceStatusPublic' page: type: integer format: int32 example: 1 limit: type: integer format: int32 example: 50 pageCount: type: integer format: int32 example: 1 itemCount: type: integer format: int32 example: 1 DeviceStatusPublic: type: object properties: deviceId: type: string description: Device identifier. example: 67c977317437671625264e05 status: type: - string - 'null' enum: - ok - down - fault - disabled - no_value - null description: >- Connectivity status of the device. `null` when the device never reported. example: ok dateTime: type: - string - 'null' format: date-time description: >- Time of the recorded status, in UTC. `null` when the device never reported. example: '2026-11-01T08:15:00.000Z' responses: Unauthorized: description: The access token is missing, invalid, or expired. Request a new token. Forbidden: description: The service account lacks permission for this building or operation. TooManyRequests: description: >- A rate-limit window is exhausted. Wait, then retry with increasing delays. securitySchemes: bearerAuth: type: http scheme: bearer bearerFormat: JWT description: > Paste an access token from [Create an access token](/products/kode-api/api-reference/authentication/create-an-access-token). Tokens expire, so request a new one if you receive `401`. ```` This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.