> ## Documentation Index
> Fetch the complete documentation index at: https://docs.athenahq.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Mark Content as Published

> Mark a content item as published at its live URL so Athena starts attributing citations and mentions to it. Call this only after the piece is actually live on the site: the URL becomes the item's citation/metric join key, the publish time is stamped, and the pipeline stage moves to done. A first publish requires a finished article (stage generated): briefs, still-generating or failed pieces, and items with a scheduled CMS publish are rejected with 409 and the reason. Pass the exact public URL of the live page (a bare domain path like acme.com/blog/post is fine; the protocol is stripped on store). Calling it again on an already-published item (including external and imported pages, which are live by definition) updates the tracked URL only, keeping the original publish time. This is the only way to set a content URL over the API: the rename endpoint is deliberately title-only.



## OpenAPI

````yaml /api-reference/openapi.json post /api/v1/content/{content_id}/publish
openapi: 3.1.0
info:
  title: AthenaHQ API
  description: >-
    AthenaHQ API provides programmatic access to manage your websites and
    prompts for AI-powered content optimization.
  version: 1.0.0
  contact:
    email: support@athenahq.ai
servers:
  - url: https://api.athenahq.ai
    description: Production server
security:
  - apiKey: []
tags:
  - name: Basics
    description: Core API operations for managing websites and prompts
  - name: Metrics
    description: Metrics and analytics endpoints for tracking AI visibility
  - name: Billing
    description: Billing and credits endpoints for managing usage
  - name: Team Management
    description: Endpoints for managing team members and invitations
  - name: Groups
    description: Endpoints for managing groups of websites
  - name: Content
    description: >-
      Endpoints for accessing Content Hub data — tabs, tracked URLs, and per-URL
      prompt breakdowns.
  - name: Pitch Workspace
    description: >-
      Endpoints for accessing pitch workspace reports — org-scoped pitch runs
      with competitors, prompts, attributes, and aggregate metrics.
  - name: Knowledge Base
    description: >-
      Endpoints for reading the brand Knowledge Base — approved brand facts and
      the pillars that organize them.
paths:
  /api/v1/content/{content_id}/publish:
    post:
      tags:
        - Content
      summary: Mark Content as Published
      description: >-
        Mark a content item as published at its live URL so Athena starts
        attributing citations and mentions to it. Call this only after the piece
        is actually live on the site: the URL becomes the item's citation/metric
        join key, the publish time is stamped, and the pipeline stage moves to
        done. A first publish requires a finished article (stage generated):
        briefs, still-generating or failed pieces, and items with a scheduled
        CMS publish are rejected with 409 and the reason. Pass the exact public
        URL of the live page (a bare domain path like acme.com/blog/post is
        fine; the protocol is stripped on store). Calling it again on an
        already-published item (including external and imported pages, which are
        live by definition) updates the tracked URL only, keeping the original
        publish time. This is the only way to set a content URL over the API:
        the rename endpoint is deliberately title-only.
      operationId: content.publish
      parameters:
        - name: content_id
          in: path
          required: true
          schema:
            type: string
      requestBody:
        required: true
        content:
          application/json:
            schema:
              type: object
              properties:
                website_id:
                  type: string
                url:
                  type: string
              required:
                - website_id
                - url
      responses:
        '200':
          description: Success
          content:
            application/json:
              schema:
                type: object
                properties:
                  content_id:
                    type: string
                  title:
                    type: string
                    nullable: true
                  url:
                    type: string
                  published_at:
                    type: string
                    nullable: true
                  already_published:
                    type: boolean
                required:
                  - content_id
                  - title
                  - url
                  - published_at
                  - already_published
        '400':
          description: 'Bad Request: validation failed'
          content:
            application/json:
              schema:
                type: object
                properties:
                  error:
                    type: string
                required:
                  - error
        '401':
          description: Unauthenticated
          content:
            application/json:
              schema:
                type: object
                properties:
                  error:
                    type: string
                required:
                  - error
        '403':
          description: Forbidden
          content:
            application/json:
              schema:
                type: object
                properties:
                  error:
                    type: string
                required:
                  - error
        '404':
          description: Not Found
          content:
            application/json:
              schema:
                type: object
                properties:
                  error:
                    type: string
                required:
                  - error
        '409':
          description: >-
            Conflict: the piece has no finished article to publish (brief,
            generating, or failed stage), or it has a scheduled CMS publish
          content:
            application/json:
              schema:
                type: object
                properties:
                  error:
                    type: string
                required:
                  - error
        '429':
          description: Rate Limited
          content:
            application/json:
              schema:
                type: object
                properties:
                  error:
                    type: string
                required:
                  - error
        '500':
          description: Internal Error
          content:
            application/json:
              schema:
                type: object
                properties:
                  error:
                    type: string
                required:
                  - error
components:
  securitySchemes:
    apiKey:
      type: apiKey
      in: header
      name: x-api-key
      description: >-
        API key for authentication. You can create one
        [here](https://app.athenahq.ai/organization?tab=api).

````