Ask about auth, request shape, or code samples in your preferred language.

API Assistant

Every request to public SDK endpoints must include a valid API key header.

This endpoint does not require a request body.

Use this endpoint to discover data sources when you do not already know their IDs. Results are paged with a cursor and can be filtered by site, usage or name. Once you have the IDs, `GET /data-sources/{id}` gives you the full record.

Failures return a JSON body with a `message` and an `internalErrorCode`, at the status shown below. Whenever the underlying error carries structured detail — which every schema-validation failure does — the body is replaced with a generic `Internal server error.` / `02-001` pair while the real status code is kept. Branch on the HTTP status and on `internalErrorCode`; never parse the message text.

x-api-key

Page size. Always send it, so that a missing `lastValue` reliably means you have reached the end.

limit

Cursor for the next page. Pass the `lastValue` from the previous response back verbatim.

lastValue

Comma-separated site IDs to restrict the list to, e.g. `1512,1513`.

siteIds

Comma-separated data source IDs, when you want a known set rather than a browse.

meterIds

Comma-separated usage IDs — `1` Sensor, `2` form, `7` AI Vision.

applyingIds

Free-text search over data source names. Keep sending the same value while paging through its results.

textSearch

Adds each row’s most recent reading. Any value at all turns this on — omit the parameter to leave it off.

withLastReadings

Expands each row to all of its metrics. Any value at all turns this on — omit the parameter to leave it off.

withDetails

Send the literal string `true` to restrict each row to its main metric.

onlyMain

AI Vision

Line 1 Label Counter

Fresno Plant

Form

A page of data sources. `null` — not an empty array — when nothing matched.

data

Data source ID — use it with `GET /data-sources/{id}`, `GET /reading` and `POST /reading`.

data[].id

data[].name

Where the data source is in validation: `10` Pending Validation, `20` Valid, `30` Invalid. A number here, while `GET /data-sources/{id}` returns the same thing as an object.

data[].validationStatus

`{ id, name, ordinal }` — what kind of data source it is.

data[].type

`{ id, name, channelId }` for the owning site.

data[].site

`{ id, name }` — how it is used: `1` Sensor, `2` form, `7` AI Vision.

data[].applying

Channel that carries this data source’s feed.

data[].channelId

Whether the data source is shared with other sites.

data[].isShared

Opaque cursor for the next page. Pass it back as `?lastValue=…`.

Returns a page of data sources in `data`, with an opaque `lastValue` cursor beside it. Each row is a summary — enough to identify a data source and decide which ones you care about. Fetch the full record with `GET /data-sources/{id}`.

Browse the data sources the API key can see, a page at a time.

Get Data Source List


## `GET /data-sources`

Use this endpoint to discover data sources when you do not already know their IDs. Results are paged with a cursor and can be filtered by site, usage or name. Once you have the IDs, `GET /data-sources/{id}` gives you the full record.

## Authentication

```http
x-api-key: <your-api-key>
```

See [API Authentication](/developers/api-reference/api-authentication) for how to create a key.

## Query parameters

| Parameter | Type | Required | Description |
| --- | --- | --- | --- |
| `limit` | number | no | Page size. Always send it, so that a missing `lastValue` reliably means you have reached the end. |
| `lastValue` | string | no | Cursor for the next page. Pass the `lastValue` from the previous response back verbatim. |
| `siteIds` | string | no | Comma-separated site IDs to restrict the list to, e.g. `1512,1513`. |
| `meterIds` | string | no | Comma-separated data source IDs, when you want a known set rather than a browse. |
| `applyingIds` | string | no | Comma-separated usage IDs — `1` Sensor, `2` form, `7` AI Vision. |
| `textSearch` | string | no | Free-text search over data source names. Keep sending the same value while paging through its results. |
| `withLastReadings` | boolean | no | Adds each row’s most recent reading. Any value at all turns this on — omit the parameter to leave it off. |
| `withDetails` | boolean | no | Expands each row to all of its metrics. Any value at all turns this on — omit the parameter to leave it off. |
| `onlyMain` | boolean | no | Send the literal string `true` to restrict each row to its main metric. |

## Response

`200 OK`

Returns a page of data sources in `data`, with an opaque `lastValue` cursor beside it. Each row is a summary — enough to identify a data source and decide which ones you care about. Fetch the full record with `GET /data-sources/{id}`.

```json
{
  "data": [
    {
      "id": "43510",
      "name": "Line 1 Label Counter",
      "validationStatus": 20,
      "type": {
        "id": "50",
        "name": "Form",
        "ordinal": 1
      },
      "site": {
        "id": "1512",
        "name": "Fresno Plant",
        "channelId": "45187"
      },
      "applying": {
        "id": "7",
        "name": "AI Vision",
        "channelId": null
      },
      "channelId": "67363",
      "isShared": false
    }
  ],
  "lastValue": "eyJ0eXBlT3JkaW5hbCI6MSwibmFtZSI6IkxpbmUgMSBMYWJlbCBDb3VudGVyIiwiaWQiOiI0MzUxMCJ9"
}
```

| Field | Type | Description |
| --- | --- | --- |
| `data` | array (nullable) | A page of data sources. `null` — not an empty array — when nothing matched. |
| `data[].id` | string | Data source ID — use it with `GET /data-sources/{id}`, `GET /reading` and `POST /reading`. |
| `data[].name` | string | Display name. |
| `data[].validationStatus` | number (nullable) | Where the data source is in validation: `10` Pending Validation, `20` Valid, `30` Invalid. A number here, while `GET /data-sources/{id}` returns the same thing as an object. |
| `data[].type` | object | `{ id, name, ordinal }` — what kind of data source it is. |
| `data[].site` | object | `{ id, name, channelId }` for the owning site. |
| `data[].applying` | object (nullable) | `{ id, name }` — how it is used: `1` Sensor, `2` form, `7` AI Vision. |
| `data[].channelId` | string (nullable) | Channel that carries this data source’s feed. |
| `data[].isShared` | boolean | Whether the data source is shared with other sites. |
| `lastValue` | string | Opaque cursor for the next page. Pass it back as `?lastValue=…`. |

### Good to know

- Rows always carry `id`, `name`, `validationStatus`, `type`, `site` and `isShared`. Other fields depend on the data source and on the flags you send, so read defensively.
- Add `withLastReadings` to get each row’s latest reading inline, or `withDetails` to expand every metric — either saves a follow-up call per data source.
- Do not treat the presence of `lastValue` as proof that more data exists. Keep paging until `data` comes back `null`, or until you receive fewer rows than the `limit` you asked for.
- The list is ordered by type, then name, then ID, and the cursor is built from those three. There is no way to change the sort.
- An empty result is `{"data": null}`, not `{"data": []}`.
- To map metric IDs to names for a data source, call `GET /data-sources/{id}?withSchema=true`.

## Errors

Failures return a JSON body with a `message` and an `internalErrorCode`, at the status shown below. Whenever the underlying error carries structured detail — which every schema-validation failure does — the body is replaced with a generic `Internal server error.` / `02-001` pair while the real status code is kept. Branch on the HTTP status and on `internalErrorCode`; never parse the message text.

```json
{
  "message": "Internal server error.",
  "internalErrorCode": "02-001"
}
```

| Status | Meaning |
| --- | --- |
| `400` | The request failed validation — a missing required field, a field the schema does not allow, an unparseable body, a value out of range, or a malformed `lastValue`. |
| `401` | The API key resolved to a user context that is not allowed to read or write the record you asked for. |
| `403` | The `x-api-key` header is missing or is not a recognised key. API Gateway rejects the call before the endpoint runs, so the body is only `{"message":"Forbidden"}`. |
| `409` | The write conflicts with an existing record, or it references a record that does not exist. |
| `429` | The API key exceeded the rate limit or quota on its usage plan. Also returned by API Gateway rather than the endpoint. |
| `500` | Unexpected server error, or the database returned no result where one was required. |



## `POST /devices/status/{id}`

Use this endpoint when an integration needs to report device health or operational state for a specific CV device.

## Authentication

```http
x-api-key: <your-api-key>
Content-Type: application/json
```

See [API Authentication](/developers/api-reference/api-authentication) for how to create a key.

## Path parameters

| Parameter | Type | Required | Description |
| --- | --- | --- | --- |
| `id` | string | yes | ID of the data source whose device status you are reporting. |

## Request body

Send a `status` object describing the device’s current health. Report the full set of fields every time.

```json
{
  "status": {
    "battery": 82,
    "isCharging": true,
    "onLine": true,
    "deviceOn": true,
    "cameraOn": true,
    "wifiConnected": true,
    "cellularConnected": false,
    "temperature": 31.5,
    "version": "2.14.0"
  }
}
```

| Field | Type | Required | Description |
| --- | --- | --- | --- |
| `status` | object | yes | The device’s current health and operational state. Its fields are listed below. |
| `status.battery` | number | no | Battery charge as a percentage. A low value raises an alert unless `isCharging` is true. |
| `status.isCharging` | boolean | no | Whether the device is currently charging. |
| `status.onLine` | boolean | no | Whether the device can reach Zira. |
| `status.deviceOn` | boolean | no | Whether the device itself is powered on and running. |
| `status.cameraOn` | boolean | no | Whether the camera is active. |
| `status.wifiConnected` | boolean | no | Whether Wi-Fi is connected. Send at least one connected network flag. |
| `status.cellularConnected` | boolean | no | Whether a cellular connection is up. |
| `status.ethernetConnected` | boolean | no | Whether a wired connection is up. |
| `status.temperature` | number | no | Device temperature in °C. A high value raises an alert. |
| `status.version` | string | no | Software version running on the device. |

## Response

`200 OK`

Returns the fixed string `"SUCCESS"` once the status has been stored. Nothing about the device or the alerts that were raised is echoed back — a `200` means "status recorded", not "device healthy".

```json
{
  "data": "SUCCESS"
}
```

| Field | Type | Description |
| --- | --- | --- |
| `data` | string | Always the literal `"SUCCESS"` on a 200. |

### Good to know

- Status values are not validated — they are evaluated. An unhealthy or missing value raises an alert for the device instead of failing your request, and you still get a `200`.
- Because of that, send the full set every time: `battery`, `onLine`, `deviceOn`, `cameraOn`, `wifiConnected` and `cellularConnected`. A field you leave out is treated as if it were bad news.
- Re-reporting a healthy status is how you clear alerts you raised earlier — Zira resolves an alert once the new status no longer triggers it.
- The device is identified by the path segment, not by a `deviceId` in the body.
- The reported status shows up in Zira as the data source’s device status.
- Errors from this endpoint are unusually detailed compared with the rest of the API. Do not treat that detail as a stable contract, and do not show it to end users.

## Errors

Failures return a JSON body with a `message` and an `internalErrorCode`, at the status shown below. Whenever the underlying error carries structured detail — which every schema-validation failure does — the body is replaced with a generic `Internal server error.` / `02-001` pair while the real status code is kept. Branch on the HTTP status and on `internalErrorCode`; never parse the message text.

```json
{
  "message": "Internal server error.",
  "internalErrorCode": "02-001"
}
```

| Status | Meaning |
| --- | --- |
| `400` | The request failed validation — a missing required field, a field the schema does not allow, an unparseable body, a value out of range, or a malformed `lastValue`. |
| `401` | The API key resolved to a user context that is not allowed to read or write the record you asked for. |
| `403` | The `x-api-key` header is missing or is not a recognised key. API Gateway rejects the call before the endpoint runs, so the body is only `{"message":"Forbidden"}`. |
| `409` | The write conflicts with an existing record, or it references a record that does not exist. |
| `429` | The API key exceeded the rate limit or quota on its usage plan. Also returned by API Gateway rather than the endpoint. |
| `500` | Unexpected server error, or the database returned no result where one was required. |


Update CV device status and trigger diagnostic alert evaluation.

Update Device Status


## `GET /data-sources/{id}`

Use this endpoint to load one data source and optionally include its schema and last reading.

## Authentication

```http
x-api-key: <your-api-key>
```

See [API Authentication](/developers/api-reference/api-authentication) for how to create a key.

## Path parameters

| Parameter | Type | Required | Description |
| --- | --- | --- | --- |
| `id` | string | yes | ID of the data source to fetch. |

## Query parameters

| Parameter | Type | Required | Description |
| --- | --- | --- | --- |
| `withSchema` | boolean | no | Send the literal string `true` to include the data source’s metric schema. Any other value is treated as false. |
| `withLastReading` | boolean | no | Send the literal string `true` to include the most recent reading. Any other value is treated as false. |

## Response

`200 OK`

Returns one data source with its identity, location, time zone, collection settings and status. The example below is trimmed — a real payload also carries per-type blocks such as `formConfig` for forms and `cv` for cameras.

```json
{
  "data": {
    "id": "43510",
    "name": "Line 1 Label Counter",
    "description": "Camera 5",
    "externalId": null,
    "type": {
      "id": "50",
      "name": "Form"
    },
    "offset": -420,
    "timezoneId": "3",
    "tzTimezoneName": "US/Pacific",
    "site": {
      "id": "1512",
      "name": "Fresno Plant",
      "channelId": "45187"
    },
    "model": {
      "id": null,
      "name": null
    },
    "manufacturer": null,
    "inactiveThreshold": 1500,
    "validationStatus": {
      "id": "10",
      "name": "Pending Validation"
    },
    "activityStatus": {
      "id": "40",
      "name": "Pending Readings"
    },
    "collector": {
      "id": "29",
      "name": "Form"
    },
    "collectorType": {
      "id": "1",
      "name": "Push"
    },
    "applying": {
      "id": "7",
      "name": "AI Vision"
    },
    "isCustomSchema": true,
    "collectionEnabled": true,
    "readingInterval": null,
    "channelId": "67363",
    "companyId": "1216",
    "isShared": false,
    "isTemplate": false,
    "isDeleted": false,
    "isPrivate": false,
    "displayUoms": [
      {
        "metricId": "81",
        "uomId": "2501"
      },
      {
        "metricId": "86",
        "uomId": "2600"
      }
    ],
    "images": null,
    "files": null,
    "auditInfo": {
      "createdBy": {
        "id": "318",
        "name": "Alex Rivera"
      },
      "createdDate": "2026-01-14T08:36:16.120973Z",
      "lastModifiedBy": {
        "id": "318",
        "name": "Alex Rivera"
      },
      "lastModifiedDate": "2026-01-14T08:36:16.120973Z"
    }
  }
}
```

| Field | Type | Description |
| --- | --- | --- |
| `data.id` | string | Data source ID. |
| `data.name` | string | Display name. |
| `data.description` | string (nullable) | Free-text description. |
| `data.externalId` | string (nullable) | Your own identifier for this data source, if one was set. |
| `data.type` | object | `{ id, name }` — what kind of data source it is, e.g. `Form`, `Power Meter`. |
| `data.applying` | object | `{ id, name }` — how it is used: `1` Sensor, `2` form, `7` AI Vision. |
| `data.site` | object | `{ id, name, channelId }` for the owning site. |
| `data.tzTimezoneName` | string | IANA time zone, e.g. `US/Pacific`. `offset` is the same thing in minutes. |
| `data.validationStatus` | object | `{ id, name }` — where the data source is in validation. In the list endpoint this same field is a bare number. |
| `data.activityStatus` | object | `{ id, name }` — whether it is actively reporting, e.g. `Active`, `Pending Readings`. |
| `data.collector` | object (nullable) | What collects the data. `collectorType` says whether Zira pulls it or the device pushes it. |
| `data.inactiveThreshold` | number (nullable) | Seconds of silence after which the data source counts as inactive. |
| `data.readingInterval` | number (nullable) | Expected seconds between readings. `null` for push sources. |
| `data.collectionEnabled` | boolean | Whether collection is currently switched on. |
| `data.channelId` | string | Channel that carries this data source’s feed. |
| `data.displayUoms` | array (nullable) | Per-metric unit choices, as `{ metricId, uomId }`. |
| `data.meterSchema` | object (nullable) | Only present with `withSchema=true`. Holds `metrics[]`, each with its `metric` `{ id, name }`, `uom`, `displayName` and `isRequired` — this is where you map metric IDs to names. |
| `data.formConfig` | object (nullable) | Present on form data sources. Describes the fields operators fill in, with `order`, `required` and a `properties` map. |
| `data.cv` | object (nullable) | Present on camera data sources. Holds vision configuration such as counting lines, shifts and posting intervals. |
| `data.auditInfo` | object | `createdBy`, `createdDate`, `lastModifiedBy`, `lastModifiedDate`. |

### Good to know

- Add `withSchema=true` to get `meterSchema`. That is how you map the numeric metric IDs used by `GET /reading` and `POST /reading` to human-readable names.
- Metrics that Zira calculates for you are left out of the schema, because you cannot write to them.
- Add `withLastReading=true` to get the most recent reading inline, instead of making a separate `GET /reading` call.
- `withSchema=true` on a data source that has no schema fails with a server error rather than returning an empty schema.
- The payload varies by type: forms carry `formConfig`, cameras carry `cv`, metered devices carry connection fields such as `ipAddress`, `port` and `modbus`. Read the blocks you need and ignore the rest.
- Both flags are compared against the literal string `true` — `withSchema=1` or `withSchema=yes` will not work.

## Errors

Failures return a JSON body with a `message` and an `internalErrorCode`, at the status shown below. Whenever the underlying error carries structured detail — which every schema-validation failure does — the body is replaced with a generic `Internal server error.` / `02-001` pair while the real status code is kept. Branch on the HTTP status and on `internalErrorCode`; never parse the message text.

```json
{
  "message": "Internal server error.",
  "internalErrorCode": "02-001"
}
```

| Status | Meaning |
| --- | --- |
| `400` | The request failed validation — a missing required field, a field the schema does not allow, an unparseable body, a value out of range, or a malformed `lastValue`. |
| `401` | The API key resolved to a user context that is not allowed to read or write the record you asked for. |
| `403` | The `x-api-key` header is missing or is not a recognised key. API Gateway rejects the call before the endpoint runs, so the body is only `{"message":"Forbidden"}`. |
| `409` | The write conflicts with an existing record, or it references a record that does not exist. |
| `429` | The API key exceeded the rate limit or quota on its usage plan. Also returned by API Gateway rather than the endpoint. |
| `500` | Unexpected server error, or the database returned no result where one was required. |


Fetch a single data source or device by ID.

https://api.zira.us/public/data-sources

Description