# Compromised Device Detail

GET /cti/compromised-devices/{compromised_employee_device_id}: Returns one compromised device.

Source: https://docs.deepinfo.com/reference/cti/compromised-device-detail/

Last updated: 2026-09-27

---
`GET https://api.deepinfo.com/v1/cti/compromised-devices/{compromised_employee_device_id}`

Returns one compromised device.

## Authentication

Send your API key in the `apikey` request header.

## Path Parameters

| Parameter | Required | Description | Example |
|---|---|---|---|
| `compromised_employee_device_id` | Required |  | `<compromised_employee_device_id>` |

## Response Fields

| Field | Type |
|---|---|
| `id` | string |
| `account` | object |
| `compromised_device` | object |
| `leaked_data` | object |
| `compromise_summary` | object |

> No live example: the DEMO account has no data for this endpoint yet, or it returned an error during testing. The response shape is described above.

## Examples

### 404 · Not Found (nonexistent compromised_employee_device_id)

```bash
curl 'https://api.deepinfo.com/v1/cti/compromised-devices/ffffffffffffffffffffffff' \
  -H 'apikey: YOUR_API_KEY' \
  -H 'Accept: application/json'
```

`Content-Type: application/json` · `deepinfo-request-id: 00000000-0000-4000-8000-0000356d0001`

```json
{
  "code": 30003,
  "details": [
    "Compromised Employee Device with given id=ffffffffffffffffffffffff does not exist."
  ],
  "solution": "https://docs.deepinfo.com/reference/"
}
```
