Skip to main content
POST
Migrate Content
Updates content to use a newer ContentType version, updating the derived packageVersion and validating against the new schema.

Path Parameters

string
required
Organization ID
string
required
Project ID
string
required
Content ID

Request Body

number
required
The ContentType version to migrate to

Example Request

Response

Returns the updated Content object with the new typeVersion and derived packageVersion.
Migration changes the typeVersion and packageVersion. The content’s status changes to modified and must be published to make the migration live. Ensure the content is compatible with the new schema before publishing.

Error Responses

ContentType Version Not Found

Validation Failed

If the content doesn’t match the new schema:

Cannot Downgrade

Code Examples