Acoustic

aid: acoustic
deliveryModel:
  model: saas
  open_source: false
  commercial: true
  callable_host: false
  label: Hosted service · you call their endpoint
  confidence: medium
  source:
  - openapi
  - pricing
  generated: '2026-08-28'
  method: derived
accessModel:
  pricing: paid
  onboarding: sales
  trial: false
  try_now: false
  public: true
  label: Public docs, gated onboarding
  confidence: medium
  source:
  - https://developer.goacoustic.com
  - https://www.acoustic.com/pricing
  generated: '2026-08-13'
  method: searched
image: https://kinlane-images.s3.amazonaws.com/shared/apis-json/icons/acoustic.png
name: Acoustic
description: 'Acoustic is a real-time behavioral marketing platform for B2C companies, delivering omnichannel customer engagement
  across email, SMS, WhatsApp, mobile push and web. Its developer portal at developer.goacoustic.com publishes an RFC 9727
  api-catalog advertising six API products: Acoustic Connect (a GraphQL API for contacts, consent, audiences, product catalog
  and signals), Acoustic Campaign (a long-lived REST + XML API estate inherited from Silverpop, with a live Swagger service
  description per regional pod), Acoustic Content (a headless CMS / digital asset management REST API covering authoring,
  delivery, rendering, publishing and webhooks), Acoustic Personalization (a client-side library for real-time content and
  product recommendations), Acoustic Experience Analytics (Tealeaf) and Acoustic Exchange. Formerly IBM Watson Marketing,
  Acoustic was carved out as an independent martech company and is a portfolio company of Sapphire Ventures.'
url: https://raw.githubusercontent.com/api-evangelist/acoustic/refs/heads/main/apis.yml
x-type: company
x-source: vc-portfolio
x-backed-by:
- sapphire-ventures
x-tier: profiled
x-tier-reason: machine-readable-contracts-harvested
specificationVersion: '0.23'
created: '2026-07-17'
modified: '2026-08-13'
tags:
- Company
- MarTech
- Marketing
- Marketing Automation
- Customer Engagement
- Content Management
- Personalization
- Email
- SMS
- Push Notifications
- Headless CMS
- Digital Asset Management
- Customer Data
- GraphQL
- Consent Management
tags_raw:
- Company
- Martech
- Marketing
- Marketing Automation
- Customer Engagement
- Content Management
- Personalization
- Email
- SMS
- Push Notifications
- Headless CMS
- Digital Asset Management
- Customer Data
- GraphQL
- Consent Management
apis:
- name: Acoustic Campaign REST API
  description: REST API for the Acoustic Campaign (formerly Silverpop Engage) marketing automation platform, covering contact
    databases, relational tables, programs, contact sources, channels (push, SMS, in-app, rich content), messages, web tracking,
    Universal Behaviors (events), event types, organization settings and GDPR job status. Acoustic serves a live, unauthenticated
    Swagger 1.1 service description from every regional pod at /restdoc, and each pod is a separate base host (api-campaign-us-1..6,
    -eu-1, -ap-2, -ap-3, -ca-1).
  humanURL: https://developer.goacoustic.com/acoustic-campaign/reference/rest-api-overview
  baseURL: https://api-campaign-us-1.goacoustic.com/rest
  properties:
  - type: Swagger
    url: openapi/acoustic-campaign-rest-swagger-index.json
  - type: Swagger
    name: Channels
    url: openapi/acoustic-campaign-channels-swagger.json
  - type: Swagger
    name: Contact databases
    url: openapi/acoustic-campaign-databases-swagger.json
  - type: Swagger
    name: Relational tables
    url: openapi/acoustic-campaign-relationaltables-swagger.json
  - type: Swagger
    name: Programs
    url: openapi/acoustic-campaign-programs-swagger.json
  - type: Swagger
    name: Organization settings
    url: openapi/acoustic-campaign-orgs-swagger.json
  - type: Swagger
    name: Contact sources
    url: openapi/acoustic-campaign-contactsources-swagger.json
  - type: Swagger
    name: Universal Behaviors (events)
    url: openapi/acoustic-campaign-events-swagger.json
  - type: Swagger
    name: Event types
    url: openapi/acoustic-campaign-eventtypes-swagger.json
  - type: Swagger
    name: Messages
    url: openapi/acoustic-campaign-messages-swagger.json
  - type: Swagger
    name: Web tracking
    url: openapi/acoustic-campaign-webtracking-swagger.json
  - type: Swagger
    name: GDPR jobs
    url: openapi/acoustic-campaign-gdpr_jobs-swagger.json
  - type: RateLimits
    url: rate-limits/acoustic-rate-limits.yml
  - type: Webhooks
    url: asyncapi/acoustic-webhooks.yml
  - type: APIReference
    url: https://api-campaign-us-1.goacoustic.com/restdoc/
  - type: Documentation
    url: https://developer.goacoustic.com/acoustic-campaign/reference/rest-api-overview
  - type: ErrorCatalog
    url: errors/acoustic-campaign-error-codes.yml
  - type: Authentication
    url: authentication/acoustic-authentication.yml
- name: Acoustic Campaign XML API
  description: The long-lived XML-over-HTTP API for Acoustic Campaign, inherited from Silverpop Engage. A single POST endpoint
    per regional pod accepts XML request documents for contact list management, recipient management, mailing and template
    management, relational tables, scheduling, reporting and data export. Authenticated with OAuth 2 (refresh-token grant)
    or the legacy jsessionid session. Acoustic publishes a public Postman collection for it.
  humanURL: https://developer.goacoustic.com/acoustic-campaign/reference/xml-api-overview-1
  baseURL: https://api-campaign-us-1.goacoustic.com/XMLAPI
  properties:
  - type: Documentation
    url: https://developer.goacoustic.com/acoustic-campaign/reference/xml-api-overview-1
  - type: Postman
    url: https://documenter.getpostman.com/view/1643559/2sBXqQEHNz
  - type: Authentication
    url: authentication/acoustic-authentication.yml
- name: Acoustic Connect API
  description: The GraphQL API for Acoustic Connect — the platform's contact, consent, audience, reference-set, product-catalog,
    product-performance and signal surface. A single POST endpoint at the region host root, authenticated with an X-API-Key
    header generated in Connect under Administration > General settings > API keys. Three regional endpoints (us-east-1, ap-southeast-2,
    eu-central-1). Schema introspection is authentication-gated.
  humanURL: https://developer.goacoustic.com/acoustic-connect/reference/introduction
  baseURL: https://connect-gql-us-1.goacoustic.com/
  properties:
  - type: Documentation
    url: https://developer.goacoustic.com/acoustic-connect/reference/introduction
  - type: GettingStarted
    url: https://developer.goacoustic.com/acoustic-connect/reference/use-connect-api
  - type: ChangeLog
    url: https://developer.goacoustic.com/acoustic-connect/changelog
  - type: Authentication
    url: authentication/acoustic-authentication.yml
- name: Acoustic Personalization
  description: 'Real-time personalization library and APIs for delivering optimized, tailored content to each visitor based
    on behavior and contextual data, with product catalog, recommendations, zones, geolocation and behavioral analytics capture.
    Delivered as a client-side PZN library (MPA script deployment via Exchange Capture, or an npm package for Angular/React
    SPAs distributed from Acoustic''s private Artifactory). Acoustic publishes no callable API host for Personalization: /acoustic-personalization/reference
    returns 404, and the endpoints the library talks to are registered per tenant inside Exchange rather than documented,
    so baseURL is deliberately left unset rather than pointed at a docs page.'
  humanURL: https://developer.goacoustic.com/acoustic-personalization/
  x-baseURL-status: no-usable-base
  x-baseURL-note: Checked 2026-08-13. https://developer.goacoustic.com/acoustic-personalization/reference returns HTTP 404;
    the docs describe a browser library and Exchange-registered endpoints, never a public API host.
  properties:
  - type: Documentation
    url: https://developer.goacoustic.com/acoustic-personalization/docs
  - type: GettingStarted
    url: https://developer.goacoustic.com/acoustic-personalization/docs/quick-start-guide-for-personalization
  - type: Components
    url: components/acoustic-components.yml
- aid: acoustic:acoustic-administering-user-profiles-api
  name: Acoustic Administering user profiles API
  description: The Administering user profiles API from Acoustic — 3 operation(s) for administering user profiles.
  humanURL: https://developer.goacoustic.com/acoustic-content/
  baseURL: https://content-us-1.content-cms.com/api/{tenantId}
  tags:
  - Administering user profiles
  properties:
  - type: OpenAPI
    url: openapi/acoustic-administering-user-profiles-api-openapi.yml
  - type: Swagger
    url: openapi/acoustic-content-swagger2-original.yaml
  - type: Documentation
    url: https://developer.goacoustic.com/acoustic-content/docs
  - type: APIReference
    url: https://developer.goacoustic.com/acoustic-content/reference
  - type: GettingStarted
    url: https://developer.goacoustic.com/acoustic-content/reference/get-started
  - type: ErrorCatalog
    url: errors/acoustic-problem-types.yml
  - type: Conventions
    url: conventions/acoustic-conventions.yml
  - type: DataModel
    url: data-model/acoustic-data-model.yml
  - type: Webhooks
    url: asyncapi/acoustic-webhooks.yml
  - type: LLMsTxt
    url: llms/acoustic-llms.txt
- aid: acoustic:acoustic-authoring-assets-api
  name: Acoustic Authoring assets API
  description: '## General

    Use the Content Asset service Rest APIs to work with assets. Assets are file types that are uploaded or created such as
    an image file, video file, or text that are used in content items. You can create, retrieve, update, and delete assets
    in a database. Managed assets are those located in the root dxdam directory as specified by its path and are visible on
    the Content UI.

    ## 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.'
  humanURL: https://developer.goacoustic.com/acoustic-content/
  baseURL: https://content-us-1.content-cms.com/api/{tenantId}
  tags:
  - Authoring assets
  properties:
  - type: OpenAPI
    url: openapi/acoustic-authoring-assets-api-openapi.yml
  - type: Swagger
    url: openapi/acoustic-content-swagger2-original.yaml
  - type: Documentation
    url: https://developer.goacoustic.com/acoustic-content/docs
  - type: APIReference
    url: https://developer.goacoustic.com/acoustic-content/reference
  - type: GettingStarted
    url: https://developer.goacoustic.com/acoustic-content/reference/get-started
  - type: ErrorCatalog
    url: errors/acoustic-problem-types.yml
  - type: Conventions
    url: conventions/acoustic-conventions.yml
  - type: DataModel
    url: data-model/acoustic-data-model.yml
  - type: Webhooks
    url: asyncapi/acoustic-webhooks.yml
  - type: LLMsTxt
    url: llms/acoustic-llms.txt
- aid: acoustic:acoustic-authoring-categories-api
  name: Acoustic Authoring categories API
  description: Use the Acoustic Content category authoring data service Rest APIs to work with category and taxonomy items.
  humanURL: https://developer.goacoustic.com/acoustic-content/
  baseURL: https://content-us-1.content-cms.com/api/{tenantId}
  tags:
  - Authoring categories
  properties:
  - type: OpenAPI
    url: openapi/acoustic-authoring-categories-api-openapi.yml
  - type: Swagger
    url: openapi/acoustic-content-swagger2-original.yaml
  - type: Documentation
    url: https://developer.goacoustic.com/acoustic-content/docs
  - type: APIReference
    url: https://developer.goacoustic.com/acoustic-content/reference
  - type: GettingStarted
    url: https://developer.goacoustic.com/acoustic-content/reference/get-started
  - type: ErrorCatalog
    url: errors/acoustic-problem-types.yml
  - type: Conventions
    url: conventions/acoustic-conventions.yml
  - type: DataModel
    url: data-model/acoustic-data-model.yml
  - type: Webhooks
    url: asyncapi/acoustic-webhooks.yml
  - type: LLMsTxt
    url: llms/acoustic-llms.txt
- aid: acoustic:acoustic-authoring-changes-api
  name: Acoustic Authoring changes API
  description: Use the Content Authoring Changes Rest APIs to apply changes, including bulk actions, to multiple types of
    Content items.
  humanURL: https://developer.goacoustic.com/acoustic-content/
  baseURL: https://content-us-1.content-cms.com/api/{tenantId}
  tags:
  - Authoring changes
  properties:
  - type: OpenAPI
    url: openapi/acoustic-authoring-changes-api-openapi.yml
  - type: Swagger
    url: openapi/acoustic-content-swagger2-original.yaml
  - type: Documentation
    url: https://developer.goacoustic.com/acoustic-content/docs
  - type: APIReference
    url: https://developer.goacoustic.com/acoustic-content/reference
  - type: GettingStarted
    url: https://developer.goacoustic.com/acoustic-content/reference/get-started
  - type: ErrorCatalog
    url: errors/acoustic-problem-types.yml
  - type: Conventions
    url: conventions/acoustic-conventions.yml
  - type: DataModel
    url: data-model/acoustic-data-model.yml
  - type: Webhooks
    url: asyncapi/acoustic-webhooks.yml
  - type: LLMsTxt
    url: llms/acoustic-llms.txt
- aid: acoustic:acoustic-authoring-comments-api
  name: Acoustic Authoring comments API
  description: Use the Content Authoring comment APIs to work with comments. Comments are a simple way to associate a message
    to an item in Content. Comments are associated with a single item and user (creatorId). An item can have many comments.
    You can create, retrieve, and delete comments from a database.
  humanURL: https://developer.goacoustic.com/acoustic-content/
  baseURL: https://content-us-1.content-cms.com/api/{tenantId}
  tags:
  - Authoring comments
  properties:
  - type: OpenAPI
    url: openapi/acoustic-authoring-comments-api-openapi.yml
  - type: Swagger
    url: openapi/acoustic-content-swagger2-original.yaml
  - type: Documentation
    url: https://developer.goacoustic.com/acoustic-content/docs
  - type: APIReference
    url: https://developer.goacoustic.com/acoustic-content/reference
  - type: GettingStarted
    url: https://developer.goacoustic.com/acoustic-content/reference/get-started
  - type: ErrorCatalog
    url: errors/acoustic-problem-types.yml
  - type: Conventions
    url: conventions/acoustic-conventions.yml
  - type: DataModel
    url: data-model/acoustic-data-model.yml
  - type: Webhooks
    url: asyncapi/acoustic-webhooks.yml
  - type: LLMsTxt
    url: llms/acoustic-llms.txt
- aid: acoustic:acoustic-authoring-content-api
  name: Acoustic Authoring content API
  description: '## 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.'
  humanURL: https://developer.goacoustic.com/acoustic-content/
  baseURL: https://content-us-1.content-cms.com/api/{tenantId}
  tags:
  - Authoring content
  properties:
  - type: OpenAPI
    url: openapi/acoustic-authoring-content-api-openapi.yml
  - type: Swagger
    url: openapi/acoustic-content-swagger2-original.yaml
  - type: Documentation
    url: https://developer.goacoustic.com/acoustic-content/docs
  - type: APIReference
    url: https://developer.goacoustic.com/acoustic-content/reference
  - type: GettingStarted
    url: https://developer.goacoustic.com/acoustic-content/reference/get-started
  - type: ErrorCatalog
    url: errors/acoustic-problem-types.yml
  - type: Conventions
    url: conventions/acoustic-conventions.yml
  - type: DataModel
    url: data-model/acoustic-data-model.yml
  - type: Webhooks
    url: asyncapi/acoustic-webhooks.yml
  - type: LLMsTxt
    url: llms/acoustic-llms.txt
- aid: acoustic:acoustic-authoring-context-search-api
  name: Acoustic Authoring context search API
  description: "The Authoring context search is a discretional middleware service that is positioned before the Search service.\
    \ Use the Authoring context search Rest APIs to retrieve user targeted content items. You can target specific content\
    \ items by providing the condition requests as filters. The filters that are currently supported by the API are  \n1.\
    \ `accept-language` : Use this filter to target content items in a language of your preference.  \n2. `location` : Use\
    \ this filter to target content items that are available in a location, that is, proximity to current location (within\
    \ `distance` radius) of your preference.\n3. `similar` : Use this filter to target content items or assets that are similar\
    \ to a specified item."
  humanURL: https://developer.goacoustic.com/acoustic-content/
  baseURL: https://content-us-1.content-cms.com/api/{tenantId}
  tags:
  - Authoring context search
  properties:
  - type: OpenAPI
    url: openapi/acoustic-authoring-context-search-api-openapi.yml
  - type: Swagger
    url: openapi/acoustic-content-swagger2-original.yaml
  - type: Documentation
    url: https://developer.goacoustic.com/acoustic-content/docs
  - type: APIReference
    url: https://developer.goacoustic.com/acoustic-content/reference
  - type: GettingStarted
    url: https://developer.goacoustic.com/acoustic-content/reference/get-started
  - type: ErrorCatalog
    url: errors/acoustic-problem-types.yml
  - type: Conventions
    url: conventions/acoustic-conventions.yml
  - type: DataModel
    url: data-model/acoustic-data-model.yml
  - type: Webhooks
    url: asyncapi/acoustic-webhooks.yml
  - type: LLMsTxt
    url: llms/acoustic-llms.txt
- aid: acoustic:acoustic-authoring-image-profiles-api
  name: Acoustic Authoring image profiles API
  description: Use the Acoustic Content authoring image profile service Rest APIs to work with image profiles. You can create,
    retrieve, and update image profiles in a database.
  humanURL: https://developer.goacoustic.com/acoustic-content/
  baseURL: https://content-us-1.content-cms.com/api/{tenantId}
  tags:
  - Authoring image profiles
  properties:
  - type: OpenAPI
    url: openapi/acoustic-authoring-image-profiles-api-openapi.yml
  - type: Swagger
    url: openapi/acoustic-content-swagger2-original.yaml
  - type: Documentation
    url: https://developer.goacoustic.com/acoustic-content/docs
  - type: APIReference
    url: https://developer.goacoustic.com/acoustic-content/reference
  - type: GettingStarted
    url: https://developer.goacoustic.com/acoustic-content/reference/get-started
  - type: ErrorCatalog
    url: errors/acoustic-problem-types.yml
  - type: Conventions
    url: conventions/acoustic-conventions.yml
  - type: DataModel
    url: data-model/acoustic-data-model.yml
  - type: Webhooks
    url: asyncapi/acoustic-webhooks.yml
  - type: LLMsTxt
    url: llms/acoustic-llms.txt
- aid: acoustic:acoustic-authoring-import-api
  name: Acoustic Authoring Import API
  description: Provides generic copying and importing functionality
  humanURL: https://developer.goacoustic.com/acoustic-content/
  baseURL: https://content-us-1.content-cms.com/api/{tenantId}
  tags:
  - Authoring Import
  properties:
  - type: OpenAPI
    url: openapi/acoustic-authoring-import-api-openapi.yml
  - type: Swagger
    url: openapi/acoustic-content-swagger2-original.yaml
  - type: Documentation
    url: https://developer.goacoustic.com/acoustic-content/docs
  - type: APIReference
    url: https://developer.goacoustic.com/acoustic-content/reference
  - type: GettingStarted
    url: https://developer.goacoustic.com/acoustic-content/reference/get-started
  - type: ErrorCatalog
    url: errors/acoustic-problem-types.yml
  - type: Conventions
    url: conventions/acoustic-conventions.yml
  - type: DataModel
    url: data-model/acoustic-data-model.yml
  - type: Webhooks
    url: asyncapi/acoustic-webhooks.yml
  - type: LLMsTxt
    url: llms/acoustic-llms.txt
- aid: acoustic:acoustic-authoring-layouts-api
  name: Acoustic Authoring layouts API
  description: 'Use the Content content authoring layout service Rest APIs to work with layouts and layout mappings.


    Layouts define the template for the type documents. They define the markup and how to add content properties and elements
    into the markup. For example, the layouts ''Article'', and ''Event'' would define what an article or event looks like
    on the web site, or email.


    Layout Mappings define an association between a content-type and one or more layouts. Specifically marking those layouts
    as valid for the given content-type.'
  humanURL: https://developer.goacoustic.com/acoustic-content/
  baseURL: https://content-us-1.content-cms.com/api/{tenantId}
  tags:
  - Authoring layouts
  properties:
  - type: OpenAPI
    url: openapi/acoustic-authoring-layouts-api-openapi.yml
  - type: Swagger
    url: openapi/acoustic-content-swagger2-original.yaml
  - type: Documentation
    url: https://developer.goacoustic.com/acoustic-content/docs
  - type: APIReference
    url: https://developer.goacoustic.com/acoustic-content/reference
  - type: GettingStarted
    url: https://developer.goacoustic.com/acoustic-content/reference/get-started
  - type: ErrorCatalog
    url: errors/acoustic-problem-types.yml
  - type: Conventions
    url: conventions/acoustic-conventions.yml
  - type: DataModel
    url: data-model/acoustic-data-model.yml
  - type: Webhooks
    url: asyncapi/acoustic-webhooks.yml
  - type: LLMsTxt
    url: llms/acoustic-llms.txt
- aid: acoustic:acoustic-authoring-library-api
  name: Acoustic Authoring library API
  description: Use the Content library Rest APIs to work with libraries. Libraries currently support having content and asset
    items added to them.
  humanURL: https://developer.goacoustic.com/acoustic-content/
  baseURL: https://content-us-1.content-cms.com/api/{tenantId}
  tags:
  - Authoring library
  properties:
  - type: OpenAPI
    url: openapi/acoustic-authoring-library-api-openapi.yml
  - type: Swagger
    url: openapi/acoustic-content-swagger2-original.yaml
  - type: Documentation
    url: https://developer.goacoustic.com/acoustic-content/docs
  - type: APIReference
    url: https://developer.goacoustic.com/acoustic-content/reference
  - type: GettingStarted
    url: https://developer.goacoustic.com/acoustic-content/reference/get-started
  - type: ErrorCatalog
    url: errors/acoustic-problem-types.yml
  - type: Conventions
    url: conventions/acoustic-conventions.yml
  - type: DataModel
    url: data-model/acoustic-data-model.yml
  - type: Webhooks
    url: asyncapi/acoustic-webhooks.yml
  - type: LLMsTxt
    url: llms/acoustic-llms.txt
- aid: acoustic:acoustic-authoring-reference-api
  name: Acoustic Authoring reference API
  description: The Content Authoring reference API is used to retrieve information about references between items in the system.
    The type of relationships that are tracked  depends on the type of item. Typically, if an item has an editable property
    that points to an ID of another item, it is tracked. You can use the API to fetch both incoming and outgoing references
    for any item.
  humanURL: https://developer.goacoustic.com/acoustic-content/
  baseURL: https://content-us-1.content-cms.com/api/{tenantId}
  tags:
  - Authoring reference
  properties:
  - type: OpenAPI
    url: openapi/acoustic-authoring-reference-api-openapi.yml
  - type: Swagger
    url: openapi/acoustic-content-swagger2-original.yaml
  - type: Documentation
    url: https://developer.goacoustic.com/acoustic-content/docs
  - type: APIReference
    url: https://developer.goacoustic.com/acoustic-content/reference
  - type: GettingStarted
    url: https://developer.goacoustic.com/acoustic-content/reference/get-started
  - type: ErrorCatalog
    url: errors/acoustic-problem-types.yml
  - type: Conventions
    url: conventions/acoustic-conventions.yml
  - type: DataModel
    url: data-model/acoustic-data-model.yml
  - type: Webhooks
    url: asyncapi/acoustic-webhooks.yml
  - type: LLMsTxt
    url: llms/acoustic-llms.txt
- aid: acoustic:acoustic-authoring-renditions-api
  name: Acoustic Authoring renditions API
  description: Use the Content renditions data service Rest APIs to work with image renditions. A 'rendition' of an image
    defines how you can customize a source image such as the width and height to be shown for a particular device or context.
    Renditions that are not referenced by an asset or content will be cleaned up periodically.
  humanURL: https://developer.goacoustic.com/acoustic-content/
  baseURL: https://content-us-1.content-cms.com/api/{tenantId}
  tags:
  - Authoring renditions
  properties:
  - type: OpenAPI
    url: openapi/acoustic-authoring-renditions-api-openapi.yml
  - type: Swagger
    url: openapi/acoustic-content-swagger2-original.yaml
  - type: Documentation
    url: https://developer.goacoustic.com/acoustic-content/docs
  - type: APIReference
    url: https://developer.goacoustic.com/acoustic-content/reference
  - type: GettingStarted
    url: https://developer.goacoustic.com/acoustic-content/reference/get-started
  - type: ErrorCatalog
    url: errors/acoustic-problem-types.yml
  - type: Conventions
    url: conventions/acoustic-conventions.yml
  - type: DataModel
    url: data-model/acoustic-data-model.yml
  - type: Webhooks
    url: asyncapi/acoustic-webhooks.yml
  - type: LLMsTxt
    url: llms/acoustic-llms.txt
- aid: acoustic:acoustic-authoring-resources-api
  name: Acoustic Authoring resources API
  description: Use the Content resources data service Rest APIs to work with resources. Resources are binary files that are
    stored in the CMS and used in content or site design. Resources that are not referenced by an asset or content will be
    cleaned up periodically.
  humanURL: https://developer.goacoustic.com/acoustic-content/
  baseURL: https://content-us-1.content-cms.com/api/{tenantId}
  tags:
  - Authoring resources
  properties:
  - type: OpenAPI
    url: openapi/acoustic-authoring-resources-api-openapi.yml
  - type: Swagger
    url: openapi/acoustic-content-swagger2-original.yaml
  - type: Documentation
    url: https://developer.goacoustic.com/acoustic-content/docs
  - type: APIReference
    url: https://developer.goacoustic.com/acoustic-content/reference
  - type: GettingStarted
    url: https://developer.goacoustic.com/acoustic-content/reference/get-started
  - type: ErrorCatalog
    url: errors/acoustic-problem-types.yml
  - type: Conventions
    url: conventions/acoustic-conventions.yml
  - type: DataModel
    url: data-model/acoustic-data-model.yml
  - type: Webhooks
    url: asyncapi/acoustic-webhooks.yml
  - type: LLMsTxt
    url: llms/acoustic-llms.txt
- aid: acoustic:acoustic-authoring-review-api
  name: Acoustic Authoring review API
  description: Use the Content Review Rest APIs to review assets and content. Use reviews to receive feedback from other members
    of your team. You can start, update, and complete the reviews that are set up. You can approve the content and assets
    under review.
  humanURL: https://developer.goacoustic.com/acoustic-content/
  baseURL: https://content-us-1.content-cms.com/api/{tenantId}
  tags:
  - Authoring review
  properties:
  - type: OpenAPI
    url: openapi/acoustic-authoring-review-api-openapi.yml
  - type: Swagger
    url: openapi/acoustic-content-swagger2-original.yaml
  - type: Documentation
    url: https://developer.goacoustic.com/acoustic-content/docs
  - type: APIReference
    url: https://developer.goacoustic.com/acoustic-content/reference
  - type: GettingStarted
    url: https://developer.goacoustic.com/acoustic-content/reference/get-started
  - type: ErrorCatalog
    url: errors/acoustic-problem-types.yml
  - type: Conventions
    url: conventions/acoustic-conventions.yml
  - type: DataModel
    url: data-model/acoustic-data-model.yml
  - type: Webhooks
    url: asyncapi/acoustic-webhooks.yml
  - type: LLMsTxt
    url: llms/acoustic-llms.txt
- aid: acoustic:acoustic-authoring-search-api
  name: Acoustic Authoring search API
  description: '## General

    Use the Content authoring search service REST API to access assets, categories, content, content types, image profiles,
    and taxonomies by searching the content hub. You need prior authentication to use the authoring search service. The authoring
    search service contains content in all states including draft, ready, and retired.

    ## 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

# --- truncated at 32 KB (57 KB total) ---
# Full source: https://raw.githubusercontent.com/api-evangelist/acoustic/refs/heads/main/apis.yml