# Acoustic Delivery render API

**Canonical:** https://apis.io/apis/acoustic/acoustic-delivery-render-api/  
**Provider:** Acoustic — https://apis.io/providers/acoustic/  
**Base URL:** https://content-us-1.content-cms.com/api/{tenantId}  
**Documentation:** https://developer.goacoustic.com/acoustic-content/

Acoustic Delivery render API is one of 33 APIs that [Acoustic](https://apis.io/providers/acoustic/) publishes on the [APIs.io](https://apis.io/) network, described by a machine-readable OpenAPI specification. Tagged areas include Delivery render. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, an API reference, and a getting-started guide.

The Content Delivery rendering REST API provides information to render content and pages in client-side applications. **Client-side programming support** If you want to create a client-side application with Angular 4, you can use the [Acoustic Angular SDK for Content](https://www.npmjs.com/package/@acoustic-content-sdk/ng-api). With the Angular SDK, you can retrieve and render content and pages from Content without any need to interact with the REST API directly. **Conditional GET requests** The API supports ETag and Last-modified [conditional GET requests](https://developer.mozilla.org/en-US/docs/Web/HTTP/Conditional_requests). It is highly recommended to use conditional GET requests with ETags to decrease the communication data between client and API. The API provides ETag and Last-modified header response information if available. The client can send conditional GET requests with ETag and Last-modified information to validate local client data. The API responds with a `304 - Not modified response` with empty content if the condition is still valid. **JSONP support** The API has [JSONP support](https://www.w3schools.com/js/js_json_jsonp.asp). The client can activate the JSONP support by providing the JSONP callback name query parameter. **Preview support** The API supports the previewing of content information as described [here](https://developer.goacoustic.com/acoustic-content/docs/preview-content). **Usage** In order to render content and the page structure in client-side applications you must to consider the following aspects: * Identify the addressed page that correlates to the application routing state. * Identify the addressed content and layout information and render the content. With the following steps you can achieve these aspects: 1. Retrieve the site and page information by using the "Delivery Site By ID" API route. The response contains information to identify the page that correlates to the navigational state (route) of the application. 2. The page information has the property "contentId" that references the content of the page. Use that property to get the content ID. 3. Use the content ID in combination with the "Delivery Rendering Context By ID" API route to retrieve the rendering context information of the content item. The rendering context contains the layout information of the content item and content references, including the resolved rendering context of the referenced items. 4. Based on the provided layout information, identify the related the layout component of your application and render the content item by using the layout component. If required the layout can render nested layouts.

## Machine-readable artifacts (10)

- **OpenAPI** — https://raw.githubusercontent.com/api-evangelist/acoustic/refs/heads/main/openapi/acoustic-delivery-render-api-openapi.yml
- **Swagger** — https://raw.githubusercontent.com/api-evangelist/acoustic/refs/heads/main/openapi/acoustic-content-swagger2-original.yaml
- **Documentation** — https://developer.goacoustic.com/acoustic-content/docs
- **APIReference** — https://developer.goacoustic.com/acoustic-content/reference
- **GettingStarted** — https://developer.goacoustic.com/acoustic-content/reference/get-started
- **ErrorCatalog** — https://raw.githubusercontent.com/api-evangelist/acoustic/refs/heads/main/errors/acoustic-problem-types.yml
- **Conventions** — https://raw.githubusercontent.com/api-evangelist/acoustic/refs/heads/main/conventions/acoustic-conventions.yml
- **DataModel** — https://raw.githubusercontent.com/api-evangelist/acoustic/refs/heads/main/data-model/acoustic-data-model.yml
- **Webhooks** — https://raw.githubusercontent.com/api-evangelist/acoustic/refs/heads/main/asyncapi/acoustic-webhooks.yml
- **LLMsTxt** — https://raw.githubusercontent.com/api-evangelist/acoustic/refs/heads/main/llms/acoustic-llms.txt

## Other Acoustic APIs (12)

- [Acoustic Campaign REST API](https://apis.io/apis/acoustic/acoustic-campaign-rest-api/)
- [Acoustic Campaign XML API](https://apis.io/apis/acoustic/acoustic-campaign-xml-api/)
- [Acoustic Connect API](https://apis.io/apis/acoustic/acoustic-connect-api/)
- [Acoustic Personalization](https://apis.io/apis/acoustic/acoustic-personalization/)
- [Acoustic Administering user profiles API](https://apis.io/apis/acoustic/acoustic-administering-user-profiles-api/)
- [Acoustic Authoring assets API](https://apis.io/apis/acoustic/acoustic-authoring-assets-api/)
- [Acoustic Authoring categories API](https://apis.io/apis/acoustic/acoustic-authoring-categories-api/)
- [Acoustic Authoring changes API](https://apis.io/apis/acoustic/acoustic-authoring-changes-api/)
- [Acoustic Authoring comments API](https://apis.io/apis/acoustic/acoustic-authoring-comments-api/)
- [Acoustic Authoring content API](https://apis.io/apis/acoustic/acoustic-authoring-content-api/)
- [Acoustic Authoring context search API](https://apis.io/apis/acoustic/acoustic-authoring-context-search-api/)
- [Acoustic Authoring image profiles API](https://apis.io/apis/acoustic/acoustic-authoring-image-profiles-api/)

## Tags

Delivery render

---

Profiled by [API Evangelist](https://apievangelist.com) and published on [APIs.io](https://apis.io/apis/acoustic/acoustic-delivery-render-api/). The API's provider profile, Kin Score and agent-readiness rating are at https://apis.io/providers/acoustic/.