> ## Documentation Index
> Fetch the complete documentation index at: https://docs.usertour.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Expanding objects

> Inline related objects and heavy fields with the expand query parameter.

## Overview

Many v2 responses can inline related objects or heavy fields with the `expand`
query parameter, so you avoid a second request. By default these fields are
omitted (or `null`).

## Usage

```bash theme={null}
# inline the version objects on a content
GET /v2/projects/{projectId}/content/{id}?expand=editedVersion

# decompiled steps on a content version (heavy → opt-in)
GET /v2/projects/{projectId}/content/{contentId}/versions/{id}?expand=steps
```

Request multiple expansions by repeating the parameter (both forms work):

```bash theme={null}
?expand=editedVersion&expand=publishedVersion
?expand[]=editedVersion&expand[]=publishedVersion
```

<Warning>
  Comma-separated values (`?expand=editedVersion,publishedVersion`) are **not**
  supported — pass each value as its own `expand` parameter.
</Warning>

## What each resource supports

| Resource        | `expand` options                                   |
| --------------- | -------------------------------------------------- |
| Content         | `editedVersion`, `publishedVersion`                |
| Content version | `questions`, `steps`, `data`                       |
| Content session | `answers`, `content`, `company`, `user`, `version` |
| User            | `companies`, `memberships`, `memberships.company`  |
| Company         | `users`, `memberships`, `memberships.user`         |
| Theme           | `settings`, `variations`                           |

A **dotted** option expands one level deeper: `memberships.company` inlines each
membership **and** the company on it (it implies `memberships`). The same goes for
`memberships.user` on a company.

<Note>
  For content versions, `steps` (flow body) and `data` (non-flow body) are heavy
  and only returned when expanded — see
  [Content representation](/api-reference-v2/content-representation).
</Note>