---
title: "Get a Viva Engage community feed"
method: GET
path: "/v1/social/viva/{accountId}/feed"
tags: ["social"]
---

# Get a Viva Engage community feed

`GET /v1/social/viva/{accountId}/feed`

## Request

- Base URL: `https://api.brixsignage.com`
- URL: `https://api.brixsignage.com/v1/social/viva/{accountId}/feed`
- Auth: none required

Get recent messages from a connected Viva Engage community. Pass the community query parameter to select which community to read. Access requires a dt token, issued by the preview-token endpoint or provided automatically to a screen. If the stored access is no longer valid, it is refreshed automatically, and the last known result is served if the community cannot be reached.

**Notes.**
- Feed envelope: `stale` (and `staleSince`) beside `data`. Answers are cached at the edge for a few minutes.

## Path parameters

- `accountId` string, required

## Query parameters

- `dt` string, required
- `community` string, required

## Response `200`

Success.

- object
  - `data` object, required
    - `messages` object[], required
      - `text` string, required
      - `createdAt` string, nullable, required: ISO-8601 timestamp (UTC).
  - `stale` boolean, required: True when the provider failed and this is the last good answer.
  - `staleSince` string: When the stale copy was fetched (only when `stale`).

## Other responses

- `400`: `bad_community`.
- `401`: Missing, expired or revoked bearer token.
- `404`: No such account, or the `dt` token is missing, expired or for another workspace.
- `502`: The provider failed and there is no recent copy to serve.
- `5XX`: Server error. The body carries a `requestId` to quote to support.

---

[API](https://skmtc.dev/brixsignage/apis/brix-api.md) · [All operations](https://skmtc.dev/brixsignage/apis/brix-api/llms.txt) · [OpenAPI document](https://skmtc.dev/brixsignage/apis/brix-api/revisions/02fd3665dc7d?raw)