# Collections

Collections enable you to store information to Stream. This allows you to use it inside your feeds, and to provide additional data for the personalized endpoints. Examples include products and articles, but any unstructured object (e.g. JSON) is a good match for collections.

Collection entries can be embedded inside activities and used to store nested data inside activities. When doing so, Stream will automatically enrich your activities with the current version of the data (see later section). Collection endpoints can be used both client-side and server-side except the batch methods that are only available server-side.

## Adding Collections

This method allows you to create a new entry on a named collection.

### Parameters

| name       | type   | description                                                          | default | optional |
| ---------- | ------ | -------------------------------------------------------------------- | ------- | -------- |
| collection | string | The name of the collection                                           | -       |          |
| entry_id   | string | The id of the entry, if not given an ID will be generated by Stream. | -       | ✓        |
| data       | object | The data related to the user                                         | -       |          |

```js label="JavaScript"
await client.collections.add("food", "cheese-burger", {
  name: "Cheese Burger",
  rating: "4 stars",
});

// if you don't have an id on your side, just use null as the ID and Stream will generate a unique ID
await client.collections.add("food", null, {
  name: "Cheese Burger",
  rating: "4 stars",
});
```

<Admonition type="info">

The max size of a collection can not exceed 50kB

</Admonition>

## Retrieving Collections

After adding an entry to a collection, you can also retrieve it easily by its ID.

### Parameters

| name       | type   | description                | default | optional |
| ---------- | ------ | -------------------------- | ------- | -------- |
| collection | string | The name of the collection | -       |          |
| entry_id   | string | The id of the entry        | -       |          |

```js label="JavaScript"
let response = client.collections.get("food", "cheese-burger");
```

## Removing Collections

An entry can also be removed from a collection with its ID.

### Parameters

| name       | type   | description                | default | optional |
| ---------- | ------ | -------------------------- | ------- | -------- |
| collection | string | The name of the collection | -       |          |
| entry_id   | string | The id of the entry        | -       |          |

```js label="JavaScript"
let response = client.collections.delete("food", "cheese-burger");
```

<Admonition type="info">

When you delete an entry from a collection any references will be converted to a missing reference error when reading feeds with [enrichment](https://getstream.io/activity-feeds/docs/node/v2/collections-enrichment/).

</Admonition>

## Updating Collections

A collection's entry data can be updated. Updates are propagated instantly to all activities embedding the entry.

### Parameters

| name       | type   | description                  | default | optional |
| ---------- | ------ | ---------------------------- | ------- | -------- |
| collection | string | The name of the collection   | -       |          |
| entry_id   | string | The id of the entry          | -       |          |
| data       | object | The data related to the user | -       |          |

```js label="JavaScript"
await client.collections.update("food", "cheese-burger", {
  name: "Cheese Burger",
  rating: "1 star",
});
```


---

This page was last updated at 2026-08-07T20:37:30.900Z.

For the most recent version of this documentation, visit [https://getstream.io/activity-feeds/docs/javascript/v2/collections-introduction/](https://getstream.io/activity-feeds/docs/javascript/v2/collections-introduction/).