---
title: "Get issue details"
method: GET
path: "/issues-api/v2/projects/{projectId}/issues/{issueUid}"
tags: ["Issues"]
---

# Get issue details

`GET /issues-api/v2/projects/{projectId}/issues/{issueUid}`

## Request

- Base URL: `https://api.smartling.com`
- URL: `https://api.smartling.com/issues-api/v2/projects/{projectId}/issues/{issueUid}`
- Auth: HTTP bearer

Returns detailed information of a single issue.

**Note**: The `resolvedByUserUid` and `reportedByUserUid` values are not currently usable for identifying the users who created or resolved issues. In the future, a People API will be exposed for looking up user details.

## Path parameters

- `projectId` string, required: Unique identifier of a Smartling project — 9 lowercase alphanumeric characters.
- `issueUid` string, required

## Response `200`

OK

- IssueGetResponse
  - `response` object, required
    - `code` 'SUCCESS', required: Indicates whether the response was successful or what error has occurred.
    - `data` object
      - `answered` boolean: Issue flag "aswered"
      - `createdDate` string: Issue creation date
      - `lastCommentDate` string: Comment Activity Date
      - `issueSeverityLevelCode` 'LOW' | 'MEDIUM' | 'HIGH': [Issue Severity Level identifier](#operation/getAllIssueSeverityLevels)
      - `issueStateCode` 'OPENED' | 'RESOLVED': [Issue State identifier](#operation/getAllIssuesStates)
      - `issueSubTypeCode` 'CLARIFICATION' | 'MISSPELLING' | 'POOR_TRANSLATION' | 'DOES_NOT_FIT_SPACE' | 'PLACEHOLDER_ISSUE' | 'REVIEW_TRANSLATION' | 'CUSTOM' | 'MT_ERROR': Issue SubType identifier
      - `issueText` string: Issue text
      - `issueTextModifiedDate` string: Issue text modification date
      - `issueTypeCode` 'SOURCE' | 'TRANSLATION': [Issue Type identifier](#operation/getIssueTypesByAccount)
      - `issueUid` string: Issue identifier
      - `projectId` string: Unique identifier of a Smartling project — 9 lowercase alphanumeric characters.
      - `accountUid` string: The account’s unique identifier. This can be found in the Smartling Dashboard under Account Settings > API.
      - `issueNumber` integer: Issue number
      - `reportedByUserUid` string: Unique identifier of a user — 12 lowercase alphanumeric characters.
      - `resolvedByUserUid` string: Unique identifier of a user — 12 lowercase alphanumeric characters.
      - `assigneeUserUid` string: Unique identifier of a user — 12 lowercase alphanumeric characters.
      - `resolvedDate` string: Issue resolve date
      - `reopened` boolean: Issue flag "reopened"
      - `reopenedByUserUid` string: Unique identifier of a user — 12 lowercase alphanumeric characters.
      - `reopenedDate` string: Issue reopen date
      - `string` object
        - `hashcode` string: MD5 hash digest — 32 lowercase hexadecimal characters.
        - `localeId` string: Locale identifier. Either a 2-letter language code (`en`) or a language-region pair (`en-US`). The language part is always lowercase; the region part is always uppercase.
      - `issueCommentsCount` integer: Issue comments count

## Changes

- **2026-10-17** `2cd7a8215799`: 1 info
  - endpoint added
- **2026-08-06** `ae422098d9c5`: 1 breaking
  - api removed without deprecation

[Operation history](https://skmtc.dev/smartling/apis/smartling-rest-api-reference/changes/issues-api/v2/projects/:projectId/issues/:issueUid/get.md)

---

[API](https://skmtc.dev/smartling/apis/smartling-rest-api-reference.md) - [All operations](https://skmtc.dev/smartling/apis/smartling-rest-api-reference/llms.txt) - [OpenAPI document](https://skmtc.dev/smartling/apis/smartling-rest-api-reference/revisions/e63066e7f5e9?raw)