Before you can get a public URL, make sure that the enhanced CMS workspace that contains your media content has a public channel associated with it. To create a channel, see Create and Manage CMS Channels. To add a channel to a workspace, see Add or Remove a Channel from a CMS Workspace. To view the CMS Channels Tab, see How to Enable CMS for your User Profile and Make CMS Tabs Visible
The public URL contains your org ID, the channel ID for the public channel where your content is published, and the content key for your media content.
To get the channel ID, you can use this API or follow these steps in the UI.
2. Open the Developer Tools in your browser. In Chrome, press press Ctrl + Shift + i (Windows) or Cmd + Opt +i (macOS).
3. Within the developer tools, click the Network tab (1), and click the circle with a slash through it (2) to clear the log.
4. In the CMS Channels list, find your public channel, click the row level action, and then click Edit.
5. When the channel settings open, go to the developer tools and click the search bar, or press Ctrl + f (Windows) or Cmd + f (macOS).
6. Enter “0ap” in the search bar to find the channel ID (1). The ID starts with “0ap” and is 18 characters long, such as “0apfI000000F4hhQAC”.
7. Copy and paste the 18 character ID (2) in a place where you can find it later, and then delete the last 3 characters from it. Now you have a channel ID of 15 characters for your URL.
Create the Public URL
The Public URL is in the format of:
<org domain>/cms/delivery/media/<content key>?channelId=<15 character channel id>&oid=<15 character organization Id>
For example:
https://mycompanydomain.my.salesforce.com/cms/delivery/media/MCL3UQA5X2WVGXNKVOALZQHZRKLE?channelId=0apfI000000G4hh&oid=00DfI00000B8FqX
If you need a public URL for any content that’s published to the same public channel, you can use the same URL, and replace the <content key> with the new content key.
004519190

We use three kinds of cookies on our websites: required, functional, and advertising. You can choose whether functional and advertising cookies apply. Click on the different cookie categories to find out more about each category and to change the default settings.
Privacy Statement
Required cookies are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security cookies.
Functional cookies enhance functions, performance, and services on the website. Some examples include: cookies used to analyze site traffic, cookies used for market research, and cookies used to display advertising that is not directed to a particular individual.
Advertising cookies track activity across websites in order to understand a viewer’s interests, and direct them specific marketing. Some examples include: cookies used for remarketing, or interest-based advertising.