# Get Article Edition Details

## Overview
  * This API retrieves the details of an article edition.

Endpoint: GET /articles/{articleID}/editions/{publishViewId}
Security: oAuthClient

## Header parameters:

  - `Accept-Language` (string, required)
    The Language locale accepted by the client (used for locale specific fields in resource representation and in error responses).
    Enum: "en-US", "es-ES", "fr-FR", "it-IT", "de-DE", "nl-NL", "pt-BR", "pt-PT", "da-DK", "ru-RU", "fr-CA", "zh-CN", "ja-JP", "ko-KR", "sv-SE"

## Path parameters:

  - `articleID` (string, required)
    The ID of the Article. Both numeric and alternate ID formats are supported.Valid numerical IDs are 15-19 digits long.
    Example: "PROD-2996"

  - `publishViewId` (string, required)
    The ID of a Publish View Id.A Publish View Id ID is composed of a 2-4 letter prefix, followed by a dash and 4-15 digits.
    Example: "PROD-3020"

## Query parameters:

  - `$lang` (string, required)
    The language used for fetching the details of a resource. Resources available in different languages may differ from each other.
    Enum: "en-US", "fr-FR", "en-GB", "es-ES", "it-IT", "nl-NL", "da-DA", "sv-SE", "pt-PT", "fi-FI", "no-NB", "no-NN", "ja-JA", "de-DE", "pt-BR", "zh-CN", "zh-TW", "ko-KO", "ru-RU", "el-EL", "tr-TR", "pl-PL", "cs-CS", "sk-SK", "hu-HU", "sr-SR", "ar-SA", "hr-HR", "ro-RO", "th-TH", "de-AT", "vi-VN", "id-ID", "ms-MY", "fil-PH", "fr-CA", "hi-IN", "uk-UA", "bg-BG", "sl-SI", "xx-XX"

## Response 200 fields (application/json):

  - `id` (string)
    ID of the edition.

  - `name` (string)
    Name of the edition.

  - `publishProfile` (object)
    This schema contains information about Profile.

  - `publishProfile.id` (string, required)
    The ID of the Publish Profile.An Publish Profile ID is composed of a 2-4 letter prefix, followed by a dash and 4-15 digits.

  - `publishProfile.name` (string, required)
    The name of the profile.

  - `content` (string)
    The raw content of the article. The maximum allowed Article content size is 5 MB.

  - `contentText` (string)
    Plain text version of the content. The maximum allowed Article content size is 5 MB.

  - `accessTags` (object)

  - `accessTags.tagCategory` (array)
    An array of tag categories. Note that the total number of tag categories cannot exceed 20.

  - `accessTags.tagCategory.name` (string)
    name of the tag category.

  - `accessTags.tagCategory.tagGroup` (array)

  - `accessTags.tagCategory.tagGroup.id` (string)
    The unique identifier for the tag group.
    Example: "PROD-14566"

  - `accessTags.tagCategory.tagGroup.name` (string)
    Name of the tag group.

  - `accessTags.tagCategory.tagGroup.tag` (array)

  - `accessTags.tagCategory.tagGroup.tag.id` (string)
    The unique identifier for the tag.
    Example: "PROD-13206"

  - `accessTags.tagCategory.tagGroup.tag.name` (string)
    The name of the tag.
    Example: "Blue"

  - `accessTags.tagCategory.created` (object)
    Date the Tag Category was created.

  - `accessTags.tagCategory.created.user` (object)

  - `accessTags.tagCategory.created.user.link` (array)
    The link to the user.

  - `accessTags.tagCategory.created.user.link.rel` (string)
    Defines the relationship between a linked resource and the current object.For example: self, prev, next or an object name such as 'user', 'folder' etc.

  - `accessTags.tagCategory.created.user.link.href` (string)
    The URL that specifies the link's destination.

  - `accessTags.tagCategory.created.user.firstName` (string)
    The first name of the user.

  - `accessTags.tagCategory.created.user.lastName` (string)
    The last name of the user.

  - `accessTags.tagCategory.created.user.id` (string)
    The ID of the user.

  - `accessTags.tagCategory.created.date` (string, required)
    The date in the format YYYY-MM-DDTHH:MM:SS.

  - `accessTags.tagCategory.lastModified` (object)
    Date of last modification.

  - `link` (object)
    Defines the relationship between this resource and another object.

## Response 400 fields (application/json):

  - `code` (string, required)
    A string that follows the pattern {integer}-{integer}.

The first {integer} is the http status code.  This code as a whole is unique.
* For example, error codes "400-101" and "404-101" are distinctly different.

  - `developerMessage` (string, required)
    A summary of the error.

  - `details` (array)

  - `details.key` (string, required)

  - `details.value` (string)

  - `userMessage` (string)
    UI friendly messages are only supported by some APIs.  
   The client must explicitly request UI friendly messages by passing the X-egain-error-message=yes* header.

## Response 401 fields (application/json):

  - `code` (string, required)
    A string that follows the pattern {integer}-{integer}.

The first {integer} is the http status code.  This code as a whole is unique.
* For example, error codes "400-101" and "404-101" are distinctly different.

  - `developerMessage` (string, required)
    A summary of the error.

  - `details` (array)

  - `details.key` (string, required)

  - `details.value` (string)

  - `userMessage` (string)
    UI friendly messages are only supported by some APIs.  
   The client must explicitly request UI friendly messages by passing the X-egain-error-message=yes* header.

## Response 403 fields (application/json):

  - `code` (string, required)
    A string that follows the pattern {integer}-{integer}.

The first {integer} is the http status code.  This code as a whole is unique.
* For example, error codes "400-101" and "404-101" are distinctly different.

  - `developerMessage` (string, required)
    A summary of the error.

  - `details` (array)

  - `details.key` (string, required)

  - `details.value` (string)

  - `userMessage` (string)
    UI friendly messages are only supported by some APIs.  
   The client must explicitly request UI friendly messages by passing the X-egain-error-message=yes* header.

## Response 404 fields (application/json):

  - `code` (string, required)
    A string that follows the pattern {integer}-{integer}.

The first {integer} is the http status code.  This code as a whole is unique.
* For example, error codes "400-101" and "404-101" are distinctly different.

  - `developerMessage` (string, required)
    A summary of the error.

  - `details` (array)

  - `details.key` (string, required)

  - `details.value` (string)

  - `userMessage` (string)
    UI friendly messages are only supported by some APIs.  
   The client must explicitly request UI friendly messages by passing the X-egain-error-message=yes* header.

## Response 406 fields (application/json):

  - `code` (string, required)
    A string that follows the pattern {integer}-{integer}.

The first {integer} is the http status code.  This code as a whole is unique.
* For example, error codes "400-101" and "404-101" are distinctly different.

  - `developerMessage` (string, required)
    A summary of the error.

  - `details` (array)

  - `details.key` (string, required)

  - `details.value` (string)

  - `userMessage` (string)
    UI friendly messages are only supported by some APIs.  
   The client must explicitly request UI friendly messages by passing the X-egain-error-message=yes* header.

## Response 500 fields (application/json):

  - `code` (string, required)
    A string that follows the pattern {integer}-{integer}.

The first {integer} is the http status code.  This code as a whole is unique.
* For example, error codes "400-101" and "404-101" are distinctly different.

  - `developerMessage` (string, required)
    A summary of the error.

  - `details` (array)

  - `details.key` (string, required)

  - `details.value` (string)

  - `userMessage` (string)
    UI friendly messages are only supported by some APIs.  
   The client must explicitly request UI friendly messages by passing the X-egain-error-message=yes* header.