New Endpoints for Managing Content Item Versions with the Sitecore Content Items API

Published on : November 18, 2026

Content management is an ongoing process. Websites frequently require content updates, campaign changes, localization, and improvements to existing pages. However, managing different versions of content across a large digital platform can become challenging, especially when multiple teams and automated workflows are involved.

To make this process more flexible, SitecoreAI introduced three new endpoints for managing content item versions through its Content Items API on November 10, 2026.

These new capabilities allow developers to create, retrieve, and delete individual content item versions programmatically. Instead of relying entirely on manual version management, development teams can integrate version-related operations directly into their applications, automation processes, and content management workflows.

For businesses using SitecoreAI, this is a useful improvement toward more controlled, scalable, and efficient content operations.

What Is the Sitecore Content Items API?

The Sitecore Content Items API is a REST API that allows developers to manage structured content within a SitecoreAI environment.

A content item represents an individual piece of structured content created using a content type (data template). It can contain information such as page content, product details, descriptions, metadata, and other fields used across digital experiences.

Using the Content Items API, developers can perform several content management operations, including:

  • Creating new content items.
  • Retrieving existing content items.
  • Updating or replacing content.
  • Deleting content items.
  • Searching and listing content items.
  • Validating content against configured rules.
  • Managing content hierarchies.
  • Translating content into different languages.

The newly introduced version-management endpoints extend these capabilities by providing direct programmatic control over individual content item versions.

What Is New in the Sitecore Content Items API?

SitecoreAI has introduced three dedicated endpoints to simplify content version management.

These endpoints address three important requirements: creating new versions, retrieving available versions, and removing versions that are no longer required.

1. Create a Content Item Version

HTTP Method: POST

Endpoint:
/api/v1/content-items/{id}/versions

The new create-version endpoint allows developers to create a new version of an existing content item.

One useful feature is the ability to specify which existing version should be used as the starting point. Developers can provide a baseVersion value to copy content from a particular version. If this value is omitted, Sitecore uses the latest available version as the source.

The request also supports:

  • language: Specifies the language of the new content version.
  • baseVersion: Identifies the source version from which content values should be copied.
  • versionName: Provides an optional custom label for the new version.

For example, a marketing team preparing an autumn promotional campaign could create a new content version using the existing website content as a starting point. Developers can label that version “Autumn campaign” to make it easier to identify.

This approach helps teams prepare content changes while maintaining a structured version history.

2. List Content Item Versions

HTTP Method: GET

Endpoint:
/api/v1/content-items/{id}/versions

The list-version endpoint retrieves the available stored versions of a specific content item.

This is particularly useful when developers need to understand the version history before performing an update, creating another version, or cleaning up older content.

The API response can include information such as:

  • Content item ID.
  • Language associated with each version.
  • Version number.
  • Custom version name.
  • Revision identifier.
  • Creation and modification timestamps.
  • User information associated with content changes.
  • Available permissions.

Developers can also use the optional language query parameter to filter versions by language. When this parameter is omitted, versions across all languages are returned.

For example, a multilingual website may maintain English, French, and German versions of the same content item. Developers can retrieve the available versions and organize content management operations accordingly.

This improves visibility into content history and makes automated version-management workflows easier to implement.

3. Delete a Content Item Version

HTTP Method: DELETE

Endpoint:
/api/v1/content-items/{id}/versions/{versionNumber}/{language}

The delete-version endpoint allows developers to remove a specific content item version by identifying its item ID, version number, and language.

This capability can be useful when managing outdated drafts, removing unnecessary versions, or implementing automated content cleanup processes.

For example, a business may maintain multiple versions of campaign content during a promotional period. Once certain versions are no longer needed, an authorized workflow can identify and remove the specified versions.

The endpoint returns a successful HTTP 204 response when the version is deleted. No response body is returned.

However, version deletion should always be handled carefully. Development teams should verify the selected version, language, permissions, and business retention requirements before executing deletion requests.

How These New Endpoints Improve Content Management

The latest Sitecore Content Items API endpoints provide practical benefits for organizations managing large content environments.

Better Content Version Control

Content teams frequently make changes to existing pages, product information, and campaign content. Creating separate versions makes it easier to maintain identifiable content states.

Developers can now create and retrieve versions through API requests, supporting more structured content management processes.

Improved Workflow Automation

Manual version management can introduce repetitive tasks, particularly when teams maintain multiple websites or large content libraries.

With the new endpoints, developers can integrate version creation, retrieval, and deletion into automated workflows. This can reduce repetitive manual operations and improve consistency.

Easier Multilingual Content Management

Organizations operating across multiple markets often maintain different language versions of their digital content.

The ability to retrieve versions across languages or create a version for a specified language provides additional flexibility when building multilingual content management integrations.

More Efficient Content Maintenance

Over time, websites can accumulate outdated content versions that are no longer required.

The delete-version endpoint provides a programmatic way to manage selected versions, helping development teams implement controlled content maintenance processes.

Better Integration with Custom Applications

Organizations often build custom dashboards, editorial tools, marketing platforms, and internal applications around their CMS.

The new endpoints provide additional integration opportunities, allowing developers to incorporate content version management into these applications instead of depending entirely on manual CMS operations.

Authentication and API Integration Considerations

Before using the Sitecore Content Items API, developers must configure the appropriate authentication credentials.

SitecoreAI uses environment automation client credentials to generate a JSON Web Token (JWT) for API authorization.

The general integration process involves:

  1. Accessing SitecoreAI Deploy through the Sitecore Cloud Portal.
  2. Creating automation credentials for the required environment.
  3. Obtaining the client ID and client secret.
  4. Requesting a JWT through the Sitecore authentication service.
  5. Including the JWT as a Bearer token in API request headers.
  6. Calling the required Content Items API endpoint.

Example authentication header:

Authorization: Bearer YOUR_JWT

Developers should also consider the following implementation practices:

  • Store client credentials securely rather than exposing them in frontend applications.
  • Use appropriate permissions for version creation and deletion.
  • Handle unauthorized, forbidden, and not-found API responses.
  • Refresh expired JWTs when necessary.
  • Validate the target content item and language before performing operations.
  • Maintain appropriate logging for version creation and deletion activities.
  • Test API integrations in a development environment before production deployment.

These practices help ensure that automated content operations remain secure, predictable, and maintainable.

Practical Use Cases for Businesses

The new Sitecore Content Versioning API capabilities can support several real-world business scenarios.

Marketing campaign management: Marketing teams can create dedicated content versions for seasonal campaigns, promotional landing pages, and product launches without repeatedly rebuilding content from scratch.

Enterprise website management: Organizations managing multiple websites can integrate version operations into centralized content administration tools.

Multilingual digital experiences: Development teams can retrieve and manage content versions across different languages, supporting international website operations.

Automated publishing preparation: Custom workflows can create new versions before content review and subsequent publishing activities. Version creation itself does not mean that content has been published.

Content governance: Teams can build controlled processes for reviewing version history and removing selected outdated versions according to their internal retention policies.

These use cases demonstrate how API-driven version management can support more flexible enterprise content operations.

What Should Developers Consider Before Implementing These Endpoints?

Although the new endpoints simplify version management, successful implementation requires careful planning.

First, developers should understand the relationship between content item IDs, version numbers, languages, and revision identifiers. These values serve different purposes and should not be treated as interchangeable.

Second, creating a new version copies content values from the selected source version. Teams should understand which version is being used as the baseline before making further changes.

Third, deleting a version is a separate operation from deleting an entire content item. Developers should implement appropriate checks to avoid removing the wrong version.

Finally, organizations should establish clear content governance policies covering version naming, review processes, access permissions, and retention requirements.

Following these considerations can help businesses take advantage of the new API capabilities without introducing unnecessary risks into their content operations.

How Skybridge Infotech Helps Businesses with Sitecore Development

At Skybridge Infotech, we help businesses build, improve, and maintain scalable digital experiences using modern enterprise technologies.

Our Sitecore development expertise covers CMS implementation, custom API integrations, content architecture, website development, migration, and ongoing platform optimization.

As Sitecore continues to introduce new API capabilities, businesses have more opportunities to automate content operations and improve the way their digital platforms are managed.

Our team can help organizations evaluate these improvements, integrate relevant APIs, develop custom content management workflows, and strengthen their existing Sitecore environments.

Whether you are upgrading an existing Sitecore implementation or building a new enterprise digital experience, the right technical approach can help create a more flexible and maintainable content ecosystem.

Looking to improve your Sitecore content management workflows? Connect with Skybridge Infotech to explore Sitecore development and API integration solutions.

Frequently Asked Questions (FAQs)

1. What is the Sitecore Content Items API?

The Sitecore Content Items API is a REST API that allows developers to create, retrieve, update, delete, validate, and manage structured content items within a SitecoreAI environment.

2. What are the new Sitecore Content Items API endpoints?

Sitecore introduced three new endpoints for managing content item versions: create a version using POST, list versions using GET, and delete a specific version using DELETE.

3. Can developers create a new content version using an existing version?

Yes. Developers can specify the baseVersion parameter to create a new version using an existing version as the source. If omitted, the latest version is used.

4. Can the Content Items API retrieve versions in different languages?

Yes. The list-version endpoint supports an optional language parameter. Without this parameter, versions across all available languages are returned.

5. Does creating a new content version automatically publish it?

No. Creating a new version and publishing content are separate operations. A new version does not automatically become publicly available.

6. How can businesses benefit from the Sitecore Content Versioning API?

Businesses can use it to automate version creation, retrieve content history, support multilingual workflows, manage outdated versions, and integrate content operations into custom applications.

7. Does the new version-management functionality require API authentication?

Yes. The Content Items API uses environment automation client credentials and JWT-based Bearer authentication.

Conclusion

The introduction of new version-management endpoints is a useful improvement to the Sitecore Content Items API. By supporting programmatic version creation, retrieval, and deletion, SitecoreAI gives developers greater flexibility when building automated content management solutions.

For enterprises managing complex websites, multilingual experiences, and frequent content updates, these capabilities can help streamline workflows and improve content governance.

With the right implementation strategy, businesses can use the Sitecore Content Versioning API to build more efficient, scalable, and maintainable digital experiences.

Skybridge Infotech helps businesses unlock the potential of Sitecore through enterprise CMS development, API integration, and digital experience solutions.

Scroll to Top