Event archives

GET /api/v1/channel_data

Returns the event archive for a metering device. It uses the same channel_data endpoint as readings, but with an event-type archive_type; the response contains event/message records (codes and descriptions) instead of numeric channels.

Query parameters

archive_type string required

Event archive type. One of: nesht, nesht_svod, changes, event, alarm, valve, seance.

equipment_id integer required

Metering device identifier. Alternatively, the pair energy_varname + uid can be passed.

fp_start string

Time interval (segment start), yyyy-mm-dd. Optional.

fp_end string

Time interval (segment end), yyyy-mm-dd. Optional.

page integer

Page number.

per_page integer

Page size. Optional. Defaults to 10 for event archives.

Response fields

AttributeDescription
data[].event_timeUnix time of the event (seconds; milliseconds are appended as a fractional part)
data[].channel_dataArray of single-key { varname: value } objects. *Description fields are enriched with texts from the message reference
total_pagesTotal number of pages in the returned set
current_pageCurrent page
next_pageNext page available for downloading, null if the current page is the last one

Request

bash
curl -i \
  --header "access-token: *********************" \
  --header "token-type: Bearer" \
  --header "client: **********************" \
  --header "uid: user@local.net" \
  --header "Content-Type: application/json" \
  --request GET \
  "https://uztgs.uz/api/v1/channel_data?archive_type=nesht&equipment_id=906&fp_start=2025-05-01&fp_end=2026-05-29&page=1"

Response

Naposledy aktualizováno

Byla tato stránka užitečná?