As a developer, most of your development work occurs outside of Acoustic Content. You use the Content REST APIs to render published assets and content. Published content or assets become available on your subscription's content delivery network. You can then use APIs to retrieve and control the display of elements and assets across channels.

View API information for a content item, asset, or list

To retrieve content, you would need information about those content and assets. When you edit assets or content, click the API information to view it. You can access API information such as item IDs, authoring and delivery URLs, and JSON details.

Delivery URL - You can use the delivery URL to reference content items and assets in applications.

Note: The delivery URL is not active until the content item or asset is published.

Authoring URL - You can reference content items and assets in authoring applications.

Note: Authentication to the authoring APIs is required to use this URL.

Item ID - This ID is unique to the content item or asset and is used to refer to them in the APIs.

You can also view the API information for a list of items, including search or filter parameters. You can then use this information to render a list of content items on a web page or app.

View developer assets

Developers also manage assets that they upload using a command-line interface (CLI). Asset files such as CSS and JavaScript files can be uploaded. You can view a list of developer assets in the product UI from the Developer > Developer files page. You can check the status of these assets and find the scheduled publishing date from this view. The developer assets list is for your information only. To update a file, you must push the file again from your CLI tools.

Developers can control the URL for these developer assets uploaded through wchtools. These developer assets can be placed in any folder under /assets on the file system other than /dxdam. You can then access them from the URL of your domain plus the path under /assets in the file system. For more information, see Host web applications.

The URL for assets added through Content UI is managed by Content. By default, these assets appear under the /dxdam path at a unique path that uses IDs. If you choose to control the URL of your assets, then consider treating them as developer assets.