2
Trace Communications
Round 2 of 5
MISSION BRIEFING
You've identified the insider. Now we need to understand what they were planning and who else is involved. The insider may have been communicating with accomplices through NEXUS's internal messaging system. Search their communications to uncover the plot.
OBJECTIVE
Find all communications involving the insider. Identify who they were in contact with and summarize what they discussed. Return the names and employee IDs of their direct contacts.
HINTS
Use these if you get stuck
- [1]The communications endpoint can filter by senderId — but messages are bidirectional. The insider could be the sender OR the recipient.
- [2]Pay attention to the channel type — encrypted messages may contain more sensitive information.
AVAILABLE ENDPOINTS
GET
/api/communicationsSearch internal communications. When filtering by senderId, returns messages where that person is either the sender OR the recipient.
PARAMETERS
| Name | Type | Required | Description |
|---|---|---|---|
| senderId | string | no | Filter by participant employee ID (matches sender or recipient) |
| recipientId | string | no | Filter by the other participant (matches sender or recipient) |
| channel | string | no | Filter by channel: 'email', 'internal-chat', or 'encrypted' |
| search | string | no | Full-text search in subject and body |
| startDate | string | no | Filter messages after this ISO date |
| endDate | string | no | Filter messages before this ISO date |
| page | number | no | Page number (default: 1) |
| pageSize | number | no | Results per page (default: 20) |
EXAMPLE RESPONSE
{
"data": [
{
"id": "MSG-001",
"threadId": "THR-001",
"senderId": "EMP-047",
"senderName": "Dr. Yuki Tanaka",
"recipientId": "EMP-023",
"recipientName": "Marcus Chen",
"channel": "encrypted",
"subject": "Infrastructure Review - Urgent",
"body": "...",
"timestamp": "2045-03-13T09:15:00Z"
}
],
"pagination": {
"page": 1,
"pageSize": 20,
"total": 4,
"totalPages": 1
}
}