---
title: "GET /feeds"
method: GET
path: "/feeds"
tags: ["Feeds"]
---

# GET /feeds

`GET /feeds`

This endpoint allows developers to list and retrieve information about the feeds that are generated by a device.  
It is important to note that after using the pageSize parameter, the "totalSize" in the response represents the  total number of available feeds, not the number of feeds resulting from the query string.

## Query parameters

- `deviceId` string
- `deviceId__in` string[]
- `type` 'main' | 'preview' | 'talkdown'
- `include` string[]
- `pageToken` string
- `pageSize` integer

## Response `200`

OK

- ApiPaginatedFeedResponse — Used to wrap results for a paginated response, containing information on how to retrieve further pages.
  - `nextPageToken` string, nullable, required — Token to retrieve the next page. The value of this token is passed into the field pageToken. This value can be null if there is no next page.
  - `prevPageToken` string, nullable, required — Token to retrieve the previous page. The value of this token is passed into the field pageToken. This value can be null of there is no previous page.
  - `results` object[], required — The result set from a collection API call.
    - `id` string, required — Identifier of the feed
    - `type` 'main' | 'preview' | 'talkdown', required — Multiple feeds can be published per source, but they should all have the same viewpoint. They can differ in: * quality: `main` is higher resolution while `preview` is low resolution and low framerate * trigger: some generate frames continuously, while others only generate frames when something specific is visible such as a license plate.
    - `deviceId` string, required — The device generating the feed
    - `mediaType` 'audio' | 'video' | 'image' | 'halfDuplex' | 'fullDuplex', required — What type of media is being generated
    - `flvUrl` string, nullable — Flash video delivered over HTTPS can be used to provide live streams, but also play back recordings.
    - `rtspUrl` string — RTSP is a protocol to request media to be sent, and to multiplex that media over one or more connections back to the client.
    - `rtspsUrl` string — Same as RTSP, but communication happens over a TLS socket instead of an unencrypted TCP socket.
    - `localRtspUrl` string, nullable — Same as RTSP, but this time requested directly to the bridge instead of the cloud.
    - `hlsUrl` string, nullable — Http Live Streaming can be used to deliver a live stream over HTTPS.
    - `multipartUrl` string — Proprietary protocol that uses multipart over HTTPS to deliver raw encoded image, video and audio frames as they become available
    - `webRtcUrl` string, nullable — WebRTC can be used to set-up push to talk connections with speakers.
    - `audioPushHttpsUrl` string, nullable — Audio push url can be used to push the audio to the speaker associated with a camera.
  - `totalSize` integer, required — Size of the total result set.

## Other responses

- `400` — The supplied object is invalid. Error detail will contain the validation error.
- `401` — You are not authenticated. Please authenticate and try again.
- `403` — You have no permission to access the specified resource.
- `404` — Referenced resource could not be found.
- `500` — Something went wrong in the server. Please try again.

---

[API](https://skmtc.net/eagleeyenetworks/apis/devices.md) · [All operations](https://skmtc.net/eagleeyenetworks/apis/devices/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/eagleeyenetworks/devices/revisions/df57313de545/schema)