1. SitecoreAI

Extending SitecoreAI

SitecoreAI is a cloud-native, SaaS content management system designed to help you create and manage digital experiences efficiently.

SitecoreAI is an API‑first platform. You extend it by integrating external services and applications, rather than modifying the platform runtime.

You extend SitecoreAI by:

  • Using APIs to read and update data.
  • Using webhooks to react to events.
  • Implementing custom logic in external applications or services.

This approach enables you to build flexible, scalable solutions while maintaining compatibility with the managed SaaS environment.

Important

SitecoreAI does not support deploying custom in-process code to the platform. Customisations should be implemented using supported extension points.

How extensibility works

SitecoreAI follows an event-driven and API-based architecture:

  1. An event occurs in SitecoreAI (for example, a content item is created or updated).

  2. A webhook sends a notification to an external endpoint.

  3. An external service processes the event.

  4. The service uses SitecoreAI APIs to read or update data as needed.

This model separates platform behaviour from custom logic and enables integration with other systems.

Before you start

Before you start extending SitecoreAI:

You can also build tailored solutions within the platform by defining content models, creating layouts and renderings, and assigning content to renderings through datasources.

Built-in extension capabilities

You can extend your implementation of SitecoreAI using the following capabilities:

APIs

Use APIs to interact with SitecoreAI data and functionality.

  • Authoring and Management GraphQL API – create custom authoring experiences with personalised dialogs and user interfaces
  • REST APIs – automate and manage operations such as creating and updating sites, deployments, and publishing workflows

Webhooks

Use webhooks to receive real-time notifications when events occur in SitecoreAI.

  • React to content, publishing, or workflow events.
  • Trigger external processing.
  • Integrate with third-party systems.

Webhooks send event data to an external endpoint, where it can be processed by a service or application. For more information, see Webhooks.

External services

Use external services to implement custom business logic.

External services typically:

  • Receive webhook events.
  • Execute custom logic.
  • Call SitecoreAI APIs to perform actions.

Examples include:

  • Integrating with third-party systems
  • Automating workflows across platforms
  • Processing content changes

Content SDK

Use the Content SDK to fetch SitecoreAI data and build front-end applications.

The SDK provides APIs and services that enable you to:

  • Retrieve content.
  • Build pages using a JavaScript framework.
  • Deliver content across channels.

Sitecore PowerShell Extensions

The Sitecore PowerShell Event Handler integration provides a way to execute scripts when defined events are fired.

Extending with Sitecore Marketplace

You can enhance your SitecoreAI implementation by integrating apps from the Sitecore Marketplace.

These applications allow you to:

  • Add additional functionality.
  • Integrate with third-party services.
  • Extend user experiences through apps and extensions.

Marketplace apps integrate with SitecoreAI’s API-first architecture and do not require modifying the core platform.

Examples include:

  • Advanced analytics tools
  • Personalisation capabilities
  • Integrations with external systems

Choosing an approach

Use the following guidance when deciding how to extend SitecoreAI:

ScenarioRecommended approach
React to eventsWebhooks
Read or update content and dataAPIs
Implement business logicExternal services
Build integrations or user interfacesApps, SDKs, or front-end frameworks

Marketplace recipes

The following Marketplace recipes can help you extend SitecoreAI:

Best practices

  • Implement custom logic outside the platform.
  • Use webhooks to trigger external processing rather than performing work in the platform.
  • Use APIs for all data access and updates.
  • Design integrations to be loosely coupled and event-driven.
  • Avoid relying on in-process customisation patterns.
If you have suggestions for improving this article, let us know!