# Acoustic Authoring content API

**Canonical:** https://apis.io/apis/acoustic/acoustic-authoring-content-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 Authoring content 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 Authoring content. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, an API reference, and a getting-started guide.

## General Use the Content content authoring data service Rest APIs to work with content documents. Content includes items that you compose in your content hub and upload from outside your content subscription. You can create, retrieve, and update content documents in a database. You can also create draft versions, change the status, and get a count of the total content in your database. ## Content workflow (status) The status of a content item can be determined by the **suffix** of the ID: - An ID like xxxx:**draft** indicates that the item is a draft. This is the initial status of a new content item until it is published. A draft of a published content item will also have this suffix. - An ID like xxxx:***[publishing_job_id]*** - indicates that the content item has been scheduled for publish in the given publishing job. - An ID like xxxx with no suffix indicates that the content is **published** or **retired**. A draft can be created from published. When such a draft is published, it will override the previously published content. **Key notes:** - The base ID (xxxx) does not change. Only the suffix changes according to the workflow status of the item. - Where content and assets are referenced from within a content item, the 'raw' ID form, without a suffix, is always used. For example, when a draft content item is referenced by another draft content item, the reference appears as a raw ID, and thus does not change when the items are published. - API clients should not depend on the ID format and should not attempt to parse it. Instead, the ***linkedDocId*** and ***links*** properties should be used. - Draft item have a property ***linkedDocId***. This is the Id that the draft item will have when it is published. - Draft items that have a published version will have a ***linkedDoc*** property within the ***links*** property. This property will not appear for drafts that do not have a published version.

## Machine-readable artifacts (10)

- **OpenAPI** — https://raw.githubusercontent.com/api-evangelist/acoustic/refs/heads/main/openapi/acoustic-authoring-content-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 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/)
- [Acoustic Authoring Import API](https://apis.io/apis/acoustic/acoustic-authoring-import-api/)

## Tags

Authoring content

---

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