A _channel_ is a site that can be managed in the [Experience Manager](🔗) app by users with the Site Editor role.
Channel is the "root" entity in the [site configuration model](🔗): all other entities in the model exist as part of a specific channel.
A channel's configuration includes a content root. Any content paths configured in the entities that are part of that channel are relative to that content root.
Additionally, a channel configuration can include custom parameters that are user-configurable in the _Channel properties_ dialog in the Experience manager.
For a full overview of properties, see the [Channel schema](🔗) in the Site Management API reference documentation.
### Platform property placeholders
You can access specific technical values defined by Bloomreach in channel properties using property placeholders. The main purpose is to enable developers to pass these values to their frontend app, so their frontend components can use it.
A placeholder can be used in your channel property values as follows:
The available placeholders are listed in the table below:
|`||Endpoint URL for Bloomreach Discovery APIs.|
|`||Bloomreach Discovery account ID.|
|`||Bloomreach Discovery account name.|
|`||Base URL of the [GraphQL Commerce API](🔗).|
|`||Base URL of the default shared hosted frontend app for the [Reference SPA channel template](🔗).|
|`||Base URL of the default shared hosted frontend app for the [SAP Spartacus channel template](🔗).|
|`||Base URL of the default shared hosted frontend app for the [Vue Storefront channel template](🔗).|
### Example JSON representation
The example below shows the JSON representation of the default channel in the sample application:
The [Site Management API](🔗) currently supports [Channel Operations](🔗), but not create and delete. The creation of new channels is handled inside the Commerce Experience Cloud web interface: a user with the Site Admin role can create new (almost empty) channels in the channel overview of the Experience manager app.
Modification of channel configuration is only allowed in the context of a [development project](🔗). As such, it is a prerequisite for using the API, that a development project for your channel exists. The _Channels_ tab of the _Projects_ app displays the branch ID, a sequence of 4 random alphanumeric characters prefixed with a 'v' (for example: "vIUy9"), which must be used in combination with the channel ID, separated by a dash (for example: "brxsaas-vIUy9").
The API additionally supports the management of a channel’s configuration parameters and their grouping in the _Channel properties_ dialog through field groups.
See [Channel Operations](🔗) in the Site Management API reference documentation for a list of operations.
You can find examples of using the channel endpoints in the [Postman Collection](🔗).