---
title: "Get the details of a ticket."
method: GET
path: "/api/v2/companies/{id}/tickets/{ticketId}"
tags: ["Ticket"]
---

# Get the details of a ticket.

`GET /api/v2/companies/{id}/tickets/{ticketId}`

Get the details of a ticket attributed to a finding.

## Path parameters

- `id` integer, required
- `ticketId` integer, required

## Response `200`

Success

- FindingTicket
  - `TicketId` number — The unique identifier of the ticket.
  - `TicketType` 'Finding' | 'Tag' — The type of the ticket. Tickets can be created based on either a 'Finding' or a 'Tag'. Each ticket can only have one type, determining its related object and context within the system. - Finding: Indicates that the ticket is associated with a specific finding. When the TicketType is 'Finding', the 'Finding' object will be populated and the 'Tag' object will be null. - Tag: Indicates that the ticket is associated with a tag. When the TicketType is 'Tag', the 'Tag' object will be populated and the 'Finding' object will be null.
  - `AssigneeType` 'Internal' | 'External' — The assignee type of the ticket. Indicates whether the ticket is assigned within the organization or to a vendor. - Internal: The ticket is assigned to users within the organization. - External: The ticket is assigned to a related vendor.
  - `Finding` FindingTicketFindingDetail, nullable
    - `Id` integer — The unique identifier of this finding.
    - `Module` string — The module of this finding. The possible responses are listed below. - DNS Health - Email Security - SSL/TLS Strength - Application Security - DDoS Resiliency - Network Security - Fraudulent Domains - Fraudulent Apps - Credential Mgmt. - IP Reputation - Hacktivist Shares - Social Network - Attack Surface - Brand Monitoring - Patch Management - Web Ranking - Information Disclosure - CDN Security - Website Security
    - `Severity` 'Info' | 'Low' | 'Medium' | 'High' | 'Critical' — The severity of a finding.
  - `Tag` TagTicketTagDetail, nullable
    - `Id` number — The unique identifier of the tag.
    - `Name` string — The name of the tag associated with this ticket.
  - `Status` 'Unassigned' | 'Assigned' | 'In Progress' | 'Closed–Acknowledged' | 'Closed–Remediated' | 'Closed–False Positive' | 'On Hold' | 'Recheck' | 'Deleted' — The status of this ticket. A ticket is automatically in “Assigned” status when a user with admin rights assigns it to another user. Depending on the user type, tickets can have different statuses: In Progress, On Hold and Recheck. - Unassigned: No owner has been set; the ticket is pending assignment. - In progress: Means the user takes responsibility of the associated finding and in the remediation process. - On hold: Means the user is waiting for another action to be completed before s/he takes action with regards to the finding. - Recheck: Means the user has completed her/his progress about the finding and waits for the user who assigns the ticket (or follow-up user with admin rights) to close it. An admin user can set a ticket in seven different statuses, In Progress, On Hold, Recheck, Closed-Acknowledged, Closed-Remediated, Closed-False Positive, and Deleted. - Closed-Acknowledged: The definition is very similar to risk acceptance. This means no or limited action can be taken with regards to the finding. There is no way but to accept the risk of the finding. This could be due to an out-of-date system soon to be retired. - Closed–Remediated: The action right after the Recheck status. If a company user sets the ticket in Recheck status, it is then passed to the admin user for him/her to close the issue. Closed status means the issue is fixed. - Closed-False Positive: Indicates a reported issue was a false alarm upon investigation. No action needed, as it poses no genuine risk. - Deleted: As the name suggests, this deletes the ticket (not the finding). It does not necessarily mean the issue is fixed or risk is accepted.
  - `DeliveryState` 'InvitationSent' | 'InvitationExpired' | 'InvitationFailed' | 'InvitationWaiting', nullable — The delivery state of this ticket invitation. Only populated when the ticket is Unassigned.
  - `Owners` string[] — A ticket may have one or more owners.
  - `FollowUpUsers` string[] — A ticket may have one or more follow up users.
  - `OpenDate` string, date-time — The date of this ticket is opened.
  - `AssignDate` string, date-time, nullable — The date of this ticket is assigned.
  - `ClosedDate` string, date-time, nullable — The date of this ticket is closed.
  - `UpdatedDate` string, date-time, nullable — The date of this ticket is updated.
  - `UpdatedBy` string — The user or system that last updated the ticket. This can be an email address, or SYSTEM for automated updates.
  - `CreatorEmail` string, email — The email address of the user who created the ticket.
  - `CreatorTenant` string, nullable — The name of the tenant (customer organization) that created the ticket.
  - `History` FindingTicketHistoryEntry[] — Contains the history entry logs for this ticket.
    - `Type` 'New Ticket' | 'Transfer' | 'Comment' | 'Status Change' | 'Ticket Deletion' | 'Action To Remote' | 'Action From Remote' — The type of the update made to the ticket. - New Ticket - Comment - Status Change
    - `Description` string — Description field also includes comments. Possibly HTML formatted.
    - `HistoryDate` string, date-time — The update date of this ticket.
    - `Owner` string, email — The owner of the comment.

## Other responses

- `401` — Unauthorized
- `403` — Forbidden
- `default` — Failure

---

[API](https://skmtc.net/blackkitetech/apis/black-kite-api.md) · [All operations](https://skmtc.net/blackkitetech/apis/black-kite-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/blackkitetech/black-kite-api/revisions/7dadaba760fb/schema)