generated: '2026-07-19'
method: searched
source: >-
  developer.khoros.com reference and changelog projects, https://status.khoros.com/,
  https://khoros.ai/customer-agreements/, and the harvested specs in ../openapi/.
description: >-
  How the Lithium / Khoros API surface versions, ages out and reports health. Versioning is
  URI-path major versioning with majors running in parallel (Care work queues expose v1 and
  v2; Care bots expose v2 and v3; Marketing Conversations exposes v1 and v2). Individual
  endpoints are retired by labelling them "deprecated" in the reference, but Khoros
  publishes no deprecation policy, no notice period and no Sunset/Deprecation header
  support. A public status page and a contractual SLA both exist.

versioning:
  scheme: uri-path
  examples:
    - https://api.app.lithium.com/bots/v3
    - https://{instance}.response.lithium.com/api/v2/conversations
    - https://{instance}.response.lithium.com/api/v1/
    - https://api.spredfast.com/v2
    - https://api.flow.ai/rest/v1
    - https://community.khoros.com/api/2.0
  parallel_majors: true
  note: >-
    Older majors remain documented and served alongside newer ones; there is no published
    migration deadline.

deprecation:
  policy_url: null
  policy_published: false
  sunset_header: false
  deprecation_header: false
  notice_period: null
  mechanism: >-
    Retired endpoints are marked "(deprecated)" in the Khoros Care API reference. None of
    the harvested OpenAPI definitions set `deprecated: true`, so the signal exists only in
    the human documentation, not in the machine-readable contract.
  deprecated_documented:
    - url: https://developer.khoros.com/khoroscaredevdocs/reference/supervisor-reports-api-deprecated
      subject: Supervisor Reports API
    - url: https://developer.khoros.com/khoroscaredevdocs/reference/generating-a-csv-export-deprecated
      subject: CSV export generation
    - url: https://developer.khoros.com/khoroscaredevdocs/reference/csvreportname-deprecated
      subject: CSV report name endpoint
    - url: https://developer.khoros.com/khoroscaredevdocs/reference/csv_longreportname-deprecated
      subject: CSV long report name endpoint
    - url: https://developer.khoros.com/khoroscaredevdocs/reference/list-deprecated
      subject: List endpoint
  deprecated_operations: []

status_page:
  url: https://status.khoros.com/
  status: 200
  subscriptions: [email, sms]
  incident_reporting: https://khoros.ai/lets-connect/
  note: Hosted status page with incident history and subscribe-to-updates.

sla:
  url: https://khoros.ai/customer-agreements/
  published: true
  uptime_target: null
  note: >-
    A Service Level Agreement defining uptime commitments, performance standards and
    remedies is incorporated into every Master Services Agreement. The numeric uptime
    target is not published on the public page.

dead_hosts:
  - host: api.massrelevance.com
    product: Khoros Marketing Stream API
    spec: ../openapi/_original/lithium-marketing-stream-api-openapi.json
    published_server: https://api.massrelevance.com
    status: 502
    probed: '2026-08-13'
    evidence:
      - {url: 'https://api.massrelevance.com/', status: 502}
      - {url: 'https://api.massrelevance.com/meta.json', status: 502}
      - {url: 'http://api.massrelevance.com/', status: 502}
      - {url: 'https://www.massrelevance.com/', status: 404}
    dns: dnrm287fziwlb.cloudfront.net (resolves)
    note: >-
      The Stream API is the Mass Relevance lineage that Spredfast acquired in 2014 and Khoros
      inherited through the 2018 merger. Its published host answers HTTP 502 Bad Gateway from
      an nginx front end on every path, over both HTTP and HTTPS, while DNS still resolves to
      a CloudFront distribution — the name and the CDN edge survive, the origin does not. 25
      operations across 24 apis.yml entries are described against this host and none of them
      is callable. Khoros has not marked the Stream API deprecated anywhere in the
      documentation, so this is a silent retirement, not an announced one.

undocumented_retirement:
  observed: true
  note: >-
    Khoros retires surfaces without announcing them. The Stream API host above is dead with no
    deprecation notice; the Care changelog's most recent entry is 2024-12-05 while the Brand
    Messenger Android SDK has shipped v2.0.1 (2026-01-01); and the RFC 9727 API catalog at
    developer.khoros.com/.well-known/api-catalog advertises three service-desc descriptors that
    all return 404. Consumers cannot distinguish a live surface from a retired one by reading
    the documentation.

support_lifecycle:
  platform_transition:
    from: Khoros Classic (Lithium Community)
    to: Aurora
    policy: >-
      Khoros publishes a no-forced-migration position — Classic customers are supported
      alongside Aurora with shared backend and data model, per
      https://khoros.ai/aurora/aurora-vs-classic/.

related:
  changelog: ../changelog/lithium-changelog.yml
  conventions: ../conventions/lithium-conventions.yml