Expanding objects

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

# 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):

?expand=editedVersion&expand=publishedVersion
?expand[]=editedVersion&expand[]=publishedVersion

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

What each resource supports

Resource	`expand` options
Content	`editedVersion`, `publishedVersion`
Content version	`questions`, `steps`, `data`, `localizations`
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.

For content versions, steps (flow body) and data (non-flow body) are heavy and only returned when expanded — see Content representation.

localizations inlines the version’s translation status: one entry per non-default project locale with enabled, missing and outdated counts — the check to run before publishing a version whose text you edited. See Localization.

Getting started

Conventions

Concepts

Endpoints

Overview

Usage

What each resource supports

​Overview

​Usage

​What each resource supports

Overview

Usage

What each resource supports