# Retrieve an article version

Fetch a single prior version of an article, including its body content,
by making a GET request to
`https://api.intercom.io/articles/<article_id>/versions/<id>`. Returns
the version's full content; the live article remains untouched.
Requires the `read_articles_scope` OAuth scope. Set `Intercom-Version: Preview`.

Endpoint: GET /articles/{article_id}/versions/{id}
Version: Preview
Security: bearerAuth

## Path parameters:

  - `article_id` (integer, required)
    The unique identifier for the article.

  - `id` (string, required)
    The unique identifier for the version.

## Query parameters:

  - `locale` (string)
    Return the version's content for a specific locale. If the locale is not configured for the workspace, a `400` is returned.

## Header parameters:

  - `Intercom-Version` (string)

## Response 200 fields (application/json):

  - `type` (string)
    String representing the object's type. Always has the value `article_version`.
    Enum: "article_version"

  - `id` (string)
    The unique identifier for the version.
    Example: 301

  - `article_id` (string)
    The unique identifier of the article this version belongs to.
    Example: 123

  - `title` (string)
    The title of the article at this version.
    Example: This is the article title

  - `description` (string)
    The description of the article at this version.

  - `body` (string)
    The HTML body of the article at this version.
    Example: <p class="no-margin">Body of this version</p>

  - `body_markdown` (string)
    The Markdown body of the article at this version.
    Example: Body of this version


  - `author_id` (string)
    The id of the teammate listed as the article's author at this version.
    Example: 991267502

  - `created_by_id` (string)
    The id of the teammate who created this version.
    Example: 5017691

  - `created_via` (string)
    How this version was created (for example `web`, `api`).
    Example: web

  - `from_version_id` (string)
    The id of the version this version was created from, or `null` if this is the first version.
    Example: 300

  - `state` (string)
    Whether this version is the currently published version of the article (`published`) or an earlier non-live version (`draft`).
    Enum: "published", "draft"

  - `created_at` (integer)
    The time the version was created, as a UTC Unix timestamp.
    Example: 1734537292

  - `updated_at` (integer)
    The time the version was last updated, as a UTC Unix timestamp.
    Example: 1734537292

## Response 400 fields (application/json):

  - `type` (string, required)
    The type is error.list
    Example: error.list

  - `request_id` (string)
    Example: f93ecfa8-d08a-4325-8694-89aeb89c8f85

  - `errors` (array, required)
    An array of one or more error objects

  - `errors.code` (string, required)
    A string indicating the kind of error, used to further qualify the HTTP response code
    Example: unauthorized

  - `errors.message` (string)
    Optional. Human readable description of the error.
    Example: Access Token Invalid

  - `errors.field` (string)
    Optional. Used to identify a particular field or query parameter that was in error.
    Example: email

## Response 401 fields (application/json):

  - `type` (string, required)
    The type is error.list
    Example: error.list

  - `request_id` (string)
    Example: f93ecfa8-d08a-4325-8694-89aeb89c8f85

  - `errors` (array, required)
    An array of one or more error objects

  - `errors.code` (string, required)
    A string indicating the kind of error, used to further qualify the HTTP response code
    Example: unauthorized

  - `errors.message` (string)
    Optional. Human readable description of the error.
    Example: Access Token Invalid

  - `errors.field` (string)
    Optional. Used to identify a particular field or query parameter that was in error.
    Example: email

## Response 404 fields (application/json):

  - `type` (string, required)
    The type is error.list
    Example: error.list

  - `request_id` (string)
    Example: f93ecfa8-d08a-4325-8694-89aeb89c8f85

  - `errors` (array, required)
    An array of one or more error objects

  - `errors.code` (string, required)
    A string indicating the kind of error, used to further qualify the HTTP response code
    Example: unauthorized

  - `errors.message` (string)
    Optional. Human readable description of the error.
    Example: Access Token Invalid

  - `errors.field` (string)
    Optional. Used to identify a particular field or query parameter that was in error.
    Example: email